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 wrong spec asserting headers maintain original definition #38422

Merged
merged 1 commit into from
Feb 10, 2020

Conversation

vipulnsward
Copy link
Member

This was introduced in #20559 but was wrongly asserting %w[close] to match "close" as the header value

Changes from rack/rack@d2e608e returns headers as is which makes this break.

This was introduced in rails#20559 but was wrongly asserting %w[close] to match close as the header value
@rails-bot rails-bot bot added the actionpack label Feb 9, 2020
@kaspth kaspth merged commit f3eaddb into rails:master Feb 10, 2020
@kaspth
Copy link
Contributor

kaspth commented Feb 10, 2020

Thanks @vipulnsward! Wanna take a look at the other one mentioned in #38420?

@kaspth
Copy link
Contributor

kaspth commented Feb 10, 2020

Ah, you're already looking at it 🙌

@ioquatix
Copy link
Contributor

ioquatix commented Feb 10, 2020

Also, just FYI, you definitely shouldn't be setting connection headers unless you are actually know the server will handle it correctly.

e.g. falcon will delete this header from the app response, and issue a warning.

@kaspth
Copy link
Contributor

kaspth commented Feb 10, 2020

Yep, sounds sensible 🙏

kamipo pushed a commit that referenced this pull request May 18, 2020
Fix wrong spec asserting headers maintain original definition
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants