[Webkit-unassigned] [Bug 39595] New: Web Inspector does not respect HTTP status message

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=39595

           Summary: Web Inspector does not respect HTTP status message
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: yutak at chromium.org
                CC: timothy at hatcher.name, rik at webkit.org,
                    keishi at webkit.org, pmuellr at yahoo.com,
                    joepeck at webkit.org, pfeldman at chromium.org,
                    yurys at chromium.org, bweinstein at apple.com,
                    ukai at chromium.org


Currently, Web Inspector does not respect the HTTP status message (which comes with HTTP status code). It looks up the predefined set of status messages from the status code (as in Resource.js).

This design introduces a couple of problems:

- It cannot handle the status code which has potentially multiple status texts. For example, "101 Switching Protocols" from HTTP/1.1 vs "101 WebSocket Protocol Handshake" from WebSocket protocol spec. This will be a problem when I'll merge a patch that displays the info for WebSocket in the Web Inspector.

- It cannot handle unknown status codes. In the past I saw a web server that returned a response like "490 <Vendor-specific status text>" (unfortunately I don't remember what service was doing this). In this case the Inspector shows "490 undefined", which does not sound desirable to me. I admit this is a rare case that will not happen often in the wild, though.

Can we use the response text that the server returns?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.