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

chore: merge main to develop #14

Merged
merged 4 commits into from
May 7, 2024
Merged

chore: merge main to develop #14

merged 4 commits into from
May 7, 2024

Conversation

alfetopito
Copy link
Contributor

Summary

Merge latest main to develop

alfetopito added 3 commits May 1, 2024 05:55
* feat: add coingeckoProxy

* chore: add fastify/caching dependency

* feat: add request caching

* fix: only cache successfull responses from proxy origin

* chore: improve logging

* feat: set our own cache-control header

* chore: delete set-cookie header

* chore: rename local header from cache-hit to x-proxy-cache and leave it in the reply

* Revert "chore: rename local header from cache-hit to x-proxy-cache and leave it in the reply"

This reverts commit 71ecd72.

* fix: prevent content-length header mismatch errors

* fix: do not fwd accept-encoding header, as I'm not able to deal with encoded response

* chore: attempt at caching only after response is sent

* chore: try a different way to decorate

* Revert "chore: try a different way to decorate"

This reverts commit 31672a6.

* Revert "chore: attempt at caching only after response is sent"

This reverts commit b2dd0eb.

* feat: coingecko proxy without server side caching (#11)

* feat: remove server side caching

* chore: remove fastify-caching

* chore: undici config still required

* fix: type on cdn-cache-control value

* feat: add coingecko api key (#12)

* feat: add coingecko api key to proxy requests

* fix: remove `simple` prefix as it's part of coingecko's path

* chore: temporarily change to pro-api since the key is set to "pro"

* chore: add COINGECKO_PROXY_UPSTREAM as optional env var
* refactor: move coingeckoProxy to proxies/coingecko

* refactor: move proxy to proxies/tokens and keep proxy for awhile

* chore: add permanent redirect rather than re-exporting same path

* Revert "chore: add permanent redirect rather than re-exporting same path"

This reverts commit 246c27a.

graphql-request doesn't seem able to handle redirects natively:
https://stackoverflow.com/questions/78015439/follow-redirects-setting-for-aws-appsync#comment137542218_78015439

Thus, reverting the redirect change
@alfetopito alfetopito self-assigned this May 7, 2024
Copy link

vercel bot commented May 7, 2024

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

Name Status Preview Updated (UTC)
cow-web-services ❌ Failed (Inspect) May 7, 2024 8:29am

Copy link

socket-security bot commented May 7, 2024

@anxolin anxolin merged commit 6b9e8c6 into develop May 7, 2024
2 of 3 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants