Re: Content Sniffing impact on HTTPbis - #155

Henrik Nordstrom wrote:
> HTTP intends that these representations should have pretty much the same
> semantic meaning to the user,

The is clearly not true in the case of some forms and web applications,
where every step through the form/application is served on the same
URL, with state managed through a combination of POSTed hidden form
fields and/or server-side state addressed through cookies or a URL token.

It's clearly the same resource they are dealing with ("the
form/appliction"), I won't argue against that, but the representations
served up have quite different semantic meanings to the user.

An entire complex site can be constructed that way.

> but can naturally not enforce it.

Does that mean such applications are not complying with
specifications, even though they are technically possible?

-- Jamie