I have multiple web services which lie on different directories:
- Service A is located under http://localhost/svcA
- Service B is located under http://localhost/svcB
Both web services are accessible over a custom HTTP binding with Connection: keep-alive to reduce the handshaking overhead.
When I connect to service A over a browser, and directly afterwards to service B, the connection stays open with service A (due to Connection: keep-alive) and bugs occur since the messages were sent to the wrong service.
- Is there some HTTP header that specifies when a browser should reconnect?
- I've thought about subdomaining to avoid the problem, e.g. http://svcA.localhost for service A. Is there something in the HTTP spec which guarantees a reconnect on subdomain changes or does this only work on specific browsers?