Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Request header field Cache-Control is not allowed by Access-Control-Allow-Headers #130

Closed
hakunin opened this issue Nov 23, 2015 · 1 comment

Comments

@hakunin
Copy link

hakunin commented Nov 23, 2015

Hi, I am trying to use fake-s3 with pre-signed post and this is what I get:

screen shot 2015-11-23 at 12 58 14

Btw, I had to modify the aws-sdk-ruby to use the the correct url btw, it doesn't support the custom endpoint.
aws/aws-sdk-ruby#1012

ushatil added a commit to ushatil/fake-s3 that referenced this issue Jan 24, 2018
The issue only required modifying the Allowed-Headers,
but it seemed strange to add the ability to control
that one without being able to control the others

- Current behavior without added flags is unnaffected
- No existing assertions are changed
- Added assertions to demonstrate control of CORS Headers
@ushatil
Copy link
Contributor

ushatil commented Jan 24, 2018

Addressed this in PR #229

@jubos jubos closed this as completed in 994f7ff Jan 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants