Re: [hybi] Additional HTTP headers on upgrade request?

[Greg Wilkins <[e-mail]>]

On 21 July 2010 10:57, Ian Hickson <[e-mail]> wrote:

> On Fri, 7 May 2010, Doug Simpkinson wrote:
> >
> > In draft 76, the upgrade request is said to include cookies that may be
> > relevant, but no mention of other HTTP headers is made.
> >
> > What about other relevant HTTP headers such as User-Agent and
> > Accept-Language?  Shouldn't these also be sent?
>
> What's the use case?
>

Ian,

it is a little disingenuous of you to fall back on the "what's the use
case?" stone wall
on topics like this that have been long discussed and people have given many
use
cases at length.   You might not understand and/or agree with the use cases
presented,
but that is entirely different to pretending that others have not motivated
their contributions
to the discussion with good reasoning.

The result of continually asking "what is the use-case" when it has already
been explained
many times, is that the list just goes around and around in endless circles.

In this particular case, it has been long argued that arbitrary headers
should be allowed in
the handshake for flexibility and anticipation of future needs.   You've
refuted the need for
generally extensible header.  Now  Doug motivated his comment with the
specific
use-case of using user-agent for dealing with browser quirks.


Let's flip this around the otherway... because allowing arbitrary headers is
not really
a feature of websocket is not really a feature because before the upgrade
the connection
is HTTP and thus arbitrary headers is allowed.

In essence, you should be making the use-case for adding a "feature" to the
websocket
handshake to prevent the addition of arbitrary headers.

So what is the use-case for that?  I know you have previously argued that
somehow it
would be easier for amateur not to have to write code to ignore headers
(surely they
just don't write code to handle them?), but the amateur programmer
requirement has been
widely rejected.     Is there any other use-case that motivates the
rejection of websocket
handshakes due to the presence of additional ignorable headers?