This site is used to aid making coralized urls. More information about the coral cdn can be found on their website at www.coralcdn.org.

This is a redirector site. It will take the address and forward you to the coralized version of it. Going to http://coralize.net/http://www.google.com/translate will redirect you to http://www.google.com.nyud.net/translate. This server only reformats the address, all caching is still handled by Coral.

Since ssl connections can not and should not be cached, going to an address like http://coralize.net/https://www.google.com/ will automatically redirect to https://www.google.com/. This is the same behavior done by Coral.

Credit goes to whoever initially created this site for starting the idea (and motivating me to actually reregister the domain and recreate it)

FAQ

What information do you track?
As little as possible. Since having this hosted at dreamhost a minimum of 3 days access logs are kept. No stats are kept beyond that. I just test a url myself every so often to make sure it's still working. You can also contact me at the address at the bottom of the page to let me know if it isn't working.
Why should I use this?
If you don't want to figure out how to properly form an address so it goes through the coral cache. Typically I'll use it if I go to an address that is really slow or down. I will then just prepend 'http://coralize.net/' to the address.
Why should I NOT use this?
Keep in mind this is being run by an individual as a free service. If sometime down the road I decide to no longer renew the domain all links would then no longer work. Also when using the coralized address, it uses a mirroring system to make sure the request goes through. Coralize.net is running of a single server, and creates a single point of failure.
How do you pay for this service?
All costs are out of pocket. The domain registration is the most costly thing at under $10.00 per year. Traffic usage is very minimal. In short, the costs to run this are minimal.
How popular is this?
See first question. I don't keep logs so I have no idea. When testing and I enable logging I do notice it is being used but I don't have any exact numbers. It may be interesting to have a counter for the number of times it's been used, but that would introduce a little more overhead, even though very minimal.

Changelog