[
https://issues.apache.org/jira/browse/GUACAMOLE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-783:
-------------------------------------
Description:
When using IE 11, changes made via the Apache Guacamole admin interface, such
as creating or renaming connections, appear to not take effect until after
logging out and back in. This is actually due to IE caching the results of the
GET requests from the relevant REST API endpoints.
This behavior does not occur in Chrome nor in Firefox and appears to be due to
a bug in IE 11's handling of the HTTP cache. Implementations are required to
invalidate cached responses for a URI once a PUT, DELETE, or POST request is
sent to that same URI:
https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.10
Adding {{Cache-Control: no-cache}} and {{Pragma: no-cache}} to requests sent
via {{$http}} solves the issue.
was:
When using IE 11, changes made via the Apache Guacamole admin interface, such
as creating or renaming connections, appear to not take effect until after
logging out and back in. This is actually due to IE caching the results of the
GET requests from the relevant REST API endpoints.
{{Cache-Control: no-cache}} is present on all GET requests to the REST API
(confirmed via both Chrome and IE dev tools), and [RFC
7234|https://tools.ietf.org/html/rfc7234] dictates that this header should
control whether the client side cache serves cached responses, but IE returns
cached responses regardless. IE *does* behave correctly if {{Pragma: no-cache}}
is present.
This behavior does not occur in Chrome nor in Firefox.
> REST API responses are cached in IE 11
> --------------------------------------
>
> Key: GUACAMOLE-783
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-783
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Reporter: Michael Jumper
> Assignee: Michael Jumper
> Priority: Minor
>
> When using IE 11, changes made via the Apache Guacamole admin interface, such
> as creating or renaming connections, appear to not take effect until after
> logging out and back in. This is actually due to IE caching the results of
> the GET requests from the relevant REST API endpoints.
> This behavior does not occur in Chrome nor in Firefox and appears to be due
> to a bug in IE 11's handling of the HTTP cache. Implementations are required
> to invalidate cached responses for a URI once a PUT, DELETE, or POST request
> is sent to that same URI:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.10
> Adding {{Cache-Control: no-cache}} and {{Pragma: no-cache}} to requests sent
> via {{$http}} solves the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
