Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

api should respect the request origin when processing data #137

Open
AddressXception opened this issue Nov 14, 2021 · 0 comments
Open

api should respect the request origin when processing data #137

AddressXception opened this issue Nov 14, 2021 · 0 comments

Comments

@AddressXception
Copy link
Contributor

the production environment has both a rinkeby and a mainnet chainlink node, but the api is configured to only support either prod (mainnet) or development (rinkeby) configs. we need to be able to discern between requests comingh from either of the nodes and route data accordingly. specifically, a chainlink request includes a callback response url and that response url has the name of the service in it (chainlink-rinkeby or chainlink-mainnet). depending which of those re receive, the request should route correctly. anywhere there is a check for if "API_MODE == prod" or that sort of thing we need to consider if the ocntrol flow needs to be modified to take the request origin into account

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant