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

Was the response data hijacked after ProductPage requested Reviews? #40670

Closed
liuqi-sun opened this issue Aug 26, 2022 · 4 comments
Closed

Was the response data hijacked after ProductPage requested Reviews? #40670

liuqi-sun opened this issue Aug 26, 2022 · 4 comments
Labels
lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while

Comments

@liuqi-sun
Copy link

Was the response data hijacked after ProductPage requested Reviews? Does the response data go directly to ProductPage, or is it hijacked to Envoy? Looking at the iptable rules, I feel that it is hijacked to 15001,15001 how to handle the response data, I do not understand.

@zirain
Copy link
Member

zirain commented Aug 26, 2022

@liuqi-sun
Copy link
Author

please checkout this blogs about how istio work: https://www.solo.io/blog/istios-networking-in-depth/ blogs in chinese: https://cloudnative.to/blog/istio-traffic-management-series-service-management-concept-theory/

That's not my concern. I'm concerned with iptables.

@liuqi-sun
Copy link
Author

Another question, when I access www.google.com through curl in Sidecar pod, is traffic hijacked to 15001? If so, what did Envoy do?

@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Nov 25, 2022
@istio-policy-bot
Copy link

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2022-08-26. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.

@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label Dec 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while
Projects
None yet
Development

No branches or pull requests

3 participants