Possible cache confusion between HTML shim and turtle versions of a page
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 70
- Forks
- 31
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 5
Description
My attempt to reload https://solidos.solid.community/Team/ lead to a blank page and the browser tab favicon showing a "working ... " circle.
Nothing on console log.
Maybe the browser renderer, instead of being given the data browser HTML file, has internally been given the TTL file.
https://solidos.solid.community/Team/SolidOs%20team%20chat/index.ttl#this
Request URL: https://solidos.solid.community/Team/
Request Method: GET
Response headers
Status Code: 304 Not Modified
Remote Address: 165.227.231.225:443
Referrer Policy: no-referrer-when-downgrade
Accept-Ranges: bytes
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Authorization, User, Location, Link, Vary, Last-Modified, ETag, Accept-Patch, Accept-Post, Updates-Via, Allow, WAC-Allow, Content-Length, WWW-Authenticate, MS-Author-Via
Allow: OPTIONS, HEAD, GET, PATCH, POST, PUT, DELETE
Cache-Control: public, max-age=0
Content-Length: 759
Content-Type: text/html; charset=utf-8
Date: Mon, 10 Aug 2020 22:30:36 GMT
ETag: W/"2f7-7438674ba0"
Last-Modified: Sat, 26 Oct 1985 08:15:00 GMT
Link: <.acl>; rel="acl", <.meta>; rel="describedBy", <http://www.w3.org/ns/ldp#Container>; rel="type", <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"
MS-Author-Via: SPARQL
Set-Cookie: nssidp.sid=s%3A5ggq0_s689eNtskxk5PaVrYB2HJul0gw.TuU8LfocIZA%2BMeKoqWyobVIWBHZWBu3o80VkEf7%2BoO0; Domain=.solid.community; Path=/; Expires=Tue, 11 Aug 2020 22:30:36 GMT; HttpOnly; Secure
Updates-Via: wss://solidos.solid.community
Vary: Accept, Authorization, Origin
WAC-Allow: user="read",public="read"
X-Powered-By: solid-server/5.4.0
Request headers:
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9,fr;q=0.8
Cache-Control: max-age=0
Connection: keep-alive
Cookie: nssidp.sid=s%3A5ggq0_s689eNtskxk5PaVrYB2HJul0gw.TuU8LfocIZA%2BMeKoqWyobVIWBHZWBu3o80VkEf7%2BoO0
Host: solidos.solid.community
If-Modified-Since: Sat, 26 Oct 1985 08:15:00 GMT
If-None-Match: W/"2f7-7438674ba0"
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: none
Sec-Fetch-User: ?1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the reload of https://solidos.solid.community/Team/ and inspect the documented request and response headers, especially the 304 response and content type. Done means identifying whether the HTML shim or Turtle representation is returned and resolving the blank-page behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100