Thanks, I assumed reload was more something like undeploy followed by
deploy.
On Sat, Mar 29, 2014 at 4:42 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Brendan,
>
> On 3/28/14, 9:21 PM, Brendan Mil
Using the tasks from the example ant script at:
http://tomcat.apache.org/tomcat-8.0-doc/appdev/build.xml.txt
I have can deploy and undeploy from ant. However, the "reload" task doesn't
seem to do anything.
I make changes to java and html files, run "ant reload" which triggers the
reload task. Ant
t-util.jar.
The user needs the manager-script role for deploy to succeed. The tutorial
doesn't mention this.
Overall the appdev tutorial is pretty problematic because it doesn't really
include a complete example and seems to have kind of random organization.
On Fri, Mar 28, 2014 at 4:4
I was going through the tomcat docs and trying to use the default build.xml
file provided by the appdev tutorial to deploy my war to tomcat.
Example build.xml:
http://tomcat.apache.org/tomcat-8.0-doc/appdev/build.xml.txt
However, when I use the deploy task I always get
a java.lang.NoClassDefFound
equest, response);
> >
> > resp.setHeader("Cache-Control",
> > "must-revalidate, max-age=0, post-check=0,
> > pre-check=0");
> > }
> >
> > Programmatically I can see the header is null.
> >
> > Has the content already been sent to the web browser after
> chain.doFilter?
> > If so, is there a way to delay sending data to the browser? I need to
> > inspect the status code in the response before setting my header (to
> > prevent 404's from being cached).
> >
> > Thanks,
> > Brendan Miller
>
>
ammatically I can see the header is null.
Has the content already been sent to the web browser after chain.doFilter?
If so, is there a way to delay sending data to the browser? I need to
inspect the status code in the response before setting my header (to
prevent 404's from being cached).
Thanks,
Brendan Miller
Currently, I have a filter that sets some cache control headers. I need to
change these cache control headers in the case of a non-successful
response, such as a 404.
Unfortunately, when I check HttpServletReponse.getStatus() in the in my
doFilter method, it always reports 200 even if actually a 4
