Garr oh well . If only we had a servlet spec person around who would
know for sure if this is possible.
On 4/4/07, Hans Drexler <[EMAIL PROTECTED]> wrote:
On Tue, 3 Apr 2007 20:49:02 -0400, Jesse Kuhnert wrote
> You can still do HttpServletResponse.setStatus(int code, String
> message);
>
> It's
On Tue, 3 Apr 2007 20:49:02 -0400, Jesse Kuhnert wrote
> You can still do HttpServletResponse.setStatus(int code, String
> message);
>
> It's deprecated so there may be a better way but who knows..It
> wouldn't make sense if they didn't let you do it.
>
I think the setStatus() will only affect
You can still do HttpServletResponse.setStatus(int code, String message);
It's deprecated so there may be a better way but who knows..It
wouldn't make sense if they didn't let you do it.
On 4/3/07, Hans Drexler <[EMAIL PROTECTED]> wrote:
On Tue, 03 Apr 2007 14:11:03 +0100, Richard Kirby wrote
>
On Tue, 03 Apr 2007 14:11:03 +0100, Richard Kirby wrote
> Hi Hans,
>
> The status line is output by the servlet engine - not Tapestry,
> since it is a core part of the HTTP spec.
>
> What you may be able to do, is create a javax.servlet.Filter which
> reads the response from Tapestry into a str
Hi Hans,
The status line is output by the servlet engine - not Tapestry, since it
is a core part of the HTTP spec.
What you may be able to do, is create a javax.servlet.Filter which reads
the response from Tapestry into a stream, hopefully including the status
line - and then just re-output
We try to create a Tapestry-service that generates a Shoutcast stream. The
problem is that the shoutcast response must have a status line that reads:
ICY 200 OK
Instead, the status line we get is always:
HTTP/1.1 200 OK
Many mediaplayers (WinAmp, Xmms, iTunes) accept the header with HTTP status
