Using Spring Boot 2.1.5.RELEASE, then build a app.war, finally running in tomcat.

With tomcat, I have modified the default configuration in conf/catalina.properties org.apache.catalina.STRICT_SERVLET_COMPLIANCE=true; the default is false; its affects, you can find in this web address ;

Tomcat run with error:

Spring spring boot 2.1.5.REALSE  build war ,run in tomcat with xsd:schema  error

According the error, I find the URI in org.springframework:spring-webmvc:5.1.7.RELEASE/META-INF/spring-form.tld

Spring spring boot 2.1.5.REALSE  build war ,run in tomcat with xsd:schema  error

It is https, but not http?

But in servlet-api.jar it's http ...

Spring spring boot 2.1.5.REALSE  build war ,run in tomcat with xsd:schema  error

So , I want to know it's a bug or am I wrong !

Thank You !!!

Comment From: huang7230468

but in pring boot 2.1.3.REALSE is ok ,And it is a http

Comment From: sbrannen

The stack trace you have supplied comes from a warning.

Is your application no longer working correctly with spring-webmvc:5.1.7.RELEASE? If so, can you please provide details regarding the actual failure?

Or is the warning causing problems for you?

Regarding spring-form.tld, the location of the namespace is https://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd, but the name of the namespace has not changed. It is still http://java.sun.com/xml/ns/j2ee with HTTP instead of HTTPS.

Comment From: spring-projects-issues

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Comment From: huang7230468

@sbrannen
Use the version of spring-webmvc:5.1.7.RELEASE , With tomcat, I have modified the default configuration in conf/catalina.properties org.apache.catalina.STRICT_SERVLET_COMPLIANCE=true; Then my application can not start

Comment From: stanleynguyen

modifying https to http inside spring.tld and spring-form.tld works for me. However, is there any workaround at the moment without editing source of the jar?

Comment From: rstoyanchev

Closing due to inactivity. There was a comprehensive effort to replace http URLs for security reasons. This issue here sounds like something that might need to be addressed on the Tomcat side.