1223834 - Repeated description for "Corrupted Content Error"

Status: RESOLVED FIXED

(Core :: Networking, defect)

Description

[YF (Yang)]

Attachment: screenshot

The errorShortDescText of errorShortDesc and errorLongDesc got the same content and displayed.


I see it while an URL returns invalid Location header with 302 Found, although the URL no longer reproducible.
Location:"javascript:void(0)&mtd=1" while HTTP 302.

Comment 1

[Ryan VanderMeulen [:RyanVM]]

Is this a regression? The code for this goes back to Fx7 and doesn't appear to have changed (directly, anyway) since.

Comment 2

[YF (Yang)]

Yes, I see the situation in Fx45b8 too.

STR:
Run the Fiddler2, go to AutoResponder.
Add Rule, "method:GET", "Create a new response...", click "Save" button.
Click [Raw] link in Headers tab, paste and save:
HTTP/1.1 302 Redirect
Date: Fri, 25 Jan 2013 16:49:29 GMT
Location: javascript:void(0)&mtd=1
Content-Length: 0

Open the http://127.0.0.1:8888 (or your port) in Firefox, see the error info.

Comment 3

[YF (Yang)]

Also happened for https://www.virtualbox.org/wiki/Translating?version=5&format=txt, Google Chrome says ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION for that.

Comment 4

[Patrick McManus [:mcmanus]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=ce42460d2a09

Comment 5

[Patrick McManus [:mcmanus]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=4a37ad10e220

Comment 6

[Patrick McManus [:mcmanus]]

Attachment: new err

Comment 7

[Patrick McManus [:mcmanus]]

Attachment: Corrupted Content Error Description repeated twice

Comment 8

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/7521936774c1

Comment 9

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/7521936774c1

Comment 10

[Francesco Lodolo [:flod]]

I'm sorry but you just broke l10n badly, introducing a variable in an existing string.
https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_content_best_practices#Changing_existing_strings

I'm going to file a follow-up and assign this bug to the same person who fixed this, but please be aware of it in the future, especially if you're reviewing patches involving strings.