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.

Sign up for GitHub

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

Jump to bottom

Fetch directly from azure APi instead of CORS proxy #18

Closed
OLILHR opened this issue Dec 21, 2024 · 1 comment · Fixed by #35
Closed

Fetch directly from azure APi instead of CORS proxy #18

OLILHR opened this issue Dec 21, 2024 · 1 comment · Fixed by #35

Comments

@OLILHR
Copy link
Member

OLILHR commented Dec 21, 2024

currently, the calendar takes a few seconds to load; same applies to the download waiting time. if i had to guess, it might be related to the way the data is fetched via the azure functions via a CORS proxy. maybe there is a better way to adapt the legacy JS (which loads the data instantly).
@OLILHR
Copy link
Member Author

OLILHR commented Jan 7, 2025 •
edited
Loading

fixed by adding corresponding URLs to API/CORS in azure portal
image

@OLILHR OLILHR linked a pull request Jan 7, 2025 that will close this issue
chore: replace CORS proxy using direct fetch #35
Merged
@OLILHR OLILHR closed this as completed in #35 Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: replace CORS proxy using direct fetch Hochfrequenz/fristenkalender-frontend
1 participant
@OLILHR