Closed Bug 1242098 Opened 9 years ago Closed 3 years ago

HTTP inspection should understand semantics of OPTIONS requests

Categories

(DevTools :: Netmonitor, defect)

Product:
DevTools
Component:
Netmonitor
Version:
43 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: michalwadas, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20160106234723 Steps to reproduce: Browser perform OPTIONS request to external server. External server returns following headers: Cache-Control: no-cache Content-Type: application/json Date: Sat, 23 Jan 2016 01:16:25 GMT access-control-allow-headers: authorization access-control-allow-methods: GET, PUT, PATCH, POST, DELETE, OPTIONS access-control-allow-origin: ... access-control-max-age: 300 Actual results: I can inspect "Response" tab of OPTIONS request with red message "SyntaxError: JSON.parse: unexpected end of data..." Expected results: OPTIONS request aren't supposed to contain response body, so if there is no body, tab "response" is pointless and rather confusing (many times I have mistaken OPTIONS request with real one).
Component: Untriaged → Networking: HTTP
Product: Firefox → Core
Component: Networking: HTTP → Developer Tools: Netmonitor
Product: Core → Firefox
Product: Firefox → DevTools

Firefox 94 doesn't have this issue (response tab is properly empty).

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.