TestGatewaySubdomains

Implementationkubo
Conformance Versionv0.5.2
Total228
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy%294
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy%29#012
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy tunneling via CONNECT%292
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy tunneling via CONNECT%29#011
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28direct HTTP%292
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28direct HTTP%29#011
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28HTTP proxy%298
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28HTTP proxy%29#014
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28HTTP proxy tunneling via CONNECT%294
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28HTTP proxy tunneling via CONNECT%29#012
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28direct HTTP%294
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28direct HTTP%29#012
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy%298
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy%29#014
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy tunneling via CONNECT%294
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy tunneling via CONNECT%29#012
request for %7BCID%7D.ipfs.example.com should return expected payload %28direct HTTP%294
request for %7BCID%7D.ipfs.example.com should return expected payload %28direct HTTP%29#012
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy%298
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy%29#014
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy tunneling via CONNECT%294
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy tunneling via CONNECT%29#012
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28direct HTTP%294
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28direct HTTP%29#012
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy%298
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy%29#014
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy tunneling via CONNECT%294
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy tunneling via CONNECT%29#012
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28direct HTTP%294
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28direct HTTP%29#012
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy%298
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy%29#014
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy tunneling via CONNECT%294
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy tunneling via CONNECT%29#012
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28direct HTTP%294
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28direct HTTP%29#012
request for example.com%2Fipfs%2F%3Furi=ipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy%298
request for example.com%2Fipfs%2F%3Furi=ipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy%29#014
request for example.com%2Fipfs%2F%3Furi=ipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy tunneling via CONNECT%294
request for example.com%2Fipfs%2F%3Furi=ipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy tunneling via CONNECT%29#012
request for example.com%2Fipfs%2F%3Furi=ipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28direct HTTP%294
request for example.com%2Fipfs%2F%3Furi=ipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28direct HTTP%29#012
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%298
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%29#014
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%294
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29#012
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%294
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%29#012
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy%298
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy%29#014
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy tunneling via CONNECT%294
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy tunneling via CONNECT%29#012
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28direct HTTP%294
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28direct HTTP%29#012
request for example.com%2Fipfs%2F%7BCIDv1%7D%2F%7Bfilename with percent encoding%7D redirects to subdomain %28HTTP proxy%298
request for example.com%2Fipfs%2F%7BCIDv1%7D%2F%7Bfilename with percent encoding%7D redirects to subdomain %28HTTP proxy%29#014
request for example.com%2Fipfs%2F%7BCIDv1%7D%2F%7Bfilename with percent encoding%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%294
request for example.com%2Fipfs%2F%7BCIDv1%7D%2F%7Bfilename with percent encoding%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29#012
request for example.com%2Fipfs%2F%7BCIDv1%7D%2F%7Bfilename with percent encoding%7D redirects to subdomain %28direct HTTP%294
request for example.com%2Fipfs%2F%7BCIDv1%7D%2F%7Bfilename with percent encoding%7D redirects to subdomain %28direct HTTP%29#012
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%294
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%29#012
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%292
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29#011
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%292
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%29#011
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy%2916
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy%29#018
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%298
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29#014
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28direct HTTP%298
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28direct HTTP%29#014
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy%298
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy%29#014
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%294
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29#012
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28direct HTTP%294
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28direct HTTP%29#012
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy%294
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy%29#012
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy tunneling via CONNECT%292
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy tunneling via CONNECT%29#011
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28direct HTTP%292
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28direct HTTP%29#011
request for http:%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto: https produces redirect to HTTPS URL %28HTTP proxy%298
request for http:%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto: https produces redirect to HTTPS URL %28HTTP proxy%29#014
request for http:%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto: https produces redirect to HTTPS URL %28HTTP proxy tunneling via CONNECT%294
request for http:%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto: https produces redirect to HTTPS URL %28HTTP proxy tunneling via CONNECT%29#012
request for http:%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto: https produces redirect to HTTPS URL %28direct HTTP%294
request for http:%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto: https produces redirect to HTTPS URL %28direct HTTP%29#012
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy%294
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy%29#012
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy tunneling via CONNECT%292
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy tunneling via CONNECT%29#011
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28direct HTTP%292
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28direct HTTP%29#011
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com and X-Forwarded-Proto: https match the example.com gateway%2C redirect with https %28HTTP proxy%298
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com and X-Forwarded-Proto: https match the example.com gateway%2C redirect with https %28HTTP proxy%29#014
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com and X-Forwarded-Proto: https match the example.com gateway%2C redirect with https %28HTTP proxy tunneling via CONNECT%294
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com and X-Forwarded-Proto: https match the example.com gateway%2C redirect with https %28HTTP proxy tunneling via CONNECT%29#012
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com and X-Forwarded-Proto: https match the example.com gateway%2C redirect with https %28direct HTTP%294
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com and X-Forwarded-Proto: https match the example.com gateway%2C redirect with https %28direct HTTP%29#012
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com match the example.com gateway %28HTTP proxy%298
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com match the example.com gateway %28HTTP proxy%29#014
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com match the example.com gateway %28HTTP proxy tunneling via CONNECT%294
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com match the example.com gateway %28HTTP proxy tunneling via CONNECT%29#012
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com match the example.com gateway %28direct HTTP%294
request for http:%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host: example.com match the example.com gateway %28direct HTTP%29#012
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO: cleanup Kubo-specifics%29 %28HTTP proxy%298
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO: cleanup Kubo-specifics%29 %28HTTP proxy%29#014
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO: cleanup Kubo-specifics%29 %28HTTP proxy tunneling via CONNECT%294
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO: cleanup Kubo-specifics%29 %28HTTP proxy tunneling via CONNECT%29#012
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO: cleanup Kubo-specifics%29 %28direct HTTP%294
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO: cleanup Kubo-specifics%29 %28direct HTTP%29#012
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy%298
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy%29#014
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%294
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29#012
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28direct HTTP%294
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28direct HTTP%29#012
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy%298
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy%29#014
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy tunneling via CONNECT%294
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy tunneling via CONNECT%29#012
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28direct HTTP%294
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28direct HTTP%29#012