-
Notifications
You must be signed in to change notification settings - Fork 8
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
Customisable API path #57
Comments
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
to vagaerg/s3-proxy
that referenced
this issue
Jun 20, 2024
vagaerg
added a commit
that referenced
this issue
Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is tangentially related to #23 as it also deals with configuration
The API path for the S3 resource and the STS resource is hardcoded: https://github.com/trinodb/s3-proxy/blob/83e31e95311a09923beff7b332797fb76e123bcd/trino-s3-proxy/src/main/java/io/trino/s3/proxy/server/rest/TrinoS3ProxyResource.java#L34
We should be able to configure it so the proxy could live at the root if needed, or under different paths.
The text was updated successfully, but these errors were encountered: