Skip to content
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

fix(boot2): Allow paths with URL-encoded slashes #454

Merged
merged 4 commits into from
Jun 17, 2019
Merged

fix(boot2): Allow paths with URL-encoded slashes #454

merged 4 commits into from
Jun 17, 2019

Conversation

avram
Copy link
Contributor

@avram avram commented Jun 5, 2019

Spring Boot 2 tightened up restrictions, but CI job names may legitimately include encoded slashes

See spinnaker/spinnaker#4477

https://spinnakerteam.slack.com/archives/C091CCWRJ/p1559269913055000

Spring Boot 2 tightened up restrictions, but CI job names may legitimately include encoded slashes

See spinnaker/spinnaker#4477
@avram
Copy link
Contributor Author

avram commented Jun 5, 2019

I would love to actually add a test for this, but none of the tests I looked at seemed to actually run requests through the Spring request handling logic (which is what is changed here) and I was hoping to limit the amount of new test boilerplate for this fix.

It would also be nice to just relax this for the specific endpoints that need it, but it's not clear that we can do that with StrictHttpFirewall.

Copy link
Contributor

@ezimanyi ezimanyi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me; would like @emjburns to look as well before merging.

@emjburns
Copy link
Contributor

LGTM

@ezimanyi ezimanyi merged commit d02914a into spinnaker:master Jun 17, 2019
@avram avram deleted the allow-encoded-slashes branch June 17, 2019 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants