-1

Weird, Read https://google.com had been working, and today it doesn't work anymore:

read https://google.com *** Access Error: invalid UTF-8 encoding: #{E9206E27}

user310291
  • 36,946
  • 82
  • 271
  • 487
  • 1
    If something is clearly (or likely) transient, the value over time of putting it on StackOverflow as "institutional knowledge" is low. It is probably a fit [for a bug tracker](https://github.com/red/red/issues) or just to go ask about it in [Red's chat rooms](https://gitter.im/red/home). Remember that the "long tail" of value of StackOverflow isn't for the questioner: it's whether that question is likely to be useful for future users. – HostileFork says dont trust SE Nov 04 '17 at 16:54

1 Answers1

1

That's a long time known issue with pages with invalid / different utf implementations. This can help

convert-invalid: function [page] [
    collect/into [foreach c page [keep to-char c]]  clear ""
]

>> convert-invalid read/binary https://google.com
== {<!doctype html><html itemscope="" itemtype="http://schema.org/Web...
sqlab
  • 6,412
  • 1
  • 14
  • 29