301 mapping
Hi,
occas is mapping an incoming 301 permanently moved to a 480 temporarily unavailable. Is this normal behavior? all I can find is this in RFC 2616.
If the 301 status code is received in response to a request other
than GET or HEAD, the user agent MUST NOT automatically redirect the
request unless it can be confirmed by the user, since this might
change the conditions under which the request was issued.
Is it correct container to return the 480? Our old SIP A/S did not.
thanks,
Bill
occas is mapping an incoming 301 permanently moved to a 480 temporarily unavailable. Is this normal behavior? all I can find is this in RFC 2616.
If the 301 status code is received in response to a request other
than GET or HEAD, the user agent MUST NOT automatically redirect the
request unless it can be confirmed by the user, since this might
change the conditions under which the request was issued.
Is it correct container to return the 480? Our old SIP A/S did not.
thanks,
Bill
0