Patrik Ragnarsson comments

Results 771 comments of


                                            Patrik Ragnarsson

Support apps responding to `Expect: 100-continue`

Corresponding issue on Falcon: https://github.com/socketry/falcon/issues/204

Support apps responding to `Expect: 100-continue`

Example use-case, respond with a redirect where an upload should go: https://stackoverflow.com/questions/68172230/nginx-behavior-of-expect-100-continue-with-http-redirect

Support apps responding to `Expect: 100-continue`

I don't know either if it is doable. Maybe the best we can do is offer a hook via the Puma config, similar to the "low level error handler", where...

Support apps responding to `Expect: 100-continue`

Yeah that's exactly what I had in mind (but I choose "false" instead of "true" to indicate the NOOP path – maybe good because "true" and array are both considered...

Introduce support for fiber-per-request.

Re `Thread.current` and leaking state, I suspect most apps are clearing it themselves ([example](https://github.com/steveklabnik/request_store/blob/81003584e527f7ddceaa8df47ace4badc48a4c84/lib/request_store/middleware.rb#L21-L34))

Something odd with Puma 6.0.0 / 6.0.1

Related to https://github.com/puma/puma/issues/2999 perhaps?

Something odd with Puma 6.0.0 / 6.0.1

Or https://github.com/puma/puma/issues/3000?

Something odd with Puma 6.0.0 / 6.0.1

@simonc @vitalinfo can you see if https://github.com/puma/puma/commit/3d33475dd400c8d097889ddd93fab38d080c25e0 (#3002) resolves the issue for you?

Something odd with Puma 6.0.0 / 6.0.1

Closing as https://github.com/puma/puma/pull/3002 that seems to address this was merged (this issue was probably the same as https://github.com/puma/puma/issues/2999 that was also closed by #3002)

Something odd with Puma 6.0.0 / 6.0.1

@vitalinfo can you try to reproduce your issue outside of your application? in an app anyone can run