This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

HTTP Response

Douglas Rapp
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

This is kind of a low-level question, perhaps aiming at the HTTP specification itself. I've posed the same basic question at here:

Essentially what I need to know is (and I am currently trying to test this behavior on my test system): is it possible for an HTTP client (say, a web browser or a web service client) to make a request to a server at some IP address (say,, and then receive a response from a different address (say, because the server has more than one valid interface? Or is there anything that would enforce the response packets to go out over the same interface on which the request was received?

If it is possible, is there a way to configure a Windows Server 2008 system (running a Tomcat-deployed web application) to ensure that responses get sent over the same interface as the request?

  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic