Hi, On Tue, 2008-03-18 at 17:15 -0400, Christopher Schultz wrote: > You could set an <error-page> in web.xml that produces no output for > these status codes. the rest of the application serves pages visited by humans - for them we want to display error pages. (Sorry, I didn't point this out)
Only for the REST api (mapped to a specific path/url-pattern) we do not want to return these error pages but only codes. Cheers, Martin On Tue, 2008-03-18 at 17:15 -0400, Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Martin, > > Martin Grotzke wrote: > | Is there a way not to return error pages in these cases? > > You could set an <error-page> in web.xml that produces no output for > these status codes. Something like: > > <error-page> > ~ <error-code>400</error-code> > ~ <location>/path/to/zero/length/file</location> > </error-page> > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkfgMPIACgkQ9CaO5/Lv0PDuFQCgkZkgW2+MU2X+LW96TmBtIZx0 > KX0An1EyQ7MEpQ+vSzngOlgRgWf8knrq > =lkAr > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
signature.asc
Description: This is a digitally signed message part
