Re: Sockets!

On 9 Sep 2005 09:27:55 +0200, Gordon Beaton <not@xxxxxxxxx> wrote or
quoted :

>The client doesn't need to tell the server where to send the response
>because the connection consists of two channels, one in each
>direction. The server can send the response on the same socket that
>the request arrived on.

See http://mindprod.com/jgloss/tcpip.html

Look at the packet format. It might become a little clearer.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Again taking new Java programming contracts.
.

Relevant Pages

  • Re: NT Backup and Restore
    ... >It was the intelligent community I was soliciting a response from anyway. ... I have a recommendation of my own. ... I bet you troll these channels ...
    (microsoft.public.windows.server.general)
  • [REVS] Introduction to HTTP Response Splitting
    ... single HTTP request that forces the web server to form an output stream, ... one response. ... HTTP response splitting is a fairly new web application vulnerability. ... Web cache poisoning: In this form a rather larger defacement takes place ...
    (Securiteam)
  • Re: Help - administrator locked out!
    ... Second - thanks for your extremely helpful response. ... with 1 Novell server. ... I don't pretend that I'm some sort of super administrator or anything. ... I agree it's my practices that have got me into trouble in the first ...
    (microsoft.public.windows.server.general)
  • [NEWS] Cisco Content Service Switch 11000 Series DNS Negative Cache of Information Denial-of-Service
    ... respond to certain Domain Name Service (DNS) name server record requests ... Global Server Load Balancing. ... This vulnerability in CSS is documented as Cisco Bug IDs CSCdz62499 and ... formulate a response for the client. ...
    (Securiteam)
  • Re: NotificationSampleWebDav-Monitor OWA Inbox
    ... re-login or update your cookie with each response you get... ... Warning: Exiting Action with an exception: The remote server returned an ... // Create request object and assign credentials. ... Stream newStream = Request.GetRequestStream; ...
    (microsoft.public.exchange.applications)