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

A user can request a single movie multiple times with auto-approve #705

Closed
wastingaeons opened this issue Jan 20, 2021 · 9 comments
Closed

Comments

@wastingaeons
Copy link

Describe the bug
A user with auto-approve movie can create duplicate requests. Does not appear to affect auto-approve TV nor requests needing admin approval.

What version of Overseerr are you running?
develop-2bfab5e99c04709a1ed45bf30748e4fb5ac95f72

To Reproduce

  1. On discover or search page hover and request a movie with auto-approve permissions.
  2. Click on movie poster to go to details.
  3. Hit back button in browser.
  4. Observe you can hover over movie and request again.
  5. Observe duplicates on /requests page

Expected behavior
Duplicates should not be allowed.

Screenshots
Untitled

Desktop (please complete the following information):

  • OS: Win10
  • Browser: Chrome
  • Version: 87

Smartphone (please complete the following information):

  • Device: OnePlus 6T
  • OS: Android 11
  • Browser: Chrome
  • Version: 87
@wastingaeons
Copy link
Author

Issue persists as described on develop-a3fe4e6321c3480ac0463ed26e0d9be25d88352f

@sct sct reopened this Jan 29, 2021
@sct
Copy link
Owner

sct commented Jan 29, 2021

Will take a look.

@sct sct removed the released label Jan 30, 2021
Repository owner deleted a comment from github-actions bot Jan 30, 2021
@TheCatLady
Copy link
Collaborator

Hi @wastingaeons, are you still experiencing this issue? I was investigating this just now but could not repro the problem.

@wastingaeons
Copy link
Author

@TheCatLady I can replicate it consistently on Win10 Chrome & Edge on the latest dev (57c00c1). Strangely I can no longer repro from my phone's chrome.

capture.mp4

Here's a video of it in action in an incognito Chrome window.

@TheCatLady
Copy link
Collaborator

@wastingaeons Thanks for following up! I think that perhaps it's a browser caching issue, since we hide the request button when there is an existing request. In your video, you can also see it disappear and only reappear when you press "back."

That said, we shouldn't actually add a duplicate request if one already exists. I will take a look at this later today 🙂

@TheCatLady
Copy link
Collaborator

@wastingaeons Hi again, could you see if you're able to repro the issue in Incognito mode? Also, do you have Overseerr behind a reverse proxy? I've been discussing this with the other devs, and we suspect this is a browser caching issue of some sort.

@wastingaeons
Copy link
Author

wastingaeons commented Feb 19, 2021

Yes, the video is from a fresh incognito window.

Aha! It is behind a reverse proxy and I am unable to repro from accessing Overseerr directly.

Edit: Reverse proxy is nginx with LS.io's Swag. Probably outside the scope of Overseer, but like you mentioned, OS shouldn't allow duplicates =)

@TheCatLady
Copy link
Collaborator

Aha! It is behind a reverse proxy and I am unable to repro from accessing Overseerr directly.

Ah, bingo! Closing this issue now since it is unrelated to Overseerr itself. Thanks again for the quick follow-up responses!

@TheCatLady
Copy link
Collaborator

Yes, the video is from a fresh incognito window.

Aha! It is behind a reverse proxy and I am unable to repro from accessing Overseerr directly.

Edit: Reverse proxy is nginx with LS.io's Swag. Probably outside the scope of Overseer, but like you mentioned, OS shouldn't allow duplicates =)

We actually already added a check to prevent duplicates, but I think that your reverse proxy may be causing issues and preventing the initial request from going through immediately. I am also using SWAG but could not reproduce the problem. I suggest checking your SWAG and Overseerr proxy configurations, and seeking help from the appropriate support channels for SWAG if you still experience issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants