We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Annotation ingress.pomerium.io/allow_spdy: "true" doesn't work
ingress.pomerium.io/allow_spdy: "true"
https://httpbin.localhost.pomerium.io
IC v0.220
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: httpbin annotations: ingress.pomerium.io/pass_identity_headers: "true" ingress.pomerium.io/allow_spdy: "true" ingress.pomerium.io/allow_any_authenticated_user: "true" spec: ingressClassName: pomerium rules: - host: 'httpbin.localhost.pomerium.io' http: paths: - path: / pathType: Prefix backend: service: name: httpbin port: name: http
# Paste your logs here. # Be sure to scrub any sensitive values
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I believe the way it works is is the connecting party wants to use SPDY, it will be allowed. I think browsers want HTTP/2
the only place where it was used is for self-hosted kubernetes clusters, in order to reach their internal API from the outside.
Sorry, something went wrong.
To confirm, we need a simple example SPDY app to test against.
Context -- we added this for k8s as @wasaga mentioned.
No branches or pull requests
What happened?
Annotation
ingress.pomerium.io/allow_spdy: "true"
doesn't workWhat did you expect to happen?
How'd it happen?
ingress.pomerium.io/allow_spdy: "true"
to the ingress file and run Pomeriumhttps://httpbin.localhost.pomerium.io
in the browserThe HTTP/2 protocol is present instead of spdy
What's your environment like?
IC v0.220
What's your config.yaml?
What did you see in the logs?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: