689981 - NPP_NewStream called with HTTP/0.9 200 OK header for a completely empty response

Status: RESOLVED WONTFIX

(Core Graveyard :: Plug-ins, defect)

Description

[David Fooks]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1

Steps to reproduce:

Created a very simple HTTP server for returning completely empty responses (simulating the loss of a connection before a response is received). Then made a GET request to the server using NPN_GetURLNotify.


Actual results:

NPP_NewStream is called by the browser but the NPStream argument headers property contains:

HTTP/0.9 200 OK\n

This now means that it is impossible to tell the difference between a perfectly valid "HTTP/0.9 200 OK\n\n" response and a completely empty response.


Expected results:

There should be no headers at all since there are no headers in the response. stream->headers should be NULL.

Safari does something similar (it inserts "HTTP 200 OK\n" omitting the version number)  but Chrome simply does not call NPP_NewStream.

Comment 1

[Boris Zbarsky [:bzbarsky]]

This may depend on the necko behavior for empty responses, which I believe changed recently.  If you try a trunk nightly, do you still see this issue?

Comment 2

[BMO Automation]

Resolving as wont fix, plugin support deprecated in Firefox 85.