Page MenuHomePhabricator

Mediawiki thumbnail requests for 0px should result in http 400 not 500
Closed, ResolvedPublic


There's significant traffic ATM for thumbnails with '0px' dimensions, mediawiki barfs with 500 on such requests. In this case the client is at fault though and mw should reply with 400 on bad parameters, not 500. Thumbor isn't affected and returns 400 instead.

Event Timeline

fgiunchedi raised the priority of this task from Medium to High.Oct 28 2016, 7:18 PM

There's still significant traffic for 0px thumbs resulting in 500s, it'd be helpful I think if MW returned 400 here since there's nothing we can do about it really

I think either 404 or 410 might be more appropriate. Typically 400 is for malformed requests in the HTTP sense (as in, unparseable/illegal request line), as opposed to undesirable query parameter values.

Indeed, 410 seems the more appropriate. 404 might give the impression that the url isn't persistently a failure. (cc @Gilles for Thumbor)

Looking at the definition of 400 seems more accurate than 410. The definition of 400 is broad and doesn't imply at what level the syntax is incorrect. The definition of 410 implies that the resource was there at some point in the past.

Mediawiki already returns 400s for other incorrect thumbnail parameters. Example:

Gilles added a project: Performance-Team.
Gilles moved this task from Inbox to Doing (old) on the Performance-Team board.

See T88412 for similar issues in the past.

Change 323385 had a related patch set uploaded (by Gilles):
Serve 400 instead of 500 when invalid thumbnail parameters are requested

Change 323385 merged by jenkins-bot:
Serve 400 instead of 500 when invalid thumbnail parameters are requested