AMO records commenter's IP, probably to easily spot duplicate comments or returning shrills/trolls. Unluckily a side effect of the proxy cache is hiding this info: all the comments appear to come from 10.2.81.4.
Duplicate of this bug: 370352
Moving to Public Pages as that is where reviews originate. I think this is still a problem in Remora. (Also occurs with download logging)
Component: Developer Pages → Public Pages
OS: Windows XP → All
QA Contact: developers → web-ui
Hardware: PC → All
Target Milestone: --- → 3.1
Target Milestone: 3.1 → 3.2
Version: 2.0 → 3.0
Does the Netscaler pass on the original user's IP in a request header? If not, can we make it? If it can't, this is a classical "CANTFIX" I'd say. But if we can get the cache to pass it on to the app server, we should put some magic into place to fish the right IP out of the request. CCing mrz because he knows how the Netscalers roll.
(In reply to comment #3) > Does the Netscaler pass on the original user's IP in a request header? If not, > can we make it? HTTP_X_FORWARDED_FOR, iirc.
(In reply to comment #3) > Does the Netscaler pass on the original user's IP in a request header? If not, > can we make it? Client IP is passed along as X-Forwarded-For.
This isn't an issue anymore.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.