Enhancement #296

Websocket configurable in a different port and/or subdomain

Added by Vicente J. Ruiz Jurado over 8 years ago. Updated over 8 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:WIAB ServerEstimated 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".

https://issues.apache.org/jira/browse/WAVE-357

History

#1 Updated by Vicente J. Ruiz Jurado over 8 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 80

#3 Updated by Vicente J. Ruiz Jurado over 8 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 80 to 100

Also available in: Atom PDF