bzz-immutable returns empty page instead of content
burdakovd opened this issue · comments
Expected behaviour
https://swarm-gateways.net/bzz-immutable:/3f04f0076ccf39b410f3421e5476a9e79edc4e327d59d7929aa6ad9fc73f672b/ to have content
Actual behaviour
https://swarm-gateways.net/bzz-immutable:/3f04f0076ccf39b410f3421e5476a9e79edc4e327d59d7929aa6ad9fc73f672b/ has no content
Steps to reproduce the behaviour
- https://swarm-gateways.net/bzz-hash:/theswarm.eth/ returns 3f04f0076ccf39b410f3421e5476a9e79edc4e327d59d7929aa6ad9fc73f672b
- https://swarm-gateways.net/bzz-immutable:/3f04f0076ccf39b410f3421e5476a9e79edc4e327d59d7929aa6ad9fc73f672b/ returns empty document (content length=0, whereas I expected it to return the same as https://swarm-gateways.net/bzz:/theswarm.eth/ )
Not sure what the protocol in your team for closing issues is, but just wanted to let you know that the issue is still visible at https://swarm-gateways.net/bzz-immutable:/3f04f0076ccf39b410f3421e5476a9e79edc4e327d59d7929aa6ad9fc73f672b/
I assume it's been fixed in master, but will take some time to get to production?
@burdakovd the protocol is that issues get closed when they get merged.
we don't do continuous deployment at the moment with swarm for various reasons and we deploy to swarm-gateways.net only on a new version tag on the main ethereum repository.
you could, in the meanwhile, run master@HEAD locally to verify the fix.