@jeremyevans

Shouldn't SCRIPT_NAME="" and PATH_INFO="" (both empty strings) be invalid? Since this is a code change, we probably want to do it in a new PR, but what are your thoughts?

I agree that this may be an issue. Can we add a test and update the SPEC if necessary to provide clarification?