Closed
Bug 354814
Opened 19 years ago
Closed 19 years ago
network.http.sendRefererHeader set to 0 as default in 2.0 RC1
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mario, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060918 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060918 Firefox/2.0
What a nasty little bugger! I updated my Firefox browser to v2.0 RC1 today and noticed I could not publish to my blog anymore. After a little bit of digging, I found this posted on the Wordpress site:
“Once Wordpress has identified you as an authorized user with permission to make changes, you can access any of the protected admin options. All the pages within the admin area remain secure, without the nuisance of your having to log in to each page individually. Any additional admin page you choose can verify your status by checking to see which page you just came from. It does this by checking the referrer that the browser passes to it.”
OK, so I finally found a post on how to fix this. I’ve noticed that in Firefox 2.0 RC1, network.http.sendRefererHeader is set to 0 as default. In previous versions, it is set to 2 as default. These are the settings:
0 - Never send the Referer header.
1 - Send the Referer header when clicking on a link.
2 - Send the Referer header when clicking on a link or loading an image.
You set this option by typing about:config in the address bar of the Firefox browser and scrolling down to network.http.sendRefererHeader. Check the setting and modify (I set mine to 1 and it works fine). Those concerned with privacy can set this to 0, realizing that this may adversely affect some sites. Those wanting to ensure compatibility should leave it at 1 or 2. Closest I could find was http://codex.wordpress.org/Enable_Sending_Referrers.
Reproducible: Always
Steps to Reproduce:
See details
Actual Results:
See details
Expected Results:
See details
See details
Comment 1•19 years ago
|
||
Is this issue present in firefox's safemode?
- http://kb.mozillazine.org/Safe_mode
Reporter | ||
Comment 2•19 years ago
|
||
Tried it in safe mode and reproduced the error.
network.http.sendRefererHeader set to 0 as default in 2.0 RC1 safe mode as well.
Comment 3•19 years ago
|
||
Sigh. Apologies Mario, I had a brain-burp :) Of course, I meant to ask you to please try a new profile:
- http://kb.mozillazine.org/Profile_manager
With Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1) Gecko/20060929 BonEcho/2.0 ID:2006092903 and a new profile, in about:config the network.http.sendRefererHeader key is set to '2' for me.
Reporter | ||
Comment 4•19 years ago
|
||
network.http.sendRefererHeader set to 2 as default after creating a new profile.
Comment 5•19 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Comment 6•19 years ago
|
||
-->WFM probably better.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 7•19 years ago
|
||
Did a fresh install after wiping out the profiles and network.http.sendRefererHeader is indeed set to 2. Thanks Steve!
Comment 8•19 years ago
|
||
No problems! Thanks for taking time out to file a bug.
Assignee | ||
Updated•7 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•