Thread View: borland.public.cppbuilder.internet.web
5 messages
5 total messages
Started by mike
Fri, 03 Mar 2006 04:13
A basic question
Author: mike
Date: Fri, 03 Mar 2006 04:13
Date: Fri, 03 Mar 2006 04:13
19 lines
1591 bytes
1591 bytes
I have a basic question that I am trying to understand. Could some explain to me what is happening on the server side when this is entered in a web browser. http://someserver:2300/help/12345/full Of course this is a fictional site and I understand the request will go to port 2300. The other thing is that the number 12345 can be any number. What I don't understand is what or how is this request is handled on the server side. That is, if I make a request like this then information is returned to my browser, and if I change the number then different information is returned. Could someone help me in this understanding or point me to a site where I could inform myself. Thanks for any information. Mike
Re: A basic question
Author: Zara
Date: Fri, 03 Mar 2006 05:51
Date: Fri, 03 Mar 2006 05:51
31 lines
2032 bytes
2032 bytes
On Thu, 2 Mar 2006 23:13:22 -0500, "mike" <mfbrowne@earthlink.nnet> wrote: >I have a basic question that I am trying to understand. Could some explain >to me what is happening on the server side when this is entered in a web >browser. > >http://someserver:2300/help/12345/full > >Of course this is a fictional site and I understand the request will go to >port 2300. The other thing is that the number 12345 can be any number. What >I don't understand is what or how is this request is handled on the server >side. That is, if I make a request like this then information is returned to >my browser, and if I change the number then different information is >returned. > In the simplest of the servers, /help/12345/full will be the name of the file you request, it might be located (if it were a windows server) on c:\public_data\help\12345\full.html In more complex serevr, it could be abosultely anything. The server might scan the request and behavedifferently according to it. For instance, it may look at /help and decide you are asking for a suuport case, then it will see /12345 and know it refres to support case /12345, after that /full tells it to create an HTML page with full details of support case # 12345, and send it to you. Regards, Zara
Re: A basic question
Author: Hans Galema
Date: Fri, 03 Mar 2006 07:04
Date: Fri, 03 Mar 2006 07:04
27 lines
1934 bytes
1934 bytes
mike wrote: > http://someserver:2300/help/12345/full > > Of course this is a fictional site and I understand the request will go to > port 2300. The question is: who is listening on that port. Is it a normal webserver which will grab html pages or start a cgi.exe or has a cg.dll loaded ? Or is it a dedicated webserver which handles request self ? > The other thing is that the number 12345 can be any number. What > I don't understand is what or how is this request is handled on the server > side. There are many possibilities. "/help/12345/full" could be directories and then a default page would be grabbed and returned. "full"could be a cgi.exe. > That is, if I make a request like this then information is returned to > my browser, and if I change the number then different information is > returned. Indeed. It could be as simple as that number beeing a different diretory. Or help is a cgi.exe which reacts on the number. Hans.
Re: A basic question
Author: Remy Lebeau (TeamB)
Date: Fri, 03 Mar 2006 08:43
Date: Fri, 03 Mar 2006 08:43
20 lines
1954 bytes
1954 bytes
"mike" <mfbrowne@earthlink.nnet> wrote in message news:4407c261$1@newsgroups.borland.com... > I have a basic question that I am trying to understand. Have a look at RFC 1945 (http://www.ietf.org/rfc/rfc1945.txt) and RFC 2616 (http://www.ietf.org/rfc/rfc2616.txt). They describe the semantics of the HTTP protocol at the TCP/IP level. As for what happens on the server, when it receives the request you showedrequest, it parses the string "/help/12345/full", decides what to do with it, and then returns the appropriate data back to the browser. The string is just a string, so the server can process it any way it wishes. It does not have to be a physical file or folder. All the server has to do is receive requests and send responses. How it decides what data to send is at the server's descretion. Gambit
Re: A basic question
Author: mike
Date: Fri, 03 Mar 2006 13:01
Date: Fri, 03 Mar 2006 13:01
38 lines
2343 bytes
2343 bytes
Thank you Hans and Remy for responding, I appreciate it very much. So my understanding of your response is that the data positioned after the port identity is just sent to the application listening on the port. It would be the same as if an application using sockets to talk to a module running on the server sent data on the socket port. Am I correct on this interpretation. Mike "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:440801d4@newsgroups.borland.com... > > "mike" <mfbrowne@earthlink.nnet> wrote in message > news:4407c261$1@newsgroups.borland.com... > >> I have a basic question that I am trying to understand. > > Have a look at RFC 1945 (http://www.ietf.org/rfc/rfc1945.txt) and RFC 2616 > (http://www.ietf.org/rfc/rfc2616.txt). They describe the semantics of the > HTTP protocol at the TCP/IP level. > > As for what happens on the server, when it receives the request you > showedrequest, it parses the string "/help/12345/full", decides what to do > with it, and then returns the appropriate data back to the browser. The > string is just a string, so the server can process it any way it wishes. > It > does not have to be a physical file or folder. All the server has to do > is > receive requests and send responses. How it decides what data to send is > at > the server's descretion. > > > Gambit > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads