Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:proxy:lsws-as-a-websocket-proxy [2018/01/19 22:05]
Michael Alegre [Final Test: The Front End]
litespeed_wiki:proxy:lsws-as-a-websocket-proxy [2018/01/22 16:38]
Jackson Zhang [How to Configure LSWS as a WebSocket Proxy]
Line 17: Line 17:
 {{ :​litespeed_wiki:​proxy:​add-websocket-proxy1.png?​600 |}} {{ :​litespeed_wiki:​proxy:​add-websocket-proxy1.png?​600 |}}
  
-As you can see, it tested successfully +This screenshot shows a successful test. If it had failed, you would see a ''​Simple WebSocket Client undefined''​ error, like so:
- +
-If it had failed, you would see a ''​Simple WebSocket Client undefined''​ error, like so:+
  
 {{ :​litespeed_wiki:​proxy:​add-websocket-proxy2-testfail.png?​600 |}} {{ :​litespeed_wiki:​proxy:​add-websocket-proxy2-testfail.png?​600 |}}
Line 29: Line 27:
 {{ :​litespeed_wiki:​proxy:​add-websocket-proxy4.png?​800 |}} {{ :​litespeed_wiki:​proxy:​add-websocket-proxy4.png?​800 |}}
  
-Configure **URI** and **Address**.+Configure **URI** and **Address**. ​The URI can be a plain URI (starting with "/"​). The **URI** can be an exact match. If a plain URI ends with a "/",​ then this WebSocket backend will include all sub-URIs under this URI, such as **/sub/** should include /sub/001, /sub/002... etc.  However, the regular expression, such as ''/​sub/​*'',​ will **not** work for WebSocket. 
  
 Save and restart LSWS. Save and restart LSWS.
  • Admin
  • Last modified: 2020/01/09 00:36
  • by Lisa Clarke