-
Notifications
You must be signed in to change notification settings - Fork 182
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
Support pathStyleAccess=false / bucket subdomains #144
Labels
Comments
afranken
added a commit
that referenced
this issue
Nov 21, 2022
BucketNameFilter will extract the bucket name from subdomain or path and add it as a request attribute for consumption in handler methods. Fixes #144
2 tasks
afranken
added a commit
that referenced
this issue
Nov 21, 2022
Trying out if this works (BucketNameFilter will take name from path), assert that bucket name is the same that is passed in the path to the handler method. Fixes #144
afranken
added a commit
that referenced
this issue
Nov 24, 2022
BucketNameFilter will extract the bucket name from subdomain or path and add it as a request attribute for consumption in handler methods. Fixes #144
afranken
added a commit
that referenced
this issue
Nov 24, 2022
Trying out if this works (BucketNameFilter will take name from path), assert that bucket name is the same that is passed in the path to the handler method. Fixes #144
afranken
added a commit
that referenced
this issue
Dec 21, 2022
BucketNameFilter will extract the bucket name from subdomain or path and add it as a request attribute for consumption in handler methods. Fixes #144
afranken
added a commit
that referenced
this issue
Dec 21, 2022
Trying out if this works (BucketNameFilter will take name from path), assert that bucket name is the same that is passed in the path to the handler method. Fixes #144
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AWS has announced to deprecate pathStyleAccess in the foreseeable future.
The S3 mock server could support that when running in Docker, with properly configured Docker network and alias settings, and then maybe checking the request for the used subdomain name.
Dynamically creating buckets won't be possible, though.
The challenge is to do that without having to duplicate the complete API controller and to provide proper testing within the Maven build.
The text was updated successfully, but these errors were encountered: