Skip to content
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

File is blacklisted if it is attempted to be uploaded with an invalid token #2

Open
rmil opened this issue Aug 15, 2020 · 1 comment
Assignees

Comments

@rmil
Copy link
Member

rmil commented Aug 15, 2020

Effectively, you can't upload that particular file anymore until you've got a new session on the go? For a quick resolution, just open it again in incognito ensuring that you are using a valid token this time when uploading.

I'll need to research what is causing it to say no-no. But sounds like a job for later.

@rmil
Copy link
Member Author

rmil commented Aug 16, 2020

Seems like CORS is back at it again with the white vans! It looks like the Access-Control-Max-Age was being set by default by Firefox/tusd to 1 day? So I've updated nginx for the tusd reverse-proxy so hopefully any future requests with the following:
proxy_hide_header 'Access-Control-Max-Age'; add_header 'Access-Control-Max-Age' 0;
Still doesn't seem to be working with my regular Firefox although it still might have the original CORS set, but in incognito mode I was able to upload the file, remove the token and it wouldn't let me upload, got a new token which then allowed me to upload again, so hopefully it'll work.

@rmil rmil self-assigned this Aug 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant