document catch-all redirect hack

[thornjad]

Documents the -P http://localhost:8080? proxy hack from #338 (comment) in the Readme

Fixes #338, closes #331, closes #194, closes #80

[thornjad]

@BigBlueHat @houston3 what do you think about the wording here?

[houston3]

Looks good to me.

[BigBlueHat]

Look great, @thornjad. Merging shortly. 😃

[grundmanise]

This does not work with ssl certificates, though

/node_modules/http-server/node_modules/http-proxy/lib/http-proxy/index.js:120
    throw err;
    ^

Error: unable to verify the first certificate
    at TLSSocket.onConnectSecure (_tls_wrap.js:1055:34)
    at TLSSocket.emit (events.js:198:13)
    at TLSSocket._finishInit (_tls_wrap.js:633:8)
error Command failed with exit code 1.

[oller]

Encountering the same issue as @grundmanise , no SSL support for fallback routing. Did you find an alternative package to meet these requirements @grundmanise ? Thanks!

[grundmanise]

This command worked for me..yes, with sudo 🤷‍♂️

$ sudo npx http-server ./build -p 433 -a whatever.com -S -C ./ssl/_wildcard.pem -K ./ssl/_wildcard.key.pem -c-1

Prior to running it you should also add 127.0.0.1 whatever.com to your hosts file /private/etc/hosts and generate those ssl certificates. I don't remember which lib I've used to generate certificates, but you can try pem.

I also had to rewrite webpack certificates on every run (?) if I'm not mistaken. But maybe that's due to CRA:

$ rm -f ./node_modules/webpack-dev-server/ssl/server.pem && cat ./ssl/server.pem > ./node_modules/webpack-dev-server/ssl/server.pem

otherwise it didn't work for me. server.pem is a file that has both key and certificate in it (i.e. _wildcard.pem + _wildcard.key.pem).

I could be doing it wrong, so if any one knows an easier solution pls comment.