Hi, Currently, the RequestId middleware assumes that the request's ID is delivered in the `X-Request-Id` HTTP header. The value is hardcoded (see here <https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/request_id.rb#L18>). However, in our usecase, a different header name is used that we have no control over. So, it seems useful to be able to configure the header name to support environments that use other conventions for propagating a request ID.
Does this sound like a useful enhancement? Any opinions? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-core/1c603d07-fd1b-4f62-9586-15dadcc0eb0f%40googlegroups.com.
