Last modified: 2012-12-13 13:17:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45061, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43061 - Redirect loop while trying to view attachment
Redirect loop while trying to view attachment
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Highest critical (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-13 10:56 UTC by Daniel Kinzler
Modified: 2012-12-13 13:17 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Daniel Kinzler 2012-12-13 10:56:58 UTC
When trying to access the PNG attachment at <https://bugzilla.wikimedia.org/attachment.cgi?id=11489>, bugzilla is generating a redirect loop:


daniel@brightpad ~/tmp> LANG=EN wget -S -O /dev/null http://bugzilla.wikimedia.org/attachment.cgi?id=11489
--2012-12-13 11:55:25--  http://bugzilla.wikimedia.org/attachment.cgi?id=11489
Resolving bugzilla.wikimedia.org... 208.80.152.149
Connecting to bugzilla.wikimedia.org|208.80.152.149|:80... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 302 Found
  Date: Thu, 13 Dec 2012 10:55:25 GMT
  Server: Apache
  Location: https://bugzilla.wikimedia.org/attachment.cgi?id=11489
  Vary: Accept-Encoding
  Content-Length: 310
  Keep-Alive: timeout=15, max=100
  Connection: Keep-Alive
  Content-Type: text/html; charset=iso-8859-1
Location: https://bugzilla.wikimedia.org/attachment.cgi?id=11489 [following]
--2012-12-13 11:55:25--  https://bugzilla.wikimedia.org/attachment.cgi?id=11489
Connecting to bugzilla.wikimedia.org|208.80.152.149|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 302 Found
  Date: Thu, 13 Dec 2012 10:55:26 GMT
  Server: Apache
  X-xss-protection: 1; mode=block
  X-frame-options: SAMEORIGIN
  X-content-type-options: nosniff
  Location: https://bug-attachment.wikimedia.org/attachment.cgi?id=11489
  Content-Length: 0
  Keep-Alive: timeout=15, max=100
  Connection: Keep-Alive
  Content-Type: text/plain
Location: https://bug-attachment.wikimedia.org/attachment.cgi?id=11489 [following]
--2012-12-13 11:55:26--  https://bug-attachment.wikimedia.org/attachment.cgi?id=11489
Resolving bug-attachment.wikimedia.org... 208.80.152.149
Connecting to bug-attachment.wikimedia.org|208.80.152.149|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 302 Found
  Date: Thu, 13 Dec 2012 10:55:27 GMT
  Server: Apache
  Location: https://bugzilla.wikimedia.org/attachment.cgi?id=11489
  Vary: Accept-Encoding
  Content-Length: 317
  Keep-Alive: timeout=15, max=100
  Connection: Keep-Alive
  Content-Type: text/html; charset=iso-8859-1
Location: https://bugzilla.wikimedia.org/attachment.cgi?id=11489 [following]
--2012-12-13 11:55:27--  https://bugzilla.wikimedia.org/attachment.cgi?id=11489
Connecting to bugzilla.wikimedia.org|208.80.152.149|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 302 Found
  Date: Thu, 13 Dec 2012 10:55:28 GMT
  Server: Apache
  X-xss-protection: 1; mode=block
  X-frame-options: SAMEORIGIN
  X-content-type-options: nosniff
  Location: https://bug-attachment.wikimedia.org/attachment.cgi?id=11489
  Content-Length: 0
  Keep-Alive: timeout=15, max=100
  Connection: Keep-Alive
  Content-Type: text/plain
...
...
...
Comment 1 Andre Klapper 2012-12-13 11:28:21 UTC
https://bug-attachment.wikimedia.org to https://bugzilla.wikimedia.org and back.
Comment 2 Andre Klapper 2012-12-13 12:15:48 UTC
Reverting bug 43048 didn't change this plus it's likely more low-level.
Comment 3 Sam Reed (reedy) 2012-12-13 12:46:12 UTC
Fixed
Comment 4 Andre Klapper 2012-12-13 13:17:09 UTC
Reedy: What happened, and fixed how?


For the records, from #bugzilla:
<justdave> it'll redirect back to the main hostname to get a token issued to say you're authorized to see the attachment
<justdave> the main hostname will check your login cookie, see that you're authorized, and redirect you back with a one-time-use token 
<justdave> if something is happening that causes that token to not get recorded in the database then it wouldn't be valid and the attachment hostname would redirect you back again
<justdave> could also happen if something else is trying to retrieve it at the same time and the token gets used before you get there
<justdave> if there's javascript in an attachment that causes it to reload, the second load the token would no longer be valid and it'd have to go back for another one

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links