Page MenuHomePhabricator

Content of a 400 Bad Request response does not fit to the Content-Type
Closed, ResolvedPublic


A GET request to returns the correct HTTP status code 400 Bad Request, but with not correct specified content: It has the HTTP header Content-Type: text/html and the plain text content Request must be POSTed.

$ curl -i --http1.1
HTTP/1.1 400 Bad Request
Content-Type: text/html

Request must be POSTed

Expected result: Either the Content-Type is text/plain or the content text is a HTML document.

Event Timeline

Fomafix created this task.Sep 24 2016, 6:41 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 24 2016, 6:41 PM
Fomafix claimed this task.Sep 24 2016, 7:15 PM
Fomafix triaged this task as Low priority.

Change 312650 had a related patch set uploaded (by Fomafix):
SpecialRunJobs: Use wfHttpError to generate error messages

Change 312650 merged by jenkins-bot:
SpecialRunJobs: Use wfHttpError to generate error messages

Krinkle closed this task as Resolved.Dec 15 2016, 7:22 AM