-
Bug
-
Resolution: Fixed
-
High
-
6.0.0-rc2
-
Severity 2 - Major
-
XHR fallback has known issues when synchrony service is accessed via the synchrony-proxy web application.
Workaround is to ensure that browser traffic goes direct to synchrony instead of being routed via the confluence synchrony-proxy web application.
- mentioned in
[CONFSERVER-44250] XHR Fallback does not work with synchrony-proxy
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 212664 ] |
Workflow | Original: JAC Bug Workflow v3 [ 2903394 ] | New: CONFSERVER Bug Workflow v4 [ 2997916 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2801462 ] | New: JAC Bug Workflow v3 [ 2903394 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2731969 ] | New: JAC Bug Workflow v2 [ 2801462 ] |
Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2397262 ] | New: JAC Bug Workflow [ 2731969 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2294419 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2397262 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2230850 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2294419 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2189362 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2230850 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1919793 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2189362 ] |