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

Don't add Accept-Range header on unsafe HTTP requests #13200

Closed
wants to merge 2 commits into from
Closed

Don't add Accept-Range header on unsafe HTTP requests #13200

wants to merge 2 commits into from

Conversation

jaytaph
Copy link
Contributor

@jaytaph jaytaph commented Jan 2, 2015

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #12556
License MIT
Doc PR N/A

@@ -208,6 +208,24 @@ public function testDeleteFileAfterSend()
$this->assertFileNotExists($path);
}

/**
*
*/
Copy link
Member

Choose a reason for hiding this comment

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

this empty phpdoc should be removed

@jaytaph
Copy link
Contributor Author

jaytaph commented Jan 2, 2015

@stof fixed.

@stof
Copy link
Member

stof commented Jan 3, 2015

👍

To maintainers: this should be merged in older branches as it is a bugfix

@fabpot
Copy link
Member

fabpot commented Jan 3, 2015

Thank you @jaytaph.

fabpot added a commit that referenced this pull request Jan 3, 2015
…taph)

This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes #13200).

Discussion
----------

Don't add Accept-Range header on unsafe HTTP requests

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #12556
| License       | MIT
| Doc PR        | N/A

Commits
-------

24a287f Don't add Accept-Range header on unsafe HTTP requests
@fabpot fabpot closed this Jan 3, 2015
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