On Mar 24, 2015, at 3:26 PM, Francis Daly wrote:
> but the original "if ($query_string)" is probably simpler at
> that point.
thanks for the help! it's great having a second set of eyes on this!
___
nginx mailing list
nginx@nginx.org
http://mailman.
On Mar 24, 2015, at 2:10 PM, Gena Makhomed wrote:
> Probably you can do such tracking just looking at Referer request header
Long story short - we actually are doing that. This is just to get stats into
the HTTPS log analyzer, which is a different system and much easier for us to
deploy chang
On Wed, Mar 25, 2015 at 02:50:29AM +0900, Edho Arief wrote:
> On Wed, Mar 25, 2015 at 2:32 AM, Francis Daly wrote:
Hi there,
> > If your backend will accept /request?source=server1 and
> > /request?&source=server1 as being equivalent, then you could use the
> > $is_args variable and just always
On 24.03.2015 17:33, Jonathan Vanasco wrote:
i need to redirecting from http to https,
and append a "source" attribute for tracking
(we're trying to figure out how the wrong requests are coming in)
Probably you can do such tracking just looking at Referer request header
this seems to work:
On Wed, Mar 25, 2015 at 2:32 AM, Francis Daly wrote:
> On Tue, Mar 24, 2015 at 11:33:41AM -0400, Jonathan Vanasco wrote:
>
> Hi there,
>
>> if ($query_string){
>> return 301
>> https://$host$request_uri&source=server1 ;
>>
On Tue, Mar 24, 2015 at 11:33:41AM -0400, Jonathan Vanasco wrote:
Hi there,
> if ($query_string){
> return 301
> https://$host$request_uri&source=server1 ;
> }
> return 301 https://$host$request_uri?s
i need to redirecting from http to https, and append a "source" attribute for
tracking (we're trying to figure out how the wrong requests are coming in)
this seems to work:
if ($query_string){
return 301
https://$host$request_uri&source=s
