-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
with NSS returns : $ | data types don't match (LIST:STRING) #116
Comments
The HTTP specs seem clear that the server should not return a body on a HEAD request: https://www.rfc-editor.org/rfc/rfc9110.html#name-head |
Sorry. I was not clear with the issue.
There is no body but the data type is not the expected one. |
That does look like a possible bug in the test but I am unable to reproduce it as the tests now fail earlier. I'm running against inrupt.net on version 5.7.8 and all these tests fail with a 403 response when 200 was expected: ✗ Access-Control-Allow-Origin header is set to correct origin for GET on container Are you still seeing the original problem? If so, how can I reproduce it? |
Issue is still there. I run the tests against the test server https://solidcommunity.net:8443 |
Ah - that explains it. I only test the released version. |
tiddy done. Thanks |
I tried to create a test account on solidcommunity.net and add a trusted app but I cannot edit my WebID document. Just adding the fragment and saving gives the error:
I can't get any further. If you want to send me credentials for a test account for alice, I will try again |
I looked at the tests in NSS. The empty body check is made against
this is the
|
This is a painful known issue recently introduced in rdflib.js |
I've run the acao-vary test against this server and I can see that the body is empty. However, I think the karate response tests are confused by the fact that the server is reporting a content length of 2 despite it being empty. 2024-01-16 08:48:51,455 DEBUG [com.int.karate] (main) response time in milliseconds: 206 Can you see if fixing the content length resolves the problem? |
Sorry, that is not actually the issue since it is valid for content-length to be non-zero since it represents the length of the content that would be returned for a GET. |
You are right NSS is mistakenly returning I tested the conformance-tests and the issue is resolved. To implement the change I shall either do it resolved with commit nodeSolidServer/node-solid-server@fbd30b0 |
specification-tests/protocol/cors/acao-vary.feature
Line 33 in 6fe7818
specification-tests/protocol/cors/acao-vary.feature
Line 19 in 6fe7818
The text was updated successfully, but these errors were encountered: