On Fri, 2008-12-12 at 02:25 -0500, Alex Balashov wrote:
> Well, empty authorisation values mean invalid authorisation credentials,
> so why not? Either that or 500 Internal Server Error or 400 Bad Request.
The obvious choices are 400 (with a suitable reason phrase) (because the
header is syntact
2008/12/12 Alex Balashov :
> Well, empty authorisation values mean invalid authorisation credentials,
> so why not? Either that or 500 Internal Server Error or 400 Bad Request.
500 means an error in the server, while this is obviously a client
error. I expect 400 is the correct response while 5XX
rom: Brett Tate
> Subject: Re: [Sip-implementors] Empty Proxy-Authorization Header
> To: "Maxim Sobolev"
> Cc: sip-implementors@lists.cs.columbia.edu
> Date: Friday, 12 December, 2008, 1:53 AM
>
>>> What should be a response to an INVITE with
>>> an
Is sending a 403 Forbiddden jusitfied for this case?
--- On Fri, 12/12/08, Brett Tate wrote:
From: Brett Tate
Subject: Re: [Sip-implementors] Empty Proxy-Authorization Header
To: "Maxim Sobolev"
Cc: sip-implementors@lists.cs.columbia.edu
Date: Friday, 12 December, 2008, 1:53 AM
El Jueves, 11 de Diciembre de 2008, Iñaki Baz Castillo escribió:
> -
> 3.6 Variable Repetition*Rule
>
>
>The operator "*" preceding an element indicates repetition. The full
>form is:
>
> *element
>
>where and are optional deci
El Jueves, 11 de Diciembre de 2008, Brett Tate escribió:
> RFC 2234 section 3.8 indicates meaning of the brackets within ABNF:
>
>Square brackets enclose an optional element sequence:
>
> [foo bar]
>
>is equivalent to
>
> *1(foo bar).
Let me insist a bit ;)
--
ts.cs.columbia.edu
> Subject: Re: [Sip-implementors] Empty Proxy-Authorization Header
>
> El Jueves, 11 de Diciembre de 2008, Brett Tate escribió:
>
> > I agree that the header value is not optional within
> > Proxy-Authorization. However an empty header value is valid w
ailto:sip-implementors-boun...@lists.cs.columbia.edu] On
> Behalf Of Iñaki Baz Castillo
> Sent: Thursday, December 11, 2008 3:28 PM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] Empty Proxy-Authorization Header
>
> El Jueves, 11 de Diciembre de 2008, Br
El Jueves, 11 de Diciembre de 2008, Brett Tate escribió:
> I agree that the header value is not optional within
> Proxy-Authorization. However an empty header value is valid within some
> headers such as Supported.
"Supported" header does NOT allow empty value:
Supported = ( "Suppor
> > What should be a response to an INVITE with
> > an empty Proxy-Authorization header (i.e.
> > with no value) ?
>
> 400 Bad Request, just like any other empty
> header with no value IMHO. Header value is
> not optional.
I agree that the header value is not optional within
Proxy-Authorizati
> What should be a response to an INVITE with an empty
> Proxy-Authorization header (i.e. with no value) ?
If you want to be strict, return a 400 response. Otherwise you can
process the request as though the Proxy-Authorization was not intended
for your device.
_
ROHIT CHAUDHARY wrote:
> Hi,
>
> What should be a response to an INVITE with an empty Proxy-Authorization
> header (i.e. with no value) ?
400 Bad Request, just like any other empty header with no value IMHO.
Header value is not optional.
Regards,
--
Maksym Sobolyev
Sippy Software, Inc.
Intern
Hi,
What should be a response to an INVITE with an empty Proxy-Authorization header
(i.e. with no value) ?
Regards,
Rohit
Add more friends to your messenger and enjoy! Go to
http://messenger.yahoo.com/invite/
___
Sip-implementors mailing list
13 matches
Mail list logo
