Make handling of 'root_path' in dispatcher middleware adhere to ASGI spec #259
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.
Before this change, the dispatcher middleware didn't do anything with 'root_path'. It did, however, modify 'path'.
The problem with this behavior, is that the child ASGI app has no way to determine what its prefix it. And if it can't determine its prefix, it doesn't know how to construct URLs.
The ASGI spec isn't super clear on the expected behavior. However, some resources to review are:
root_path
to keep compatibility with ASGI and compatibility with other non-Starlette-specific libraries like a2wsgi encode/starlette#2400root_path
django/asgiref#229Based on the above, I believe that the correct behavior is that "root_path" should be updated by the dispatcher middleware but that "path" should not be modified.
In addition to the above change, I also updated the tests. And I also added a new test case where the dispatcher middleware is nested inside of itself.