This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21874 - It would be very useful to be able to include custom headers during the initial handshake. Specifically, the use case in mind is for authorization headers.
Summary: It would be very useful to be able to include custom headers during the initi...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-30 07:58 UTC by contributor
Modified: 2013-06-12 23:48 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-04-30 07:58:15 UTC 
Specification: http://dev.w3.org/html5/websockets/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top
Referrer: 

Comment:
It would be very useful to be able to include custom headers during the
initial handshake. Specifically, the use case in mind is for authorization
headers.

Posted from: 71.95.126.13
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20130428 Firefox/23.0
Comment 1 Ian 'Hixie' Hickson 2013-06-06 20:32:35 UTC 
Why can't you just send them in the first packet?