This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

[closed] Multiple Sockets on HTTP request, but only one socket open

0

My question is simple:

I am using an embedded webserver (MQX) and have one socket for port 80.

But what I see now is that within one "send()" I get requests with different ports over the same src and destination ip (HTTP). This means in my definition more than one socket is in use, but this is de facto impossible... ?!

-> What is it i donot understand with HTTP? In my understanding ONE socket means ONE src-port-dst connection is possible.

Thank you very much!

asked 17 Mar '16, 07:56

PeterMai's gravatar image

PeterMai
6112
accept rate: 0%

closed 17 Mar '16, 11:40

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k572

Sorry, can you re-word the question?

A single HTTP request and response always use a single pair of ip:port combinations - sockets, one at client side and another one at server side. So I cannot see how you could see more that one local and one remote socket in an HTTP request as the title of your question suggests.

If your "web server" really only acts as a server, I cannot see what the "single socket" setting could mean. If it acts as a client, I could imagine that multi-socket setting would mean that each new request should use its own local socket (means: open a new session) rather than keeping old ones open.

(17 Mar '16, 09:17) sindy

The question has been closed for the following reason “Sorry IMO, this question is too far off-topic for this Q&A site.” by JeffMorriss 17 Mar ‘16, 11:40