How does REV IDE connect to online features?

[edgore]

In my work environment we have the internet somewhat blocked off - most ports closed by default, some websites blocked, etc.

I think this is causing me problems with being able to access any of the online components in the IDE - the user notes in the dictionary, Revolution Online, even the "Check For Updates" feature. Trying to use all of these either results in a "can't reach server" or "No Internet Connection Found" type errors.

All of this works fine at home, using the same work machine on my home network, so I am assuming that I can probably solve this problem by asking infosec to open up the ports that Rev is using, or unblocking the URLs it's trying to access.

To do this though I need to know what they are. I tried peeking in the applicable scripts, but they are (quite reasonably) password locked.

So, I am wondering - does anybody know what ports, protocols and urls are used by the IDE when accessing these online elements?

I would assume that it's http over port 80, or maybe https on 443, but those are open on the network. I can't imagine a reason to use anything else (ftp? maybe, but that's open too), which would leave a blocked url as the reason for the problem...but that seems pretty unlikely too.

Any help greatly appreciated.

Thanks,

Edwin Gore

[Mark]

Hi Edwin,

RunRev uses port 80 as far as I know. This shouldn't be the problem.

Perhaps the firewall on your computer allows specific application to connect to the internet only. I wouldn't be surprised if RunRev isn't among those applications.

Another possibility is the router/proxy checks the user agent. RunRev's user agent is by default "Revolution (OS)" where "OS" is replaced with an abbreviation corresponding to your operating system. You might circumvent this problem by executing the following code:

Code: Select all

set the httpheaders to "User_Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; nl; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5"

(run it from the message box or a mouseUp handler in a button for example). There is a good chance that this tricks the router/router into thinking that it is dealing with a genuine browser.

Finally, it is also possible that RunRev can't cope with the proxy server of your company. You can try to enter proxy information in the preferences window or use scripts the right proxy info (but that won't solve your current problem).

Best regards,

Mark

[edgore]

This give me a couple of ideas at least. I rand some tests yesterday using openScokets and it t=does appear that rev is using port 80, and is pointed to the runrev site, so that cannot be the problem. I will try the other suggestions.

Thanks!

[edgore]

Figured it out. They changd the proxy port from what I had originally set up, and I never knew, since my browser was set up to use an automatic configuration script. Updating the port in the Rev proxy setting has fixed everything.

Thanks!