-
Notifications
You must be signed in to change notification settings - Fork 61
fix accept header handling when client sends no accept header #134
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| Changelog | ||
| ========= | ||
|
|
||
| 1.1.2 | ||
| ----- | ||
|
|
||
| * **2014-11-17** Fixed documentation for user context varnish configuration to also work when | ||
| client omits the `Accept` HTTP header. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| deny from all | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,6 +27,10 @@ abstract class UserContextTestCase extends VarnishTestCase | |
| */ | ||
| abstract protected function assertContextCache($hashCache); | ||
|
|
||
| /** | ||
| * Sending requests without an Accept: header so none should arrive at the | ||
| * backend for the actual request. | ||
| */ | ||
| public function testUserContextHash() | ||
| { | ||
| $response1 = $this->getResponse('/user_context.php', array(), array('cookies' => array('foo'))); | ||
|
|
@@ -64,6 +68,17 @@ public function testUserContextHash() | |
| $this->assertHit($headResponse2); | ||
| } | ||
|
|
||
| public function testAcceptHeader() | ||
| { | ||
| $response1 = $this->getResponse( | ||
| '/user_context.php?accept=text/plain', | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is just a weird hack to not need more backend php files for the testing - the permutations would lead to many files. |
||
| array('Accept' => 'text/plain'), | ||
| array('cookies' => array('foo')) | ||
| ); | ||
| $this->assertEquals('foo', $response1->getBody(true)); | ||
|
|
||
| } | ||
|
|
||
| public function testUserContextUnauthorized() | ||
| { | ||
| try { | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is for better error reporting. i think it makes sense here but in any system running anywhere it would be dangerous to blindly echo $_SERVER and $_GET values. should we put a .htaccess in tests/ to prevent execution if somebody manages to expose his vendor directory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we’re doing this in more places, e.g.
negotation.php. Could you add a.htaccessthat protects the fixtures but still works when running our tests through Apache?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added .htaccess in tests root directory