Make the HTTPS certificate warning less of a stumbling block about fathom-fox HOT 4 CLOSED

@biancadanforth, I think you are right. I am able to create vectors for the shopping set with a regular HTTP server. The only thing I can think of is that I was loading pages through my file explorer (using file:///) when I was testing the extractor's correctness, and so was unnecessarily causing the CORS restrictions. That would be frustrating and embarrassing for me, though it would be good news for Fathom.

from fathom-fox.

I second. https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSRequestNotHttp says CORS requests must be HTTPS, but we're not dealing with CORS requests as long as we avoid file URLs: the host and port are the same for all requests.

from fathom-fox.

Since we chatted on IRC a few hours ago, I recalled that there are several CORS-controlling about:config flags (search for "cors" and "cross"). It's pretty heavy to start [automatically] installing brew packages. Maybe we can just twiddle those flags more easily? Of course, I (like you) am assuming we're not messing with the user's primary browser.

from fathom-fox.

You know, I was thinking more about it Friday, and I am wondering... @danielhertenstein , Why do we need an HTTPS server? If we have a local HTTP server, the browser should treat that as http:// protocol, not file:/// protocol I should think.

I just tried a regular HTTP server via python3 -m http.server 8000 --bind 127.0.0.1 for the Vectorizer step at least, and the pages loaded normally, and it produced the same vectors.json file as with the HTTPS server via fathom-serve. Maybe I am missing something?

from fathom-fox.