чт, 7 нояб. 2019 г. в 05:44, Christopher Schultz :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> All,
>
> I can't believe I'm having trouble with this, but I'm struggling with
> enabling logging.
>
> I'm experimenting with the CsrfPreventionFilter, which currently has
> zero logging at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I can't believe I'm having trouble with this, but I'm struggling with
enabling logging.
I'm experimenting with the CsrfPreventionFilter, which currently has
zero logging at all in it. So, first I modified the code to add:
+ private final
I've found the root cause.
When checking the timestamps of JSPs, the JSP engine (because it has to
access all resources via the Servlet API) requests a URL for the JSP,
opens a connection to the URL and then checks the last modified time.
This goes directly to the on-disk file.
When reading the
