Location URL was being generated with base URI potentially
containing an extraneous slash (/), thus using the response
directly would not take the client to a valid session since the
session-id would be missing from where it's expected to be.
Coverage remained the same at 100.0% when pulling 1d9350ab0e6ca81dc4ee881134c7bee8698f875e on BenjamenMeyer:bugfix_admin_location_url_fix into 44d7765a92dc4efd80fbb662607dd7f195a6de5d on TestInABox:master.