That's how it works. Outgoing HTTP requests bind to a random unused, unprivileged port on the client machine and connect to port 80 on your server. A different outgoing port will be used on subsequent requests.
Mike On Thu, Jul 17, 2008 at 9:24 PM, RCKV <[EMAIL PROTECTED]> wrote: > hello > > I am using apache http server to serve some xml requests from clients. > the http server hands over the incoming XML to back end application. the back > end application creates the response and hands over to HTTP server to be sent > out. for some requests, the client port is changing to a different one. > > the network trace shows the following for some requests. > > incoming request > host port:80 client port:1234 > > outgoing response: > host port:80 client port:3456 > > Could anyone please let me know if this is acceptable behavior? I wonder if > this could be related to mismatched responses on the client side that I am > facing. > > > > > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
