Comment 1 for bug 1437607

I don't think this is a bug. This is only with this particular url. For some reason it provides a valid response when you put it in your web browser.

You can see the response vocal is getting on http://onlinecurl.com/. Oddly enough the response is correct when I use curl in my terminal.

The headers are:
HTTP/1.1 403 Forbidden
Date: Sat, 06 Jun 2015 20:51:06 GMT
Content-Type: text/plain; charset=ISO-8859-1
Content-Length: 11
X-ContextId: 7h9AFpoz/ELuEWBeK
X-Via: 1.1 ny1-prod-echo012
X-ServedBy: 10

The body is:
Forbidden.

I did some debugging in vocal and it seems to be getting the same result.