Closed
Bug 1132478
Opened 9 years ago
Closed 9 years ago
Feed Reader sends wrong Accept header
Categories
(MailNews Core :: Feed Reader, defect)
Tracking
(thunderbird39 affected, thunderbird40 fixed, thunderbird41 fixed, thunderbird_esr3839+ fixed, seamonkey2.35+ fixed, seamonkey2.36 affected, seamonkey2.37 fixed)
People
(Reporter: wiktor, Assigned: alta88)
References
Details
Attachments
(1 file)
|
2.32 KB,
patch
|
mkmelin
:
review+
mkmelin
:
approval-comm-aurora+
mkmelin
:
approval-comm-beta+
mkmelin
:
approval-comm-esr38+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36 Steps to reproduce: 1. Subscribed to my feed through built-in Thunderbird's Feed Reader. Actual results: I saw the Accept header in my server logs has value "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" This breaks for example Content Negotiation. Expected results: The Accept header should be something similar to "application/atom+xml,application/rdf+xml,application/rss+xml,application/x-netcdf,application/xml;q=0.9,text/xml;q=0.2,*/*;q=0.1" as the expected file type is an XML feed.
|
||
Updated•9 years ago
|
Component: Untriaged → Feed Reader
Product: Thunderbird → MailNews Core
|
||
Comment 2•9 years ago
|
||
Bug 1138202 was on a Mac OS X, so setting it to All OSes. Macs are using x86_64 bits CPUs so I keep it as it is.
OS: Windows 8.1 → All
Assignee: nobody → alta88
Attachment #8625501 -
Flags: review?(mkmelin+mozilla)
|
||
Comment 4•9 years ago
|
||
Comment on attachment 8625501 [details] [diff] [review] feedAccept.patch Review of attachment 8625501 [details] [diff] [review]: ----------------------------------------------------------------- LGTM, r=mkmelin
Attachment #8625501 -
Flags: review?(mkmelin+mozilla) → review+
Keywords: checkin-needed
|
||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 41.0
|
||
Comment 6•9 years ago
|
||
Should this be considered for uplift to Thunderbird 38?
tracking-seamonkey2.35:
--- → ?
sure, why not. it likely has a very low incidence of being an issue and the change is also very low risk.
|
|
||
Updated•9 years ago
|
Attachment #8625501 -
Flags: approval-comm-esr38+
Attachment #8625501 -
Flags: approval-comm-beta+
Attachment #8625501 -
Flags: approval-comm-aurora+
|
|
||
Comment 8•9 years ago
|
||
http://hg.mozilla.org/releases/comm-beta/rev/4bb56ff83ba7 http://hg.mozilla.org/releases/comm-esr38/rev/04a14456d206 No push to aurora since uplift occurred.
status-seamonkey2.35:
--- → affected
status-seamonkey2.36:
--- → affected
status-seamonkey2.37:
--- → fixed
status-thunderbird39:
--- → affected
status-thunderbird40:
--- → fixed
status-thunderbird41:
--- → fixed
status-thunderbird_esr38:
--- → fixed
tracking-thunderbird_esr38:
--- → 39+
|
||
Updated•9 years ago
|
Blocks: SM2.35-Uplift
|
|
||
Comment 9•9 years ago
|
||
http://hg.mozilla.org/releases/comm-release/rev/da4fcbb68d85 SEAMONKEY_2_35_RELEASE_BRANCH
You need to log in
before you can comment on or make changes to this bug.
Description
•