Jeremiah Senkpiel

Results 518 comments of Jeremiah Senkpiel

@jbr sorry for not catching this before I made other changes... could you rebase this?

While returning something like status 416 may technically be more correct, in case of attack mitigation returning error 400 is probably the most sensible. 403 doesn't seem correct. As for...

I suggest looking at https://github.com/eaze/preroll/tree/latest/preroll-example/tests for production-grade "unit-integration" tests. It may be a while until this comes closer to Tide itself. Some of this may also end up in https://github.com/jbr/tide-testing

I think this is good, but it could just be a method on `tide::Request` IMO.

I no longer recall the conversation well enough on what @jbr's ideas for this were, only that they were interesting.

this will cause the need for a lot of crates to be updated and should be done with caution and probably only when necessary

Tide does not have http2+ support.

Related to https://github.com/http-rs/tide/issues/528 "Graceful shutdown"

@jbr This seems fine to me - I'd approve it if it weren't a draft

I think the server only shuts down in a `panic!` or due to an external signal, such `SIGINT`, or whatever the Windows equivalents are. I suppose this could possibly be...