)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"4ed249e7ab02e7c6c3e2eca98b3219ccfd06f55e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5c05ddbf_bcaf752d","updated":"2025-03-10 18:53:21.000000000","message":"When I start the web server on my vsaio on master I get:\n\n```\nvagrant@saio:~/swift/test/cors$ python3 ./main.py --no-run\nServing test at http://localhost:8000/#OS_AUTH_URL\u003dhttps%3A//saio/auth/v1.0\u0026OS_USERNAME\u003dtest%3Atester\u0026OS_PASSWORD\u003dtesting\u0026OS_STORAGE_URL\u003dhttps%3A//saio/v1/AUTH_test\u0026S3_ENDPOINT\u003dhttp%3A//localhost%3A8080\u0026S3_USER\u003dtest%3Atester\u0026S3_KEY\u003dtesting\n```\n\nWith this change I get:\n\n```\nvagrant@saio:~/swift/test/cors$ python3 ./main.py --no-run\nServing test at http://localhost:8000/#OS_AUTH_URL\u003dhttps%3A//saio/auth/v1.0\u0026OS_USERNAME\u003dtest%3Atester\u0026OS_PASSWORD\u003dtesting\u0026OS_STORAGE_URL\u003dhttps%3A//saio/v1/AUTH_test\u0026S3_ENDPOINT\u003dhttps%3A//saio\u0026S3_USER\u003dtest%3Atester\u0026S3_KEY\u003dtesting\n```\n\nIn either case, if I fix the `localhost` part in the netloc (ignoring the `s/localhost/saio/` changed to the `S3_ENDPOINT`) and open the page in my browser I get:\n\n```\nComplete. TESTS: 80 PASS: 21 FAIL: 59 SKIP: 0\n```\n\nbut I think that\u0027s mostly because of `ERR_CERT_AUTHORITY_INVALID` from my host.\n\nIf I disable SSL on my vsaio I get\n\n```\npython3 ./main.py --no-run\nServing test at http://localhost:8000/#OS_AUTH_URL\u003dhttp%3A//saio%3A8080/auth/v1.0\u0026OS_USERNAME\u003dtest%3Atester\u0026OS_PASSWORD\u003dtesting\u0026OS_STORAGE_URL\u003dhttp%3A//saio%3A8080/v1/AUTH_test\u0026S3_ENDPOINT\u003dhttp%3A//saio%3A8080\u0026S3_USER\u003dtest%3Atester\u0026S3_KEY\u003dtesting\n```\n\n... and when I visit:\n\n```\nhttp://saio:8000/#OS_AUTH_URL\u003dhttp%3A//saio%3A8080/auth/v1.0\u0026OS_USERNAME\u003dtest%3Atester\u0026OS_PASSWORD\u003dtesting\u0026OS_STORAGE_URL\u003dhttp%3A//saio%3A8080/v1/AUTH_test\u0026S3_ENDPOINT\u003dhttp%3A//saio%3A8080\u0026S3_USER\u003dtest%3Atester\u0026S3_KEY\u003dtesting\n```\n\nI see\n\n```\nComplete. TESTS: 80 PASS: 66 FAIL: 14 SKIP: 0\n```\n\nwhere as if I revert the change and stick with the original URL:\n\n```\nvagrant@saio:~/swift/test/cors$ python3 ./main.py --no-run\nServing test at http://localhost:8000/#OS_AUTH_URL\u003dhttp%3A//saio%3A8080/auth/v1.0\u0026OS_USERNAME\u003dtest%3Atester\u0026OS_PASSWORD\u003dtesting\u0026OS_STORAGE_URL\u003dhttp%3A//saio%3A8080/v1/AUTH_test\u0026S3_ENDPOINT\u003dhttp%3A//localhost%3A8080\u0026S3_USER\u003dtest%3Atester\u0026S3_KEY\u003dtesting\n```\n\nand *only* fix the netloc part (not the query string)\n\n```\nhttp://saio:8000/#OS_AUTH_URL\u003dhttp%3A//saio%3A8080/auth/v1.0\u0026OS_USERNAME\u003dtest%3Atester\u0026OS_PASSWORD\u003dtesting\u0026OS_STORAGE_URL\u003dhttp%3A//saio%3A8080/v1/AUTH_test\u0026S3_ENDPOINT\u003dhttp%3A//localhost%3A8080\u0026S3_USER\u003dtest%3Atester\u0026S3_KEY\u003dtesting\n```\n\nI see:\n\n```\nComplete. TESTS: 80 PASS: 62 FAIL: 18 SKIP: 0\n```\n\n... so markedly better!\n\nAs I final sanity I confirmed if I fix the `S3_ENDPOINT` query string param to also say saio instead of localhost - that produces the same number of failures as I get with this change.  So there\u0027s no regression; this seems like a clear ergonomics improvement - which is quite helpful because debugging cors tests is a real PITA already.","commit_id":"cfa0094eb412e2a5e9ff8c651c463ace1c962607"}]}