I’ve got an interesting problem that I can’t seem to trace. On my site
(which is running Nginx 0.6.24), I have a link to a customer’s external
URL. When a user clicks that link and goes to the customer’s site, the
HTTP_REFERER is not being passed in the header by Nginx. I’ve verified
that the problem is not on their end by using the curl command and
manually passing a referrer… that shows up just fine on their end.
Is there a directive I need to enable (or one that has possibly disabled
it) that I can look at in my configs?
On Thu, Oct 07, 2010 at 10:19:14AM -0400, jmadtech wrote:
I’ve got an interesting problem that I can’t seem to trace. On my site
(which is running Nginx 0.6.24), I have a link to a customer’s external
URL. When a user clicks that link and goes to the customer’s site, the
HTTP_REFERER is not being passed in the header by Nginx.
When user “clicks that link and goes to the customer’s site” it’s
up to user browser to decide whether to send Referer header or not.
Your nginx doesn’t even know about that click and it’s not clear
why you think there is something to do with nginx here.
well that was my originally assumption, but I verified that in all 3
versions of my browser (firefox, IE and Chrome) that I’m set to pass
referer information to the site… and they’re still not getting it from
me. When I manually execute the same URL call from the command line
with a manually provided referer, it works fine.
Nevermind, I figured it out. Our site is HTTPS and the link that the
customer gave us is HTTP… according to HTTP referer - Wikipedia, “If a website is accessed
from a HTTP Secure connection and a link points to a non-secure
connection, then the referrer header is not sent”.
Thanks so much for pointing me in the right direction!
Posted at Nginx Forum:
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.