Hi Craig,
Would you please tell me if :
0
I have a TCP server
1
a I have a applet which connect to my TCP server
b I have already enabled some necessary "Privileges" for Netscape and IE
2
Now in my TCP server, with :
"s.getInetAddress().getHostAddress()" (s is a Socket)
a Can I always get the "real :-)" IP of client if the client computer has a
public IP
in the following cases:
client is behide a firewall
client uses a proxy server ( I don't know if there is "proxy server" for TCP
socket? )
...
b What will I get if client computer doesn't has a public IP or doesn't has a IP
in the following cases metioned in your email :
>... Indeed, the PC itself may not even *have* a real IP address -- it might
>be using the reserved Intranet >address >ranges (with the
>gateway providing address translation), or it might even be running a non-IP
>protocol internally (with the gateway providing protocol translation as
well) ...
3
Because now I am developing a audio/video live software with JMF
(Java Media Framwork), and JMF uses RTP/UDP to send stream,
so I need to know the "real" IP of client if it has . I have tried with servlet,
and now I try to use TCP socket.
If this email is "off-topic", I am sorry for that !
Thanks in advance !
Bo
Sept.11,2000
"Craig R. McClanahan" wrote:
> Jake Brain wrote:
>
> > Curious to hear from other developers who maintain session with client ip address
>and had to deal with aol users getting invalid sessions - since aol rotates ip
>addresses. How did you solve the problem, any ideas.
> >
>
> The simple answer is, you cannot depend on client IP addresses for Internet
>applications. Even if the IP address is not being rotated, it will generally be the
>IP address of a firewall or proxy server anyway -- so
> you still cannot tell which individual PC inside the firewall originated the
>request. Indeed, the PC itself may not even *have* a real IP address -- it might be
>using the reserved Intranet address ranges (with the
> gateway providing address translation), or it might even be running a non-IP
>protocol internally (with the gateway providing protocol translation as well).
>
> This is one of the reasons why the standard session management support in the
>servlet spec uses cookies or URL rewriting, not client IP addresses, as the basis for
>session identification.
>
> Craig McClanahan
>
> ====================
> See you at ApacheCon Europe <http://www.apachecon.com>!
> Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing
> Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ
> Applications to Tomcat
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
