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

[bug]: remote_api_tokens does not work with redirect #7507

Open
1 task done
keturn opened this issue Jan 2, 2025 · 0 comments
Open
1 task done

[bug]: remote_api_tokens does not work with redirect #7507

keturn opened this issue Jan 2, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@keturn
Copy link
Contributor

keturn commented Jan 2, 2025

Is there an existing issue for this problem?

  • I have searched the existing issues

Operating system

Linux

Version number

5.5.0

Browser

chrome 126

Python dependencies

No response

What happened

I can't download must-be-logged-in models from civitai.green, no matter how I set remote_api_tokens.

What you expected to happen

each request is sent with its authorization token

How to reproduce the problem

  1. put API keys for civitai\.(green|com) in remote_api_tokens
  2. grab a download URL from civitai.green, e.g. https://civitai.green/api/download/models/1227430?type=Model&format=SafeTensor
  3. give it to the Add Model location

Additional context

I am not entirely sure I have this right, but what I think is happening is that

  1. the request with authz token goes to civitai.green/api; it responds with 307 redirect to civitai.com/api.
  2. model manager follows the redirect, but does not check to see if it should send a token to the new location.
@keturn keturn added the bug Something isn't working label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant