tomcat7 does not log x-forwarded-for

Hello all, I currently have a problem with Tomcat7, or rather a colleague has it. Personally I would like to help him, but I can't find the error myself. We already asked the question on stackoverflow.com and got a good hint, but unfortunately no solving. So I would like to ask for help and suppor

Re: Limiting multipart file upload sizes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 3/30/20 16:51, Mark Thomas wrote: > On 30/03/2020 21:45, Christopher Schultz wrote: >> All, >> >> In my application under Tomcat 8.5.51, I have configured a >> servlet to allow multipart/form-data submissions and I have added >> this config

Re: Limiting multipart file upload sizes

On 30/03/2020 21:45, Christopher Schultz wrote: > All, > > In my application under Tomcat 8.5.51, I have configured a servlet to > allow multipart/form-data submissions and I have added this > configuration as a part of the config: > > > 1048576 > 1049600 > > > Without the

Limiting multipart file upload sizes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, In my application under Tomcat 8.5.51, I have configured a servlet to allow multipart/form-data submissions and I have added this configuration as a part of the config: 1048576 1049600 Without the section, the upload d

Re: Does Tomcat/Java get around the problem of 64K maximum client source ports?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Eric, On 3/27/20 16:39, Eric Robinson wrote: > Thanks for all the feedback, André, Christopher, and John. Let me > see if I can quickly answer everyone's comments.> Since there is a > TCB for each connection, and the OS knows which TCBs are associ

Re: R: Support with error in launcher.log

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Luigi, On 3/30/20 08:38, Luigi Tagliafierro wrote: > we have already tried to implement the legacy cookie processor but > with no result. What did you actually do? What was the actual result? I suspect that because: 1. The cookie domain is invali

R: Support with error in launcher.log

Hi, we have already tried to implement the legacy cookie processor but with no result. in the meantime we are considering some of the suggestions that have come so far, Keep help us! thanks, Luigi Da: calder Inviato: lunedì 30 marzo 2020 13:14 A: Tomcat Use

Re: Support with error in launcher.log

On Mon, Mar 30, 2020, 05:02 Luigi Tagliafierro wrote: > Hi everybody, > > we are experiencing an error : The bitbucket log > (/var/atlassian/bitbucket_home/log/launcher.log) constantly repeats this > error: > > "java.lang.IllegalArgumentException: An invalid domain > [.code.doxee.com] was spec

Re: Support with error in launcher.log

Hi, We've had this error and it turned out to be due to the cookie processor. According to RFC6265, the domain attribute of the cookie must not start with a dot, so the new cookie processor rejects those cookies. Either remove the starting dot from the domain attribute or use the legacy cookie pro

Re: Support with error in launcher.log

Hi, On Mon, Mar 30, 2020 at 1:02 PM Luigi Tagliafierro wrote: > Hi everybody, > > we are experiencing an error : The bitbucket log > (/var/atlassian/bitbucket_home/log/launcher.log) constantly repeats this > error: > > "java.lang.IllegalArgumentException: An invalid domain [.code.doxee.com] > w