-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fetch node doesn't respect "raw" checkbox #2411
Comments
I'm not all that clear about this one; I think @dglazkov will have a view on it, though. |
This should totally "just work", as of three weeks ago or so. I wonder if googleplex visual editor is running an older version? |
Now that I try again from scratch I'm getting an internal exception, both on googleplex and on the external site: very simple example board: |
Yup, can reproduce. The error is hidden away in DevTools:
If I change the URL protocol to https, I get another error:
Good bug! We need to add a bit more graceful error handling to |
... it's respecting CORS? Gosh. Well, good to know - guess I need to come up with a completely different plan for how to fetch web content. |
Check out this one as a possible strategy: |
That was the very first thing I tried, and then swiftly abandoned when it immediately started spitting out quota exceeded errors. (I was only calling it a couple times so it wasn't me.) Currently have an internal solution half-built, hope to get it up and running next week, but getting arbitrary web content feels like a base capability that should be better supported by the platform. |
The fetch node doesn't seem to respect the "raw" checkbox and always tries to parse what it gets as JSON. I'm trying to use it to just grab a vanilla webpage's html and it's spitting out "Internal Exception: SyntaxError: Unexpected token '<', " <hea"... is not valid JSON }" even with raw checked.
The text was updated successfully, but these errors were encountered: