Hello Jim,
could you install the livehttpheaders mozilla extension
(http://livehttpheaders.mozdev.org/) and give us the reponse headers
sent by both servers when using Mozilla as a client?
best regards,
Thierry Boileau
*
*
I am using Restlet 1.0.1. It is being used in Tomcat 6 with Spring. My Restlet
is invoked from a Servlet using a ServletConverter. My Restlet handles a
scenario where it can't map a URI to a resource (database lookup fails) by
setting the Status in the Response to Status.CLIENT_ERROR_NOT_FOUND (404). When
I test this with a standalone Restlet based client, it detects the 404 just
fine. However, when I access the service with Mozilla 2.x, I get a blank page.
I tried a similar test with a plain Servlet and returned a Servlet status of
HttpServletResponse.SC_NOT_FOUND. When I do this, the Restlet client still
detects 404, but now Mozilla presents an error page saying there was a 404.
Has anyone else experienced this? I would like the service to be accessed by
both a program and a browser. When a browser user types in a URI that doesn't
exist, I think they should see a 404 error page, and not a blank page. There is
something different between how a Restlet sets the 404 and the way a Servlet
sets the 404 that causes different behavior in Mozilla.
