add support for action dispatch request id generation #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eprothro
force-pushed
the
action-dispatch-support
branch
from
15ec188
to
5fb0444
Compare
|
SGTM, thanks for the patch + PR! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rails 3.2 and later have
ActionDispatch::RequestIdin the middleware stack.Rack::Timeoutmiddleware doesn't currently support re-using the request id generated by this middleware in Rails. This PR adds support for that.Also changes the format of a generated uuid to be a proper type 4 uuid, like nginx, heroku, etc generate for the request id header.
Should have no impact on non-rails applications.