Updating Railo behind Proxy / Firewall
If you're attempting to update your Railo server and you're behind a firewall / proxy with restricted outbound access, you can manually download the patch and install yourself.
The patches can always be found at:
http://www.getrailo.org/railo/remote/download/{full patch number}/{full patch number}.rc
So, for example, 3.1.1 is found at:
http://www.getrailo.org/railo/remote/download/3.1.1.000/3.1.1.000.rc
Now, once you have the .rc file downloaded, what do you do with it?
Depending on how your Railo is setup, you're looking the /railo-server/patches folder. In resin, it can be found {resin install}/lib/railo-server/patches -- So, if you're on a different JEE engine other than Resin, just look around for your /railo-server/patches folder and drop it in place. Once in place, restart the Railo instance in the server context ( http://{hostname}/railo-context/admin/server.cfm ). This will drop your current session and you'll have to re-log in. When you do, you should be patched!



/opt/tomcat/webapps/railo.war/WEB-INF/lib/railo-server/patches
In the mean time, if you followed Sean's 'multi web' install guide, the path is .../apache-tomcat-6.0.20/railo/railo-server/patches/3
----------------------------
The code:
<cfhttp url="http://dev.railo.ch/railo/remote/version/Info.cfc?...; method="get" resolveurl="no" result="dev">
<cfwddx action="wddx2cfml" input="#dev.fileContent#" output="dev_build">
<cfdump eval=dev_build>
<cfhttp url="http://preview.getrailo.org/railo/remote/version/I...; method="get" resolveurl="no" result="preview">
<cfwddx action="wddx2cfml" input="#preview.fileContent#" output="preview_build">
<cfdump eval=preview_build>
<cfhttp url="http://www.getrailo.org/railo/remote/version/Info....; method="get" resolveurl="no" result="public">
<cfwddx action="wddx2cfml" input="#public.fileContent#" output="public_build">
<cfdump eval=public_build>
At any rate, build .014 is on the dev.railo.ch at the moment. I don't think there will be another bleeding edge build until Event Gateways are in Railo as that's what they're currently focused on at the moment, but I could be wrong.
I am behind a proxy, but FireFox understands how to use them so that's a good solution for now.
It's just Railo's administrator GUI that doesn't understand it needs to use a proxy:-)