Hi Valentin,
I am not sure that what you provided is exactly what I am trying to
achieve.
What I want is if someone hits port 80 (HTTP) with /account that they
redirect to /account on port 443 (HTTPS). However, if they come in on port
443 (HTTPS) with /account that they remain on port 443 (HTTPS
On Friday 03 October 2014 12:43:29 nikolaos2012 wrote:
> Hi Valentin,
>
> I have read that I should be using the location directive unless I have
> numerous mappings in other places.
>
> In this case we have about a dozen mappings.
>
> But I am curious if I used the location directive what would
Hi Valentin,
I have read that I should be using the location directive unless I have
numerous mappings in other places.
In this case we have about a dozen mappings.
But I am curious if I used the location directive what would the above
mapping example translate to so that it results in a $use_se
On Thursday 02 October 2014 23:08:53 nikolaos2012 wrote:
> We have the following code that worked in 1.3.16
>
>
> # Map VWS URI's to HTTP ($use_secure=0), HTTPS ($use_secure=1) or keep same
> ($use_secure=2)
> map $uri $use_secure {
> default 0;
> ~^/sites/ 2;
> ~^/account/ 1;
> }
[..]
$uri
Turns out that this was a mis-configuration on our end and that it works
great in 1.6.0+
We had the issue on a test server that had 2 sites sharing the same IP
address but moreover both sites assigned the $use_secure variable so it was
being overwritten by the 2nd site and always set to 0 b/c of n
We have the following code that worked in 1.3.16
# Map VWS URI's to HTTP ($use_secure=0), HTTPS ($use_secure=1) or keep same
($use_secure=2)
map $uri $use_secure {
default 0;
~^/sites/ 2;
~^/account/ 1;
}
And this file for the main config that includes the map file:
include /srv/etc/web_x/
