Jade Michael Thornton
Jade Michael Thornton
Alright, @idmontie's #395 and @jesseditson's #294 have a one-line difference. I'm going to go with #294 because it came first
Requirements for merging: - [ ] Add documentation to `doc/http-server.1` - [x] Wait for #693 to merge (because it will likely cause conflicts) - [ ] Fix all conflicts
While I'm always hesitant to expand the scope of http-server, HTTPS development is obviously important, so I'd be open to seeing what a PR for this would look like!
Could you provide more context/description? What would you like to see in this option, and where exactly would caching happen and not happen? What do you mean by local and...
By local do you mean files on the server or client?
The clarification is because those files are only local to http-server, not to the browser (the client). That doesn't sound quite right though because the server doesn't do any caching...
I'm not really sure this would add much to the server, the directory listing is meant to be an aid to development. Would this add anything other than just improving...
Do other servers like Apache allow exclusions without rewriting/redirecting? It seems like files that shouldn't be served shouldn't be in a directory being served?
I know this PR is a few years old, @howardroark I can take this over if you'd like me to
Could you clarify, is the port staying open after you stop the server?