Article View: borland.public.cppbuilder.internet.socket
Article #4203Re: detect router
From: roger
Date: Fri, 18 Mar 2005 20:42
Date: Fri, 18 Mar 2005 20:42
51 lines
3145 bytes
3145 bytes
Mr joe that has just sent me a command from his client to my server(my PC) has had data returned to him from my pc where his client uses the data to build a preview html page on his PC with data such as my internet ip, username and other various data.. therefore a relative link using ie.. img src="\images\somepic.jpg" wouldn't work...as it his his Pc that generates the links.. and yes he would have already had my PC to contact me in the first place, but its for verification.. I know what you are saying Gambit is correct, but were not talking about the same type of program i dont think... Mainly me not explaining it the right way problably.. The nearest program i could describe it too although its a different line is Kazaa etc.. they search the kazaa website and then get what they want from the users pc.. "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:423b1ceb$1@newsgroups.borland.com... > > "roger" <rogersmail@ntlworld.com> wrote in message > news:423b0983@newsgroups.borland.com... > > > Why do i need my Internet IP so importantly... > > You don't. You are making the situation more complicated for yourself then > it needs to be. > > > because when i remote client contacts me after there search of > > my website my pc app returns a generated html document with > > links back to me, so Mr routers assigned IP (192.168.x.x) or my > > servers auto assigned address 0.0.0.0 wouldn't be much use to a > > hyperlink pointing say http://0.0.0.0:10245/cmd?action=&talk. > > If your server is running a webserver, and the remote client connects to a > URL associated with that webserver, than all of your links should be > formatted as relative links, not absolute links. That way, the links > themselves don't need to include the address at all. It is the remote > client's responsibility to keep track of which URL it requested, which will > be the address connected to the router's public IP, and then all links you > generate will be relative to that URL. > > > Gambit > >
Technical Details
Message-ID:
<423b3d0f$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<423a7852$1@newsgroups.borland.com> <423a95b5$1@newsgroups.borland.com> <423aa0ca$1@newsgroups.borland.com> <423ab09b@newsgroups.borland.com> <423ac0ff@newsgroups.borland.com> <423ada46$1@newsgroups.borland.com> <423b0983@newsgroups.borland.com> <423b1ceb$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,a79eaa4c33b47254 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "roger" <rogersmail@ntlworld.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <423a7852$1@newsgroups.borland.com> <423a95b5$1@newsgroups.borland.com> <423aa0ca$1@newsgroups.borland.com> <423ab09b@newsgroups.borland.com> <423ac0ff@newsgroups.borland.com> <423ada46$1@newsgroups.borland.com> <423b0983@newsgroups.borland.com> <423b1ceb$1@newsgroups.borland.com> Subject: Re: detect router Date: Fri, 18 Mar 2005 20:42:07 -0000 Lines: 53 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2739.300 NNTP-Posting-Host: 81.103.69.118 Message-ID: <423b3d0f$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1111178511 81.103.69.118 (18 Mar 2005 12:41:51 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail