- From: Henrik Frystyk Nielsen <frystyk@w3.org>
- Date: Mon, 11 May 1998 13:52:07 -0400
- To: "Roy T. Fielding" <fielding@kiwi.ics.uci.edu>, "David W. Morris" <dwm@xpasc.com>
- Cc: http-wg@cuckoo.hpl.hp.com, jg@w3.org
At 12:53 4/28/98 -0700, Roy T. Fielding wrote: >>From the point of view of the proxy, yes. From the user's perspective, >both indicate a failure of the proxy to map the identifier to a service. I think there is one situation that 504 doesn't cover and that is if the proxy doesn't *want* to proxy a certain URI, maybe because it can't (firewall etc.) or because it is not within it's trust domain etc. What are existing proxies doing in this situation? Adding this would clarify the situation a lot: 418 Not Proxying The server is not willing to proxy or gateway the Request-URI. No indication is given of whether the condition is temporary or permanent. The client MAY repeat the request using either a different proxy or no proxy at all. The 504 (Gateway Timeout) status code SHOULD be used if the server can not serve the request due to upstream errors. Henrik -- Henrik Frystyk Nielsen, World Wide Web Consortium http://www.w3.org/People/Frystyk
Received on Monday, 11 May 1998 10:55:21 UTC