Thanks folks...
My goal is to deliver PDFs back to an automated process from an already
existing Web application (it's internal so security isn't an issue), which
has a Struts front end for the UI. A simple HTTP GET request seems to fit
the bill.
Once the automated process has been written the
FWIW, I did a quick dispatcher result hack that allows setting the HTTP
result; we use it for Ajax calls (not 404s). I'll probably fold that
property back into S2, but like Wes said it's not so handy for 404s.
Dave
Wes Wannemacher wrote:
404 is a tricky header... Most of the time, you really
404 is a tricky header... Most of the time, you really don't want to
send content along with an http header, think of redirects, etc. If
you want some app-specific behavior, I would try to fit it into your
app rather than trying to munge headers. In the case of redirects,
when you see content it is
Thanks Wes.
The 'documentation' (it's very limited) gives the impression that you can
specify an error message when using the errorMessage parameter with the
error parameter, and even being able to pick up a message from the value
stack using an OGNL expression.
Having looked at what is returne
The HTTP Header result type doesn't really have the ability to write
content. You could try mapping 404 in your web.xml, then use the http
header result type in conjunction with the 404 mapping in web.xml
(never tried it, so let us know if that works).
-Wes
On Wed, Sep 2, 2009 at 5:35 AM, Mark Ro
5 matches
Mail list logo
