Bug 6003 - tlwebadm and tlwebaccess doesn't support HTTP/1.1
Summary: tlwebadm and tlwebaccess doesn't support HTTP/1.1
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks: 6004
  Show dependency treegraph
 
Reported: 2016-09-22 14:04 CEST by Samuel Mannehed
Modified: 2017-01-26 13:44 CET (History)
2 users (show)

See Also:
Acceptance Criteria:


Attachments

Description Samuel Mannehed cendio 2016-09-22 14:04:34 CEST
HTTP/1.1 supports modern features like multiple requests over one connection. Supporting it would make our services better.
Comment 1 Samuel Mannehed cendio 2016-10-05 13:43:06 CEST
See bug 6020 for HTTP/2
Comment 2 Samuel Mannehed cendio 2017-01-25 15:13:35 CET
It seems like HTTP/1.1 expands caching support by introducing new tags used in headers and other things:

http://stackoverflow.com/questions/246859/http-1-0-vs-1-1
https://tools.ietf.org/html/rfc7234
https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching

After upgrading ThinLinc, recent versions of Safari doesn't clear the cache automatically. My guess is that this happens because we do not use any of these new HTTP/1.1 caching mechanisms which Safari seems to depend on.

The workaround for this is obviously to manually clear the browser cache. But when implementing this bug, we should take this into account.
Comment 4 Samuel Mannehed cendio 2017-01-26 10:30:07 CET
(In reply to comment #2)
> It seems like HTTP/1.1 expands caching support by introducing new tags used in
> headers and other things:
> 
> http://stackoverflow.com/questions/246859/http-1-0-vs-1-1
> https://tools.ietf.org/html/rfc7234
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching
> 
> After upgrading ThinLinc, recent versions of Safari doesn't clear the cache
> automatically. My guess is that this happens because we do not use any of these
> new HTTP/1.1 caching mechanisms which Safari seems to depend on.
> 
> The workaround for this is obviously to manually clear the browser cache. But
> when implementing this bug, we should take this into account.

Actually, we don't even have basic cache control in our web server. See bug 5711.

Note You need to log in before you can comment on or make changes to this bug.