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

Server just returning 302 Found when uploading from cross-server #40

Open
Zxurian opened this issue Mar 27, 2018 · 3 comments
Open

Server just returning 302 Found when uploading from cross-server #40

Zxurian opened this issue Mar 27, 2018 · 3 comments

Comments

@Zxurian
Copy link

Zxurian commented Mar 27, 2018

I have two servers setup, A & B, with urls A & B pointing to the servers respectively. Both servers contain the same codebase.

If I go directly to url B on server B, and initiate a flowjs upload, everything works as expected.
If I go to url A (server A), but have the target url for the flowjs be url B (server B), instead of uploading the file, I just got three requests with an empty response but a 302 Found Header.

Any insight on getting this working cross-server without me digging into the codebase?

All SSL's are wildcard, and sessions are cross-domain to a redis server.

@AidasK
Copy link
Member

AidasK commented Mar 27, 2018

Are you redirecting to different domain/subdomain? Have you checked CORS? How about "Access-Control-Allow-Origin: *"?

@Zxurian
Copy link
Author

Zxurian commented Mar 27, 2018

Yes, I am redirecting to a different subdomain. I have the following headers set on both server A & B

Access-Control-Allow-Headers | Authorization, Origin, X-Reque…ed-With, Content-Type, Accept
Access-Control-Allow-Methods | GET, POST, OPTIONS
Access-Control-Allow-Origin | url A

It could be a CORS issue since I am just experimenting with it. When the initial flow AJAX request is made, it' issuing an OPTIONS request, instead of the normal POST request when it's on the same server, and a 302 Found is responding.

@mitmelon
Copy link

mitmelon commented Apr 2, 2023

Yes, I am redirecting to a different subdomain. I have the following headers set on both server A & B

Access-Control-Allow-Headers | Authorization, Origin, X-Reque…ed-With, Content-Type, Accept
Access-Control-Allow-Methods | GET, POST, OPTIONS
Access-Control-Allow-Origin | url A

It could be a CORS issue since I am just experimenting with it. When the initial flow AJAX request is made, it' issuing an OPTIONS request, instead of the normal POST request when it's on the same server, and a 302 Found is responding.

Did you later found a solution to this because am also facing same issues

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

3 participants