Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @rafaelfranca (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@mastahyeti yes, deleting PATH_INFO before or after a call to process can break tests as I outlined in #13851. Since controller tests haven't historically been processed by the full stack people have often configured environment variables to make things work and this makes them very susceptible to failing when we tinker with this behaviour.

Given that we're suggesting people move away from controller tests to integration tests because we've made them faster than controller tests in Rails 5 I'm not sure what the best thing to do here is. One option is to remove support for setting PATH_INFO in controller tests and always use the generated path, however we'd need to go through a deprecation phase for that.

Oh, damn. I wish I found that issue earlier last night 😄.

I'm going to close this, as it isn't a great solution to the problem and the problem is well documented in #13851.