HTTPRequest info request

I'm trying to access web sites on my local 'in-house' web-server. I don't seem to be able to get llHTTPRequest to get to it.

So the question is: Is this another 'feature' of LSL or am I doing something wrong.

This does not work ... (The X's are my address removed)
llHTTPRequest("http://192.XXX.XXX.XXX/index.html",[HTTP_METHOD,"GET"],"";

This Does
llHTTPRequest("http://www.whatever.com/index.html",[HTTP_METHOD,"GET"],"";

Any thoughts/suggestions?

192.XXX.XXX.XXX is a local IP address. If you want to be able to access your home computer from the internet, you need to use a real ip address that is visible on the internet. EVERYONE has a local IP address of 192.XXX.XXX.XXX just about.

First go see what your real IP address is:
http://www.myipaddress.com

See http://www.portforward.com
and/or
http://www.zoneedit.com/ to have a domain name forwarded to your public IP Address

In addition,

You'll want to have a static IP Address. You may have to ask your web host.
If you are running Windows XP, you'll hav a limited number of connections. So if you plan on allowing others to use whatevet you are making, be aware of this.

Check out this link below for detailed info on what you are trying to accomplish. This link puts you on page 3. I think you have already done page 1 and 2 (Setting up IIS).
http://www.connectedhomemag.com/HomeOffice/Articles/Index.cfm?ArticleID=24756&pg=3

Thanks MadamG ... however this is a lan ... I can type http:192.xxx.xxx.xxx in my browser and get to the sites ... (I'm using of course a router) ... it seems from your response that LSL adds an additional layer to the route ... I was hoping/thinking that the page was requested via the local client ... that appears to be not the case ...

Ah well ... I was just trying to test my lsl/php scripts without having to upload to my 'public' server test edit upload ... etc. ... just being lazy and trying to save step

Anyway thanks for the reply

I can also type 192.XXX.XXX.XXX in my web browser to get to my LAN...or my local website which are store on my PC or a PC on my lan...and so can most everyone. The thing is I cannot type that in and see your PC and you cannot use that to see my PC...or a website I have in my pc.

You must have a static IP address to access that LAN or PC from another location other than your PC or other pc on your LAN.

So if you are trying to do a request from SL, it's not on your LAN. Doing a request 10 http://192... will not find you. You need to use your static IP and set it up so that it is accessible to the internet.

Hope that helps.

Sorry didn't read that part.
Unfortunatley, it more trouble than its worth to set up your local pc in this manner just to test LSL/PHP scripts. Uploading them is less of a headache in my opinion. But I wish you luck and best regards!

HTTP requests originate from the SIM the script is on, not the local client.

This should clear everything up.


- d.

Just to clarify a bit further, you don't actually need a static public IP address. You can actually get away with using dynamic IP address with a service like Dyndns.org. As long as you have a dyndns client running that updates their DNS servers with your public IP address, then your domain will be up to date with your dynamic IP. There are clients available for windows, as well as linux, and some are built into routers, like linksys routers.

Xavior is right.
All true!

After setting up your DynDNS in your router or using the system executable, your still going to have to use PORT FORWARDING or VIRTUAL SERVER in order to tell the router to take anything on port 80 and send it to your internal LAN IP (192.168.x.x).

That way once the HTTP request is routed to your home IP by DynDNS, the router knows which computer on the LAN to send the packets too.

Also, only valid domain names are usable at this time, putting a raw IP (68.x.x.x) will not work. It must be in the form of http://www.blahblah.com. Which is fine if you use DynDNS since you can just go: http://www.yourdomain.dnsalias.com to have it forward to your home.


Enjoy!

Using something like "http://11.22.33.44/page.php" won't work? How does LSL know the difference?

Actually not all 192.x.y.z IP addresses are local. Here is the set of non-routable IP addresses:

Not to be nit-picky, and even though this is a bit off-topic, but those addresses can actually be routed. 127.0.0.1 is the only address that can't (well, it can be but it's not supposed to be) be routed. The list of addresses you give are merely the default addressing schemes for most common small home/small office broadband routers.

However, what really matters is what is on the private network, which can be anything you define. As long as those IPs are private (as in, not assigned by an ISP or some other authoritative entity) then they are not going to be able to be routed -outside- of your private network. You can have multiple subnets within your private network with static routes going between each subnet using any address scheme you specify. Those private addresses can not be routed to any public networks however.

Oh, yes. Certainly. It is a standard. But all backbone internet gateways will refuse to route those addresses, as will your ISP's gateways if they are set up correctly. This is what makes them, "private/non-routable IP numbers." Here's a rather decent description:

...and I did leave out a set, though it is rather a special case:

You also left out the old class "E" space...

http://www.faqs.org/rfcs/rfc3330.html


- d.