-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: rack/rack
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.0.9.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: rack/rack
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.0.12
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 10 commits
- 10 files changed
- 5 contributors
Commits on Mar 20, 2024
-
Return empty when parsing a multi-part POST with only one end delimiter. Fixed: #2103 Sending the following request in a browser generates a request with with only one end delimiter. ```javascript const formData = new FormData(); const request = new Request('http://127.0.0.1:8080/', { method: 'POST', body: formData, }); const response = fetch(request); ``` ``` curl 'http://127.0.0.1:8080/' \ -H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryR1LC4tR6ayskIXJm' \ --data-raw $'------WebKitFormBoundaryR1LC4tR6ayskIXJm--\r\n' ``` This request is not compliant RFC7578, but is generated by major browsers such as FireFox and Chrome. Supporting this request will cause the multipart parser to return an empty value.
Configuration menu - View commit details
-
Copy full SHA for f856dbd - Browse repository at this point
Copy the full SHA f856dbdView commit details -
Configuration menu - View commit details
-
Copy full SHA for d3c545e - Browse repository at this point
Copy the full SHA d3c545eView commit details
Commits on Apr 22, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4da4e4a - Browse repository at this point
Copy the full SHA 4da4e4aView commit details
Commits on May 9, 2024
-
Backport #2062 to 3-0-stable (#2176)
* Do not allow BodyProxy to respond to to_str, make to_ary call close See rack/rack-test#335 for an example where allowing BodyProxy to respond to to_str (when provided an invalid rack body) complicated debugging. Call BodyProxy#close if BodyProxy#to_ary is called, as not doing so violates SPEC. * Changelog for #2062 --------- Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Configuration menu - View commit details
-
Copy full SHA for b9a60d9 - Browse repository at this point
Copy the full SHA b9a60d9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3b5cef7 - Browse repository at this point
Copy the full SHA 3b5cef7View commit details -
Configuration menu - View commit details
-
Copy full SHA for efe2a9d - Browse repository at this point
Copy the full SHA efe2a9dView commit details -
Remove Ruby 3.0 from test-external (#2177)
v0.5.1 of `protocol-rack` dropped support for Ruby 3.0
Configuration menu - View commit details
-
Copy full SHA for cf26ef1 - Browse repository at this point
Copy the full SHA cf26ef1View commit details
Commits on Jul 2, 2024
-
Synchronise 3-1-stable changelog with 3-0-stable.
Configuration menu - View commit details
-
Copy full SHA for e1376a5 - Browse repository at this point
Copy the full SHA e1376a5View commit details
Commits on Feb 12, 2025
-
Configuration menu - View commit details
-
Copy full SHA for d00d195 - Browse repository at this point
Copy the full SHA d00d195View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5459513 - Browse repository at this point
Copy the full SHA 5459513View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.0.9.1...v3.0.12