You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.
Again, thank you for this fine software - I love it! I've been using globalFetch to read index.html pages, which has led me to discover that redirect errors (such as 301) do not automatically redirect (like the Fetch API normally does.) This is because Beaker doesn't use the browser's fetch call - it uses Node's http.request, throwing away many of the options which are passed in.
It seems that a Fetch polyfill library could bring this to parity - but wanted to ask here if it would be appropriate to submit a pull request like that. Ciao!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Again, thank you for this fine software - I love it! I've been using globalFetch to read index.html pages, which has led me to discover that redirect errors (such as 301) do not automatically redirect (like the Fetch API normally does.) This is because Beaker doesn't use the browser's
fetch
call - it uses Node'shttp.request
, throwing away many of the options which are passed in.It seems that a Fetch polyfill library could bring this to parity - but wanted to ask here if it would be appropriate to submit a pull request like that. Ciao!
The text was updated successfully, but these errors were encountered: