http to https : timeout with OPTIONs on NSS

[bourgeoa]

specification-tests/protocol/cors/preflight.feature

Line 27 in 6fe7818

When method OPTIONS

specification-tests/protocol/cors/preflight-requests.feature

Line 44 in 6fe7818

Scenario: OPTIONS request returns headers for pre-flight check after redirect from http

[edwardsph]

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

[bourgeoa]

@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]

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]

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.