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

Intercepter-logging: wrong protocol for real server using http2 #3395

Closed
1 task done
Tvede-dk opened this issue Jun 9, 2017 · 2 comments
Closed
1 task done

Intercepter-logging: wrong protocol for real server using http2 #3395

Tvede-dk opened this issue Jun 9, 2017 · 2 comments
Labels
bug Bug in existing code
Milestone

Comments

@Tvede-dk
Copy link

Tvede-dk commented Jun 9, 2017

What kind of issue is this?

  • Bug report.

Summary

Create a request to a http2 capable server, fire it off, and inspect the Response (there the protocol is set to "h2" as expected), and watch the interceptor log "http/1.1".

  • Write a failing test:
    its properly more a definition of using http1.1 as a default value, instead of saying "we do not know".
@swankjesse
Copy link
Member

Failing test?

@swankjesse swankjesse added the needs info More information needed from reporter label Jun 10, 2017
@swankjesse
Copy link
Member

Looking further, this is a problem with how the logging interceptor should behave when the protocol version is unknown? Yeah, we can fix this.

@swankjesse swankjesse added bug Bug in existing code and removed needs info More information needed from reporter labels Jun 10, 2017
@swankjesse swankjesse added this to the 3.9 milestone Jul 31, 2017
swankjesse added a commit that referenced this issue Aug 30, 2017
swankjesse added a commit that referenced this issue Aug 30, 2017
swankjesse added a commit that referenced this issue Aug 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug in existing code
Projects
None yet
Development

No branches or pull requests

2 participants