The application we're developing has a suite of web services (RESTful, Swagger-based), and at least one of them can accept a pound sign ("#") as a URL parameter.

Several months ago, with the application and all of its services running on Tomcat 7, it was accepting a plain, naked # in the URL. Now, running on Tomcat 8.5, it's returning an error message ("HTTP/1.1 400").

The developer (in a different time zone) has explained about URL-encoding, but hasn't said whether there was anything in his code to make it stop tolerating the naked # sign.

Did the change from Tomcat 7 to Tomcat 8.5 have anything to do with this? And if so, are there any other common ASCII characters that used to be accepted as characters, but now have to be URL-encoded?


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to