rath1
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2010
04:40 PM
HTTP on port other than 80?
Can RokuHD retrieve files from web servers running on a port other than 80?
I have tried URLs like http://<sitename>.com:1029/img.jpg with roUrlTransfer, poster screen and other SDK objects, they all returned timeout error. I downloaded packet trace from Roku, it shows TCP SYN going to port 1029 and no TCP ACK coming back.
I can connect to the same URL with a PC browser running behind the same router and it works just fine. Please advise if !=80 port should work for HTTP on Roku.
Sergey
I have tried URLs like http://<sitename>.com:1029/img.jpg with roUrlTransfer, poster screen and other SDK objects, they all returned timeout error. I downloaded packet trace from Roku, it shows TCP SYN going to port 1029 and no TCP ACK coming back.
I can connect to the same URL with a PC browser running behind the same router and it works just fine. Please advise if !=80 port should work for HTTP on Roku.
Sergey
4 REPLIES 4

RokuKevin
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2010
04:44 PM
Re: HTTP on port other than 80?
It is designed to work.... However, I can confirm that we do have an open bug on this issue right now.
--Kevin
--Kevin
rath1
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2010
05:14 PM
Re: HTTP on port other than 80?
Hi Kevin,
thanks for the prompt reply. I am writing a Roku app for the server that doesn't open port 80. It opens sequential ports, one port for each authenticated client. Is there a workaround for this bug?
thanks,
Sergey
thanks for the prompt reply. I am writing a Roku app for the server that doesn't open port 80. It opens sequential ports, one port for each authenticated client. Is there a workaround for this bug?
thanks,
Sergey
bcl
Channel Surfer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2010
07:39 PM
Re: HTTP on port other than 80?
I ran into the same problem. Streaming works, and some of the poster urls, but not other (I was originally trying to run on port 8080).
nowhereman
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2010
11:09 AM
Re:
"RokuKevin" wrote:
It is designed to work.... However, I can confirm that we do have an open bug on this issue right now.
--Kevin
I stumbled across an interesting workaround for this while trying to get some audio streams to work. It appears that is you append a forward slash to one of these problem URLs, it will work. For instance, http://88.191.48.171:8000 fails, but http://88.191.48.171:8000/ works. At least in some cases. I'd love to know if others can confirm this.
twitter:nowhereman
http://www.thenowhereman.com/roku
http://www.thenowhereman.com/netflix
http://www.thenowhereman.com/roku
http://www.thenowhereman.com/netflix