Skip to content

Incorrect Content-Length - when using a custom api router after ssl enabled gateway #633

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

Open
abwl084 opened this issue Feb 26, 2025 · 0 comments

Comments

@abwl084
Copy link

abwl084 commented Feb 26, 2025

Routing works fine when gateway is not ssl enabled. After enabling ssl with a self signed cert I get this error:

2025-02-26 21:26:42 2025-02-26T19:26:42.734Z ERROR http-worker-70 io.trino.gateway.ha.router.ExternalRoutingGroupSelector Error occurred while retrieving routing group from external routing rules processing at https://host.docker.internal:8000/gateway
2025-02-26 21:26:42 org.eclipse.jetty.http.HttpException$RuntimeException: 500: Incorrect Content-Length 179!=61
2025-02-26 21:26:42 at org.eclipse.jetty.http.HttpGenerator.generateHeaders(HttpGenerator.java:613)
2025-02-26 21:26:42 at org.eclipse.jetty.http.HttpGenerator.generateRequest(HttpGenerator.java:206)
2025-02-26 21:26:42 at org.eclipse.jetty.client.transport.internal.HttpSenderOverHTTP$HeadersCallback.process(HttpSenderOverHTTP.java:165)
2025-02-26 21:26:42 at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:262)

I am able to call the my custom api from the gateway container with full ssl validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant