-
Notifications
You must be signed in to change notification settings - Fork 71
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
[3.2] response to disallowed host #996
Conversation
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.
Can you add a test case for this.
|
||
if cluster.launch(dontBootstrap=True, loadSystemContract=False) is False: | ||
if cluster.launch(dontBootstrap=True, loadSystemContract=False, specificExtraNodeosArgs = {0: "--http-validate-host true"}) is False: |
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.
Do you really need --http-validate-host true
here? It's the default.
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.
Yes, I have to. Somewhere in the TestHarness changed it to false.
Line 362 in 1a8d88f
http-validate-host = false |
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.
ah okay, it's interesting because you can't --http-validate-host true --http-validate-host true
nor
http-validate-host = true
http-validate-host = true
But you can http-validate-host = true
& --http-validate-host true
This PR fixes the problem where HTTP plugin doesn't response to requests with disallowed HTTP HOST header.
Resolve IS #859