[OpenSER-Devel] [ openser-Bugs-1822692 ] 503 behavior
SourceForge.net
noreply at sourceforge.net
Tue Oct 30 11:07:02 UTC 2007
Bugs item #1822692, was opened at 2007-10-30 12:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1822692&group_id=139143
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver 1.2.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Klaus Darilion (klaus_darilion)
Assigned to: Nobody/Anonymous (nobody)
Summary: 503 behavior
Initial Comment:
Hi!
1. bug: Openser should change 503 to 500 when relaying responses as otherwise it will disable itself if upstream proxy is also openser with default blacklisting.
RFC 3261 page 111:
A proxy which receives a 503 (Service Unavailable) response
SHOULD NOT forward it upstream unless it can determine that any
subsequent requests it might proxy will also generate a 503.
In other words, forwarding a 503 means that the proxy knows it
cannot service any requests, not just the one for the Request-
URI in the request which generated the 503. If the only
response that was received is a 503, the proxy SHOULD generate
a 500 response and forward that upstream.
2. bug: Openser puts SIP node which sent 503 on blacklist even if Retry-After header is not present (this case should be handled like 500):
RFC 3261 page 191:
The server is temporarily unable to process the request due to a
temporary overloading or maintenance of the server. The server MAY
indicate when the client should retry the request in a Retry-After
header field. If no Retry-After is given, the client MUST act as if
it had received a 500 (Server Internal Error) response.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1822692&group_id=139143
More information about the Devel
mailing list