-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
newer tomcat rejects [:] #209
Comments
Thanks for the heads up. I'll look at this shortly. (It's Thanksgiving week here in the US). |
I see how this can give you problems, but is there anything specific to docker here? If you would like to adjust It seems like this could be a point of clarification in the TDS documentation, if it is not already. Ping @lesserwhirls. |
We discussed this issue over on the THREDDS issue tracker at Unidata/thredds#1144, although it's a bit lengthy and has some red herrings on our part. Perhaps most relevant is this particular comment: Unidata/thredds#1144 (comment) We decided that unless there is an explicit need for a server to allow unencoded urls, we suggest not using the There were some issues with the opendap html page / javascript not encoding the url properly before submitting a request, and this has been fixed in beta6 of 5.0 and the soon-to-be-released 4.6.12. Interestingly enough, when using an Apache server as a front-end to Tomcat, the illegal characters are handled without issue. This is the setup we use at Unidata, and so we had no idea there was an issue...I expect Apache will start disallowing these too at some point soon. |
Unless, there are objections, I am going to close this issue as it relates more to the core TDS project than this docker container. In addition, it was discussed more recently in the 4.6.13 release notes. |
Ugh. I just ran into this issue myself and as this docker container does not use Apache as the front end, I think, at the very least, it needs to be better documented and any example |
@julienchastang any chance you re-visit this and make a "working" axiom-data-science/docker-erddap@32ba572#diff-4acbaad6af43f602bbb598fba00d43e0R72-R73 |
Thanks for mentioning this Kyle. I agree it would be much easier since I don't like the idea of editing the server.xml inside the container. I thinking having users maintain their own server.xml might get messy, and really other than the relaxed characters setting, I never touch the server.xml |
Running this inside the container (e.g. in
|
We will still need these, right?
|
Is something like this what you have in mind Unidata/tomcat-docker#69? Slight variation of axiom-data-science/docker-erddap@32ba572#diff-4acbaad6af43f602bbb598fba00d43e0R72-R73 with the |
Closing with Unidata/tomcat-docker#69. Let me know if there are any additional issues. |
Historically, thredds supports opendap subsetting urls including syntax with [:]. Recent versions of tomcat reject this by default.
See: https://groups.google.com/a/opendap.org/forum/#!msg/support/ixTqhDXoLZQ/IT0lvZQ7CAAJ
https://stackoverflow.com/questions/41053653/tomcat-8-is-not-able-to-handle-get-request-with-in-query-parameters
https://stackoverflow.com/questions/50361171/how-to-allow-character-in-urls-for-tomcat-8-5
For unidata I think there are two actions:
Other characters may also be in scope. I just hit the problem with opendap subsetting ascii response with 5.0beta5
The text was updated successfully, but these errors were encountered: