Hi,
This test calls the method HttpServletResponse.setStatus(int, String) which
was deprecated at servlet API 2.1. Therefore, should this test still
belong in the 2.3 test buckets?
-Byron
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL
Hi Byron,
Yes, even though it's deprecated, it is a part of the API and still
valid to call.
-rl
On Tue, 2002-07-09 at 12:51, Byron L Bailey wrote:
Hi,
This test calls the method HttpServletResponse.setStatus(int, String) which
was deprecated at servlet API 2.1. Therefore, should this
Ryan,
Thanks for your quick response. However, the reason that I ask is because
in the Servlet 2.1 Spec it says that when calling setStatus(int, String
msg), the msg is sent back as the body of the response. Yet, it appears
that watchdog expects a blank response since there is no golden file
Byron,
Actually, the test expects the following to occur:
- A status code of 200
- A reason-phrase populated with the value of the message
argument from setStatus(int, String)
- A response header 'GenericResponseWrapper:setStatusMsg'
I will need to double check the 2.1 spec, but my guess
Ryan,
It looks like the HTTP server is converting my reason-phrase to OK, hence
the failure. The spec was unclear by saying that the message would be sent
back as body, and resulted in my confusion. Thanks for your help. -Byron
