-
Notifications
You must be signed in to change notification settings - Fork 218
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
Clarify request test host settings #951
Conversation
@@ -106,19 +106,23 @@ that support the following members: | |||
the query string (for example, "/foo/bar"). | |||
* - host | |||
- ``string`` | |||
- The host / endpoint provided to the client (for example, "example.com"). | |||
- The host or endpoint provided as input to the client (for example, |
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.
What about the server? Is this client only? Is the delta between host
and resolvedHost
ignored by servers implementing protocol tests?
``host`` MAY contain a path to indicate a base path from which each | ||
operation in the service is appended to. For example, given a ``host`` | ||
of ``example.com/foo/bar`` and an operation path of ``/MyOperation``, | ||
the resolved host of the operation is ``example.com`` and the resolved | ||
path is ``/foo/bar/MyOperation``. | ||
* - resolvedHost | ||
- ``string`` | ||
- The host / endpoint that the client should send to, not including the | ||
path or scheme (for example, "prefix.example.com"). | ||
- The expected host that the client must send to, not including the path |
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.
Is this what goes in the Host
header, which means server implementations would look at Host
, right?
f187e93
to
ae3e2e1
Compare
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.