Skip to content

Conversation

iainbeeston
Copy link
Contributor

There's a bug where if you pass a string as data and it looks like a
URI, we try to parse it and load the data from that location. However,
if parsing fails, we should give up trying to load remote data and
treat the data as a string instead.

@iainbeeston iainbeeston force-pushed the treat-invalid-uris-as-strings branch from 80f4740 to b9ebce0 Compare July 5, 2017 08:21
@iainbeeston
Copy link
Contributor Author

@RST-J Could I please get a review of this too?

@RST-J
Copy link
Contributor

RST-J commented Jul 6, 2017 via email

@iainbeeston
Copy link
Contributor Author

@RST-J No problem, I understand completely (sorry for spamming you with requests!)

string

There's a bug where if you pass a string as data and it looks like a
URI, we try to parse it and load the data from that location. However,
if parsing fails, we should give up trying to load remote data and
treat the data as a string instead.
@iainbeeston iainbeeston force-pushed the treat-invalid-uris-as-strings branch from b9ebce0 to d5a4ebd Compare July 6, 2017 07:51
@exterm
Copy link

exterm commented Oct 24, 2023

This seems like it is still a problem, @bastelfreak could you take a look?

@ekohl
Copy link
Member

ekohl commented Oct 25, 2023

There's at least a merge conflict so it needs a rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants