Skip to content
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

response.headers allways return text/turtle with CSS v7.0.2 and rdflib@2.2.33 #53

Closed
bourgeoa opened this issue Dec 12, 2023 · 1 comment · Fixed by #54
Closed

response.headers allways return text/turtle with CSS v7.0.2 and rdflib@2.2.33 #53

bourgeoa opened this issue Dec 12, 2023 · 1 comment · Fixed by #54

Comments

@bourgeoa
Copy link
Contributor

bourgeoa commented Dec 12, 2023

CSS v7.0.2 :

  • mashlib@1.8.8 with rdflib@2.2.30 return the correct contentType on response.headers.get('content-type')
  • while mashlib build with rdflib@2.2.33 allways return text/turtle

HumanPane found the correct contentType with :
https://github.com/SolidOS/solid-panes/blob/a5a81b8818d4d69ce7b812e84d8d95e1f3f84793/src/humanReadablePane.js#L77-L83

@bourgeoa
Copy link
Contributor Author

bourgeoa commented Dec 13, 2023

I finally used a different solution, removing the options parameter in fetcher.webOperation for GET and HEAD
There seem to be a change to investigate in rdflib between version 2.2.30 and 2.2.33.

const response = await fetcher.webOperation('HEAD', subject.uri) // , defaultFetchHeaders())

This is the first time I encounter a difference between NSS and CSS related to rdflib.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant