-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 6/29/20 12:22, Christopher Schultz wrote:
> I believe I have determined the cause (or at least the fix) for
> this:
>
> Despite the mod_proxy_ajp documentation, it is using packets
> larger than 8192 bytes.
>
> Setting this on the Tomcat re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I believe I have determined the cause (or at least the fix) for this:
Despite the mod_proxy_ajp documentation, it is using packets larger
than 8192 bytes.
Setting this on the Tomcat resolves the problem:
packetSize="65536"
I don't see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
This issue is apparently trivially reproducible in my dev environment.
Do I have to get a protocol-trace to get any more helpful information?
Thanks,
- -chris
On 6/24/20 10:46, Christopher Schultz wrote:
> All,
>
> On 6/24/20 10:29, Christop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 6/24/20 10:29, Christopher Schultz wrote:
> All,
>
> I'm slowly switching from mod_jk to mod_proxy_ajp and I have a
> development environment where I'm getting Bad Gateway responses
> sent to clients along with this exception in my Tomcat lo
