-->
Page 1 of 1

Web request on other than port 80?

PostPosted: Thu Mar 17, 2016 10:27 am
by Steve Jones
I see the "wget" command, which seems to work great, but I'm trying to make a program that will activate "Scenes" on my Vera home automation system.. The URL for activating a scene is this format:

http://ip_address:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=<SceneNum>

So.. It seems that since wget wont make a request on other than port 80, I don't see how to do this..

I guess I could investigate opening a raw socket, and sending the GET command manually, but I was curious how hard it would be to expand the wget to allow for other ports?

Thanks! I'm just beginning to play with these awesome little modules, and so far this is all very amazing!!
-Steve

Re: Web request on other than port 80?

PostPosted: Thu Mar 17, 2016 7:27 pm
by Mmiscool
Right now it is hard coded for port 80 but I think a modification to the function to include a port number might be in order.

Some thing like wget("test.com/test.htm",1234)

I have a couple of things in the que to be added on the next build and this seems like it would be a good update.

Re: Web request on other than port 80?

PostPosted: Fri Mar 18, 2016 2:40 am
by Steve Jones
That would be awesome... and I'd like to think I'm not the only person who would use it.. For example, I know Comcast blocks inbound port 80 on my residential cable modem, so if for example I wanted to have internet connected devices make calls to my internal stuff, it would have to be on a different port..

Thanks so much! I can't wait to try it.. I look forward to trying to build small battery powered buttons (like the Amazon Dash buttons, but DIY with an ESP8266 in it) that trigger scenes on the home automation system!

-Steve