Page MenuHomePhabricator

upload.wikimedia.org is giving 401 unauthorized when trying to get old versions of some images
Closed, ResolvedPublic

Description

Author: tan90000

Description:
error msg

when I click on the image http://en.wikipedia.org/wiki/file:territories_of_dynasties_in_china.gif, computer shows an "authentication required" window with the message "the site http://upload.wikimedia.org asks a username and password. The site indicates: "Sun Java System Web Server" and fields to enter your username and password.


Version: unspecified
Severity: major
URL: http://upload.wikimedia.org/wikipedia/en/archive/5/54/20071203110014!Territories_of_Dynasties_in_China.gif
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=44872

Attached:

Details

Reference
bz22321

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:46 PM
bzimport set Reference to bz22321.

Just checked. Upload.wikimedi.org is asking for username and password, using basic HTTP authorization on old images (for example: http://upload.wikimedia.org/wikipedia/en/archive/5/54/20071203110014!Territories_of_Dynasties_in_China.gif )

Changing component, as this is a wikimedia issue, not a mwdumper issue.

Then perhaps it's one of old images deleted from a bug and recreated as folder.

In that case, the server should give either a 404 or 403. People browsing to http://en.wikipedia.org/wiki/File:Territories_of_Dynasties_in_China.gif get a lot of popups asking for there username and pass, which is rather confusing.

I'm not saying that a 403 there is right. Just trying to guess the reason. I think folders used to be listable but now they aren't. Thus, if it is a "folder image", and now (ie. server move) the server was configured to give a 403 when requesting folders, that would be a reasonable explanation for the new error.

PS: Obviously the solution is to delete it and send people to http://commons.wikimedia.org/wiki/File:Territories_of_Dynasties_in_China.gif :)

Yes, this is a directory with nothing in it, dated Sept 5 2008, so it's a remnant of the thumb generation bug we had for a while on that day. I should clear those out.

In the meantime the configuration issue has been fixed (wrong keyword in an acl).