Re: Tomcat 9 - failed to set property [packetSize]
On 31/12/2020 16:05, valsaraj pv wrote: > Thanks for your reply Mark. > > Is packetSize property still available in http connector? I got this > warning when I added in it. That property has never been valid for an HTTP Connector for any Tomcat version. > It is possible to add this property in ajp connector but when I access via > Apache proxy, it shows connection closed. When this attribute is removed > all works fine. But this behaviour is different from Tomcat 8, where this > property worked fine with the same front end Apache proxy. Any > pointers would be appreciated. You'll need to provide your full proxy configuration from httpd and the full element(s) from Tomcat for us to be able to help you. Kind regards, Mark > > Thank you very much! > > > On Thu, 31 Dec 2020, 9:05 pm Mark Thomas, wrote: > >> On 31/12/2020 11:06, valsaraj pv wrote: >>> Hi, >>> >>> WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Connector] failed to set property [packetSize] to [65536] >>> >>> I see this warning when migrating from Tomcat 8 to 9 on JDK 8. The >> warning >>> went away when packetSize="65536" property removed. >>> >>> How to set this in Tomcat 9? >> >> packetSize is a valid attribute for the AJP Connectors in Tomcat 9. >> >> Please provide the full content of the Connector element exhibiting the >> issue. >> >> Mark >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9 - failed to set property [packetSize]
Thanks for your reply Mark. Is packetSize property still available in http connector? I got this warning when I added in it. It is possible to add this property in ajp connector but when I access via Apache proxy, it shows connection closed. When this attribute is removed all works fine. But this behaviour is different from Tomcat 8, where this property worked fine with the same front end Apache proxy. Any pointers would be appreciated. Thank you very much! On Thu, 31 Dec 2020, 9:05 pm Mark Thomas, wrote: > On 31/12/2020 11:06, valsaraj pv wrote: > > Hi, > > > > WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin > >> Match [Server/Service/Connector] failed to set property [packetSize] to > >> [65536] > > > > I see this warning when migrating from Tomcat 8 to 9 on JDK 8. The > warning > > went away when packetSize="65536" property removed. > > > > How to set this in Tomcat 9? > > packetSize is a valid attribute for the AJP Connectors in Tomcat 9. > > Please provide the full content of the Connector element exhibiting the > issue. > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat 9 - failed to set property [packetSize]
On 31/12/2020 11:06, valsaraj pv wrote: > Hi, > > WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin >> Match [Server/Service/Connector] failed to set property [packetSize] to >> [65536] > > I see this warning when migrating from Tomcat 8 to 9 on JDK 8. The warning > went away when packetSize="65536" property removed. > > How to set this in Tomcat 9? packetSize is a valid attribute for the AJP Connectors in Tomcat 9. Please provide the full content of the Connector element exhibiting the issue. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Not able to make JSESSIONID cookie secure
Did you make the changes to /conf/web.xml ? It seems you may have made them just to that specific our_app application Are you sure you are testing it correctly? Can you try https://gf.dev/http-headers-test On 31/12/20, 8:29 pm, "Amit Khosla" wrote: Thanks for reply, we did restarted server while trying. The issue is still there even after restart. On Thu, Dec 31, 2020 at 11:14 AM Darryl Lewis wrote: > > > true > true > > > > Restart the server. > > On 31/12/20, 3:50 pm, "Amit Khosla" wrote: > > Hi Team, > > > > As we are looking forward for JSESSIONID to be secure. > > > > We made changes in web.xml in tomcat/conf > > > > > > true > > true > > > > > > > > But even after the changes, we are not able to get the JSESSIONID > cookie as > secure. > > We also tried changes in web.xml of our application, i.e, > tomcat/webapps/our_app/WEB-INF/web.xml; but still we are not getting it > secure. > > > > Tomcat version we are using is 8.5.53. > > We are getting same issue on windows as well as linux machine. > > > > Can you please guide us what can be done as this is required as per > security compliance? > > > > Thanks & Regards > > Amit > > -- Thanks & Regards Amit Khosla
Tomcat 9 - failed to set property [packetSize]
Hi, WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin > Match [Server/Service/Connector] failed to set property [packetSize] to > [65536] I see this warning when migrating from Tomcat 8 to 9 on JDK 8. The warning went away when packetSize="65536" property removed. How to set this in Tomcat 9? Thanks!
Re: Not able to make JSESSIONID cookie secure
Thanks for reply, we did restarted server while trying. The issue is still there even after restart. On Thu, Dec 31, 2020 at 11:14 AM Darryl Lewis wrote: > > > true > true > > > > Restart the server. > > On 31/12/20, 3:50 pm, "Amit Khosla" wrote: > > Hi Team, > > > > As we are looking forward for JSESSIONID to be secure. > > > > We made changes in web.xml in tomcat/conf > > > > > > true > > true > > > > > > > > But even after the changes, we are not able to get the JSESSIONID > cookie as > secure. > > We also tried changes in web.xml of our application, i.e, > tomcat/webapps/our_app/WEB-INF/web.xml; but still we are not getting it > secure. > > > > Tomcat version we are using is 8.5.53. > > We are getting same issue on windows as well as linux machine. > > > > Can you please guide us what can be done as this is required as per > security compliance? > > > > Thanks & Regards > > Amit > > -- Thanks & Regards Amit Khosla
