Find us on GitHub

TestGatewaySubdomains

Implementationbifrost-gatewayboxokubo
Conformance Versionmainmainmain
Total216216216
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy%29444
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy%29#01222
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy tunneling via CONNECT%29222
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28HTTP proxy tunneling via CONNECT%29#01111
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28direct HTTP%29222
request for %7BCID%7D.ipfs.example.com%2Fipfs%2F%7BCID%7D should return HTTP 404 %28direct HTTP%29#01111
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28HTTP proxy%29888
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28HTTP proxy%29#01444
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%29444
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#01222
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28direct HTTP%29444
request for %7BCID%7D.ipfs.example.com%2Fipfs%2Ffile.txt should return data from a file in CID content root %28direct HTTP%29#01222
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy%29888
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy%29#01444
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy tunneling via CONNECT%29444
request for %7BCID%7D.ipfs.example.com should return expected payload %28HTTP proxy tunneling via CONNECT%29#01222
request for %7BCID%7D.ipfs.example.com should return expected payload %28direct HTTP%29444
request for %7BCID%7D.ipfs.example.com should return expected payload %28direct HTTP%29#01222
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy%29888
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy%29#01444
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy tunneling via CONNECT%29444
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28HTTP proxy tunneling via CONNECT%29#01222
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28direct HTTP%29444
request for a too long CID at %7BCIDv1%7D.ipfs.example.com returns expected payload %28direct HTTP%29#01222
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy%29888
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy%29#01444
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy tunneling via CONNECT%29444
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28HTTP proxy tunneling via CONNECT%29#01222
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28direct HTTP%29444
request for a too long CID at example.com%2Fipfs%2F%7BCIDv1%7D returns human readable error %28direct HTTP%29#01222
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy%29888
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy%29#01444
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy tunneling via CONNECT%29444
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28HTTP proxy tunneling via CONNECT%29#01222
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28direct HTTP%29444
request for deep path resource at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir%2Ffile %28direct HTTP%29#01222
request for example.com%2Fipfs%2F%3Furi%3Dipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy%29888
request for example.com%2Fipfs%2F%3Furi%3Dipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy%29#01444
request for example.com%2Fipfs%2F%3Furi%3Dipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy tunneling via CONNECT%29444
request for example.com%2Fipfs%2F%3Furi%3Dipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28HTTP proxy tunneling via CONNECT%29#01222
request for example.com%2Fipfs%2F%3Furi%3Dipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28direct HTTP%29444
request for example.com%2Fipfs%2F%3Furi%3Dipfs%253A%252F%252F.. produces redirect to %2Fipfs%2F.. content path %28direct HTTP%29#01222
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%29888
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%29#01444
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29444
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29#01222
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%29444
request for example.com%2Fipfs%2F%7BCIDv0%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%29#01222
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy%29888
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy%29#01444
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy tunneling via CONNECT%29444
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28HTTP proxy tunneling via CONNECT%29#01222
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28direct HTTP%29444
request for example.com%2Fipfs%2F%7BCIDv0%7D redirects to CIDv1 representation in subdomain %28direct HTTP%29#01222
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%29444
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy%29#01222
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29222
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29#01111
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%29222
request for example.com%2Fipfs%2F%7BCIDv1%7D produces redirect to %7BCIDv1%7D.ipfs.example.com %28direct HTTP%29#01111
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy%29888
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy%29#01444
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29444
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29#01222
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28direct HTTP%29444
request for example.com%2Fipfs%2F%7BCIDv1%7D redirects to subdomain %28direct HTTP%29#01222
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy%29888
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy%29#01444
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29444
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28HTTP proxy tunneling via CONNECT%29#01222
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28direct HTTP%29444
request for example.com%2Fipfs%2F%7BDirCID%7D redirects to subdomain %28direct HTTP%29#01222
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy%29444
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy%29#01222
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy tunneling via CONNECT%29222
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28HTTP proxy tunneling via CONNECT%29#01111
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28direct HTTP%29222
request for example.com%2Fipfs%2F%7BInvalidCID%7D produces useful error before redirect %28direct HTTP%29#01111
request for http%3A%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto%3A https produces redirect to HTTPS URL %28HTTP proxy%29888
request for http%3A%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto%3A https produces redirect to HTTPS URL %28HTTP proxy%29#01444
request for http%3A%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto%3A https produces redirect to HTTPS URL %28HTTP proxy tunneling via CONNECT%29444
request for http%3A%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto%3A https produces redirect to HTTPS URL %28HTTP proxy tunneling via CONNECT%29#01222
request for http%3A%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto%3A https produces redirect to HTTPS URL %28direct HTTP%29444
request for http%3A%2F%2Fexample.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Proto%3A https produces redirect to HTTPS URL %28direct HTTP%29#01222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy%29444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy%29#01222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy tunneling via CONNECT%29222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28HTTP proxy tunneling via CONNECT%29#01111
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28direct HTTP%29222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D doesn%27t match the example.com gateway %28direct HTTP%29#01111
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com and X-Forwarded-Proto%3A https match the example.com gateway%2C redirect with https %28HTTP proxy%29888
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com and X-Forwarded-Proto%3A https match the example.com gateway%2C redirect with https %28HTTP proxy%29#01444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com and X-Forwarded-Proto%3A https match the example.com gateway%2C redirect with https %28HTTP proxy tunneling via CONNECT%29444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com and X-Forwarded-Proto%3A https match the example.com gateway%2C redirect with https %28HTTP proxy tunneling via CONNECT%29#01222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com and X-Forwarded-Proto%3A https match the example.com gateway%2C redirect with https %28direct HTTP%29444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com and X-Forwarded-Proto%3A https match the example.com gateway%2C redirect with https %28direct HTTP%29#01222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com match the example.com gateway %28HTTP proxy%29888
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com match the example.com gateway %28HTTP proxy%29#01444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com match the example.com gateway %28HTTP proxy tunneling via CONNECT%29444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com match the example.com gateway %28HTTP proxy tunneling via CONNECT%29#01222
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com match the example.com gateway %28direct HTTP%29444
request for http%3A%2F%2Ffake.domain.com%2Fipfs%2F%7BCID%7D with X-Forwarded-Host%3A example.com match the example.com gateway %28direct HTTP%29#01222
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO%3A cleanup Kubo-specifics%29 %28HTTP proxy%29888
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO%3A cleanup Kubo-specifics%29 %28HTTP proxy%29#01444
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO%3A cleanup Kubo-specifics%29 %28HTTP proxy tunneling via CONNECT%29444
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO%3A cleanup Kubo-specifics%29 %28HTTP proxy tunneling via CONNECT%29#01222
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO%3A cleanup Kubo-specifics%29 %28direct HTTP%29444
valid breadcrumb links in the header of directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28TODO%3A cleanup Kubo-specifics%29 %28direct HTTP%29#01222
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy%29888
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy%29#01444
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29444
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28HTTP proxy tunneling via CONNECT%29#01222
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28direct HTTP%29444
valid file and subdirectory paths in directory listing at %7Bcid%7D.ipfs.example.com %28direct HTTP%29#01222
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy%29888
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy%29#01444
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy tunneling via CONNECT%29444
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28HTTP proxy tunneling via CONNECT%29#01222
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28direct HTTP%29444
valid parent directory path in directory listing at %7Bcid%7D.ipfs.example.com%2Fsub%2Fdir %28direct HTTP%29#01222