Fwd: OPTIONS and Method-Check

I am forwarding this e-mail from Anne since it does not appear in the  
public-appformats archive; my apologies for any dups you may receive ...

Begin forwarded message:

> Resent-From: "Anne van Kesteren" <annevk@opera.com>
> From: "ext Anne van Kesteren" <annevk@opera.com>
> Date: January 12, 2008 5:39:12 AM EST
> Resent-To: "WAF WG (public)" <public-appformats@w3.org>
> To: "Web API WG (public)" <public-webapi@w3.org>
> Subject: OPTIONS and Method-Check
> Archived-At: <http://www.w3.org/mid/op.t4tbvmdo64w2qv@annevk- 
> t60.oslo.opera.com>
>
>
> (Resending as I initially e-mailed this to the wrong list, public- 
> webapi@w3.org.)
>
> I and other played a bit more with our Apache installs (mine is on the
> shared-host DreamHost) in #html-wg yesterday and it turns out that  
> OPTIONS
> now works as Björn Höhrmann indicated earlier on this list. With  
> web_dav
> installed and without the need for ScriptTrapOptions. Jonas also  
> seemed
> happy with OPTIONS if support for it was present.
>
> The 10 to 20 lines code contest is now also pretty easy to beat. In  
> Python:
>
>    #!/usr/bin/env python
>    import os;
>    request_method = os.environ["REQUEST_METHOD"]
>    if "OPTIONS" == request_method:
>      ...
>    elif "GET" == request_method:
>      ...
>    else:
>      ...
>
> For PHP you use $_SERVER["REQUEST_METHOD"], for Perl $ENV 
> {REQUEST_METHOD},
> etc.
>
>
> I have left the Method-Check header in the specification, but as the
> primary (and only?) use case of that header was to indicate that  
> this is
> an authorization request maybe we should remove it. Opinions?
>
>
> -- 
> Anne van Kesteren
> <http://annevankesteren.nl/>
> <http://www.opera.com/>
>

Received on Monday, 14 January 2008 15:41:08 UTC