Well, actually "55.55.55.55" *is* a token. :-)
token = 1*(alphanum / "-" / "." / "!" / "%" / "*"
/ "_" / "+" / "`" / "'" / "~" )
But I agree with the rest of what Dale says. Certainly it isn't a
*valid* token since it hasn't been registered. But all the recipient
needs to know is that it doesn't support it.
This is a pretty good way to ensure you don't have *any* proxies in your
call!
Paul
[EMAIL PROTECTED] wrote:
> From: Arif <[EMAIL PROTECTED]>
>
> while testing my proxy server I encountered this Proxy-Require Header
> Proxy-Rquire : 55.55.55.55 (IP)
>
> the proxy sends 420 in response to this Proxy-Require header..
>
> but i tried to look up in rfc's related to sip about the meaning of
> this particular Proxy-Require value but didn't get a clear
> picture..
>
> Can any one please enlighten me on this issue ?
>
> The syntax is given at the top of page 231, RFC 3261. The processing
> is discussed in RFC 3261, section 16.3, item 5.
>
> In this case, the Proxy-Require header is syntactically incorrect, as
> "55.55.55.55" is not a "token". Since all proxies are required to
> reject a request with a 420 response if the request contains a
> Proxy-Require header with a value that is not an option-tag that it
> understands, and since since "55.55.55.55" can never be an option-tag,
> the proxy is acting correctly. The UA that is sending that field is
> erroneous.
>
> Dale
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
