[Osr-101] [Fwd: [Phoenix] Neutron-Auth does not specify WWW-Authenticate header]

[Thomas Comiotto]

Hi

I think this has been discussed here before and we came to the 
conclusion that the protocol payload has to be parsed by default, but 
optimisation hints for specific transport protocols can be included 
where feasable.

Note that lenya 1.2 implements Neutron without the need for a custom 
HTTP header. It does so by providing a single endpoint for neutron 
clients. Runs just fine.

--
Bests
Thomas



Am 07.09.2006 um 16:11 schrieb Andreas Wuest:

> This message was of course intended for the Neutron mailinglist.
>
> -------- Original Message --------
> Subject: [Phoenix] Neutron-Auth does not specify WWW-Authenticate 
> header
> Date: Thu, 07 Sep 2006 16:09:20 +0200
> From: Andreas Wuest <awuest at student.ethz.ch>
> To: phoenix at wyona.org
>
> Hi
>
> Neutron-Auth does not specify a value for the WWW-Authenticate header.
> This makes it impossible to distinguish between used authentication
> schemes on the application layer, because we have to inspect the actual
> payload of the HTTP response to detect that we have a Neutron-Auth
> challenge.
>
> I would therefore propose the following:
>
> WWW-Authenticate: Neutron-Auth
>
> This enables protocol handlers on the application layer to locate the
> correct authentication module to use.
>
> -- 
> Kind regards,
> Andi
>
> _______________________________________________
> Phoenix mailing list
> Phoenix at wyona.org
> http://wyona.com/cgi-bin/mailman/listinfo/phoenix
>
> -- 
> Kind regards,
> Andi
>
> _______________________________________________
> Osr-101 mailing list
> Osr-101 at wyona.org
> http://wyona.com/cgi-bin/mailman/listinfo/osr-101
>