Simple Apache Proxying
I was recently working with Apache and a service running on Kris Zyp's Persevere project (which is beyond awesome). Persevere was pushing messages to my application which was running on Apache; the problem was that Persevere and Apache were running on different ports which technically made them cross-domain. In order to make the server believe the web service was on the same domain/port, I needed to use Apache proxying. I opened the conf/httpd.conf file and added the following magic to make that possible:
# Proxy requests to /data to persevere
ProxyPass /service http://localhost:8080/Status
ProxyPassReverse /service/ http://localhost:8080/Status
RewriteRule ^/service$ http://localhost:8080/Status$1 [P,L]
Now any reference to the directory "/Status" is proxied to the other port to receive the data! Apache proxying is a huge boost to your web application if you can trust the other domain/port.
![CSS Gradients]()
With CSS border-radius, I showed you how CSS can bridge the gap between design and development by adding rounded corners to elements. CSS gradients are another step in that direction. Now that CSS gradients are supported in Internet Explorer 8+, Firefox, Safari, and Chrome...
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![FileReader API]()
As broadband speed continues to get faster, the web continues to be more media-centric. Sometimes that can be good (Netflix, other streaming services), sometimes that can be bad (wanting to read a news article but it has an accompanying useless video with it). And every social service does...
![Fullscreen API]()
As we move toward more true web applications, our JavaScript APIs are doing their best to keep up. One very simple but useful new JavaScript API is the Fullscreen API. The Fullscreen API provides a programmatic way to request fullscreen display from the user, and exit...
Not getting…. :-(
I don’t remember for sure, but off the top of my head don’t you have to enable the proxy module as well?
Good call Alan, you absolutely do.
That’s one of the best uses for apache proxying I’ve seen! Awesome!