Quantcast
Viewing all articles
Browse latest Browse all 3822

Publishing Atlassian Confluence websocket on port 8091 using TMG 2010

Hi Everyone,

We have Atlassian Confluence installed on our internal LAN that uses websockets (listening on port 8091) for collaborative real time editing.

Our TMG 2010 Server is single NIC solution; I believe a multi-NIC solution is required to publish a websockets non-web server protocol publishing rule.

According to Atlassian when a user cannot connect to Confluence via a WebSocket, "we'll fall back to a XML HTTP Request (XHR), allowing them to edit pages successfully."

https://confluence.atlassian.com/conf610/administering-collaborative-editing-952623315.html

Does TMG 2010 need any further configuration given we already have a HTTP/HTTPS web publishing rule in place to permit XHR?

Is it possible to use the HTTP filter to change the header to "UPGRADE" for websockets ???

https://en.wikipedia.org/wiki/HTTP/1.1_Upgrade_header

Thanks.

 

Viewing all articles
Browse latest Browse all 3822

Trending Articles