Re: [#193] Request payloads and push

What are the good reasons to restrict this?
One can always ignore a push by RSTing the promised stream.
An endpoint must have logic to do this anyway, so this isn't adding any
more code.

Safe methods without bodies seems fine.

cache invalidations != 304 get.
-=R



On Tue, Aug 13, 2013 at 4:13 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> * Mike Belshe wrote:
> >I don't think this works - I don't believe the OPTIONS request is required
> >to carry the query string, so you wouldn't know what response to push.
> > (pls double check on the query string, but I think I'm right)
>
> Could you clarify what you want to have double checked? There are no
> special provisions for query strings in "CORS" that I am aware of, and
> it would be rather unwise to add any.
> --
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
>
>