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

🐛 🚧 Redirect proxy server to prevent CORS #214

Conversation

treasurechic
Copy link
Contributor

ℹ Overview

📝 Related Issues

closes #213

@vercel
Copy link

vercel bot commented May 11, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
algodex-mailbox ✅ Ready (Inspect) Visit Preview May 11, 2022 at 8:22PM (UTC)

@treasurechic treasurechic marked this pull request as draft May 11, 2022 20:19
@PhearZero
Copy link
Contributor

This is being blocked by the provider(PureStake), the only solution currently is to launch our own indexer with the notes prefix enabled.

It's failing on CORs because of the 400 error has CORs enabled making it misleading. The other endpoints are valid and allow public access

Error: Network request error. Received status 400: provided disabled parameter: note-prefix

@treasurechic
Copy link
Contributor Author

This is being blocked by the provider(PureStake), the only solution currently is to launch our own indexer with the notes prefix enabled.

It's failing on CORs because of the 400 error has CORs enabled making it misleading. The other endpoints are valid and allow public access

Error: Network request error. Received status 400: provided disabled parameter: note-prefix

@PhearZero How about the frontend makes a call to our backend and our backend makes the call to the purestake directly on the back and return the response to the frontend?.....I think the CORs might be prevented that way.

@PhearZero
Copy link
Contributor

How about the frontend makes a call to our backend and our backend makes the call to the purestake directly on the back and return the response to the frontend?.....I think the CORs might be prevented that way.

@treasurechic The notes field search is disabled from PureStake, there is nothing we can do right now to resolve it. We would need to launch our own Algorand Indexer to support the notes field.

@treasurechic
Copy link
Contributor Author

How about the frontend makes a call to our backend and our backend makes the call to the purestake directly on the back and return the response to the frontend?.....I think the CORs might be prevented that way.

@treasurechic The notes field search is disabled from PureStake, there is nothing we can do right now to resolve it. We would need to launch our own Algorand Indexer to support the notes field.

Ohh....I understand that now

@atrefonas atrefonas closed this May 16, 2022
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

Successfully merging this pull request may close these issues.

🐛 Fix: CORS error on transaction history endpoint
3 participants