http to https : timeout with OPTIONs on NSS

solid-contrib / specification-tests

Test coverage report

https://solid-contrib.github.io/specification-tests/

MIT License

7 stars 4 forks source link

http to https : timeout with OPTIONs on NSS #113

Open bourgeoa opened 9 months ago

bourgeoa commented 9 months ago

https://github.com/solid-contrib/specification-tests/blob/6fe781855cdf0104909123ee0c28624f4bed4fd6/protocol/cors/preflight.feature#L27

https://github.com/solid-contrib/specification-tests/blob/6fe781855cdf0104909123ee0c28624f4bed4fd6/protocol/cors/preflight-requests.feature#L44

edwardsph commented 9 months ago

I'm not sure what you are asking here. If NSS times out on this request isn't that an NSS issue?

bourgeoa commented 8 months ago

@edwardsph I tried a lot of redirect options on NSS

I did not find a solution on express to redirect http to https there is no issue to redirect container Url without slash to container Url with slash (and this is implemented in NSS)
solidcommunity.net is using NGINX to redirect 301 from http to https for port 80 to port 443, but it does not work or I don't find the solution for solidcommunity.net:8443

Is this functionality a MUST in solid or in http ?

edwardsph commented 8 months ago

https://solidproject.org/TR/protocol#server-tls-https-redirect

When both http and https URI schemes are supported, the server MUST redirect all http URIs to their https counterparts using a response with a 301 status code and a Location header.

Would it perhaps be true to say that your instance does not support http - in which case the test does not apply?

bourgeoa commented 8 months ago

Would it perhaps be true to say that your instance does not support http - in which case the test does not apply?

Yes. And in which case NSS now passes 100% of the conformance tests.