Enhancement #296
Websocket configurable in a different port and/or subdomain
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | WIAB Server | Estimated time: | 0.00 hour | |
| Target version: | 0.2.0 | |||
| Resolution: | Tags: |
Description
The idea is that the client uses two configurable listening addresses:
• one for the normal traffic (all the common server petitions), the current http_frontend_public_address
• and a new one for the websocket traffic (that can be configured to a different subdomain or port if it's necessary).That is, we would be able to split these two different traffics. This would allow the use of proxies, caches or CDNs for the "normal traffic".
History
#1
Updated by Vicente J. Ruiz Jurado over 12 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 80
#2
Updated by Stanislav German-Evtushenko over 12 years ago
Fixed in 9da117c8
#3
Updated by Vicente J. Ruiz Jurado over 12 years ago
- Status changed from Resolved to Closed
- % Done changed from 80 to 100