Skip to content
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.

Etag and 302 errors with playstation #17

Open
gcollet opened this issue May 12, 2018 · 1 comment
Open

Etag and 302 errors with playstation #17

gcollet opened this issue May 12, 2018 · 1 comment

Comments

@gcollet
Copy link

gcollet commented May 12, 2018

Hi,
I got 302 errors and etag mismatch when trying to use lan-cache to cache playstation games.
Do you have an idea if we can correct this easily? Or is it more complicated feature that need to be implemented or tested?

Thanks

@RyanEwen
Copy link
Owner

It sounds like an NGINX config issue for that specific service. Unfortunately I don't have a PlayStation to try and fix this. If you come across another cacher that also uses NGINX and works for this, let me know and I might be able to spot the difference needed to fix it.

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