You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2022/01/07 00:09:56 UTC
[GitHub] [trafficserver] shinrich opened a new issue #8587: HTTP/2 does not work with outbound transparent
shinrich opened a new issue #8587:
URL: https://github.com/apache/trafficserver/issues/8587
Once I fixed issue #7525, I could pass traffic for HTTP and HTTPS HTTP/1.1 with the certifier plugin. But for HTTP/2 traffic I would get a 500 response. Looking at the debug messages, it appeared that the HttpSM was very insistent about doing a DNS lookup on the domain.
Eventually tracked it down to the fact that the accept object transparent flags were not being propagated properly to the Http2Streams. I am putting up a PR that fixes the issue, but perhaps in not the most beautiful way.
This is all working on the 9.1.1 codebase.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] shinrich commented on issue #8587: HTTP/2 does not work with outbound transparent
Posted by GitBox <gi...@apache.org>.
shinrich commented on issue #8587:
URL: https://github.com/apache/trafficserver/issues/8587#issuecomment-1009055580
Talked with @SolidWallOfCode about my original PR. He pointed out the proxy.config.hostdb.host_file.path which fixed quite a file things. Setting it to 2 made my environment work where the gateway didn't have the same DNS access as the client. I set up PR #8593 to clean up the documentation with obsolete info and highlighted this setting.
Changed the code PR #8594 to propagate the outbound settings to the HTTP/2 stream as they are being propagated to the HTTP1 client until we can get the session-based hook solution figured out.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] shinrich commented on issue #8587: HTTP/2 does not work with outbound transparent
Posted by GitBox <gi...@apache.org>.
shinrich commented on issue #8587:
URL: https://github.com/apache/trafficserver/issues/8587#issuecomment-1008956365
After some more testing, my original fix only worked if http caching was enabled. There was a different path followed if caching was disabled. Centralized the fix a bit more to address both caching and non-caching cases. Getting ready to set up PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] shinrich closed issue #8587: HTTP/2 does not work with outbound transparent
Posted by GitBox <gi...@apache.org>.
shinrich closed issue #8587:
URL: https://github.com/apache/trafficserver/issues/8587
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] shinrich edited a comment on issue #8587: HTTP/2 does not work with outbound transparent
Posted by GitBox <gi...@apache.org>.
shinrich edited a comment on issue #8587:
URL: https://github.com/apache/trafficserver/issues/8587#issuecomment-1009055580
Talked with @SolidWallOfCode about my original PR. He pointed out the proxy.config.http.use_client_target_addr setting which fixed quite a few things. Setting it to 2 made my environment work where the gateway didn't have the same DNS access as the client. I set up PR #8593 to clean up the documentation with obsolete info and highlighted this setting.
Changed the code PR #8594 to propagate the outbound settings to the HTTP/2 stream as they are being propagated to the HTTP1 client until we can get the session-based hook solution figured out.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org