Closed Bug 538089 Opened 15 years ago Closed 15 years ago

[AMO] Zeus isn't setting the x-forwarded-for header?

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

All
Other
task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: clouserw, Assigned: oremj)

References

Details

I'm not seeing the X-Forwarded-For header on preview or production AMO.  http://knowledgehub.zeus.com/faqs/2007/07/09/passing_client_ip_in_http_headers says it's not on by default but can be flipped with:

http.setHeader("X-Forwarded-For", request.getRemoteIP());

I thought we already had that set, but I guess not?

This is blocking QA. Thanks.
Blocks: 448721
Assignee: server-ops → jeremy.orem+bugs
Severity: normal → critical
Already had a rule created but it wasn't applied to addons-ssl.  

Have added to both - can you let me know if it's working as expected now?
Severity: critical → major
Looks good on preview and production.

On preview it looks like two additional things are getting set:

REDIRECT_is-forwarded  =>  1
is-forwarded  =>  1

I don't care if more stuff is set, but preview and prod should be the same.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified FIXED on https://preview.addons.mozilla.org/en-US/firefox/reviews/display/3829:

by stephend (63.245.220.240) on January 6, 2010
Status: RESOLVED → VERIFIED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.