… cases where there /is/ a custom prefix, and when there isn't one are tested
- According to http://search.cpan.org/~miyagawa/PSGI-1.03/PSGI.pod, the "SERVER_NAME, SERVER_PORT: When combined with SCRIPT_NAME and PATH_INFO, these variables can be used to complete the URL.". This scenario was not checked in Plack::Test::Suite (which is a bug that I reported to the authors) which allowed a bug where the SCRIPT_NAME and PATH_INFO were duplicates of each other, and where the URL could not be recreated. (I discovered this when tring to run a Jifty application under Mongrel2.) - Refactored the SCRIPT_NAME and PATH_INFO parsing to be more similar to what is done for rack (https://github.com/darkhelmet/rack-mongrel2/blob/master/lib/rack/handler/mongrel2.rb) and for WSGI (https://github.com/rfk/m2wsgi/blob/master/m2wsgi/io/base.py).
… cause mongrel2 just wouldn't die