Patrik Ragnarsson
Patrik Ragnarsson
This makes sense. Could be used for general instrumentation and not only debugging?
So the idea comes from Pitchfork (the code @nateberkopec linked). This is the commit that added it in pitchfork https://github.com/Shopify/pitchfork/commit/3dac0a43117aa03c854b9bc30e138b60e6166929 > Include X-Request-Id header is worker proctitle > Useful to...
My vote is on not doing this.
> This is the commit that added it in pitchfork [Shopify/pitchfork@3dac0a4](https://github.com/Shopify/pitchfork/commit/3dac0a43117aa03c854b9bc30e138b60e6166929) No, that was just an update, there is also https://github.com/Shopify/pitchfork/commit/4d87c740398ccb33d8b70e11ace21b6ca0479efb > Set better proctitle > This makes it easier...
> I think the main hangup is the Jruby step? What's the problem with it?
Should we do this in Puma? Isn't it an application problem? At least it it should be opt-in (or opt-out). Consider the [mess](https://github.com/puma/puma/issues/3014#issuecomment-1380291380) `supported_http_methods` brought. If people can do something...
cc @ioquatix
https://github.com/rack/rack/issues/1970 is related reading on this topic
> We haven incoming requests with a borked host header, i.e. > > ``` > Host: ${ip} > ``` > > (literally that string) > > My question is, who...
Now being discussed in https://github.com/rack/rack/issues/2295