6 Replies Latest reply on Mar 1, 2012 1:03 AM by welsh

Apache rewrite rules interfering with node registration

welsh Feb 17, 2012 3:25 PM

Hey Everyone,

I have mod_cluster running perfectly fine with a fresh installation of Apache and JBoss EAP 5.1, however when I start adding in rewrite rules for a site I've ran into a issue.

Certain rewrite rules that get added in place prevent nodes from being able to register themselves. So my question is, what can I do to get Apache to recognize that requests from my node don't get rewritten?

As far as I can tell that the JBoss node registers with Apache by hitting "/" but I've tried playing with some basic rewrite rules and haven't had any luck with it. Any suggestions?

Thanks,

Welsh

1. Re: Apache rewrite rules interfering with node registration

jfclere Feb 20, 2012 3:58 AM (in response to welsh)

The best it is to use a Deny/Allow
like:
+++
   <Directory />
     Order deny,allow
     Deny from all
     Allow from node1
     Allow from node2
     ....
    </Directory>
+++
Actions
2. Re: Apache rewrite rules interfering with node registration

welsh Feb 23, 2012 3:22 PM (in response to jfclere)

Hey,

I've tried something like that before but it doesn't work.

The nodes are able to properly hit "/" but then they hit the rewrite rule of sending "/" to "/content/mysite/homepage.html" and the nodes no longer are able to register themselves.

Any additional ideas?

Thanks,

Welsh
Actions
3. Re: Apache rewrite rules interfering with node registration

jfclere Feb 24, 2012 5:36 AM (in response to welsh)

It seems your configuration is broken and unsafe (you should have one VirtualHost to receive those requests).
You can set the path used those request via the proxyURL (or proxy-url in AS7) See http://docs.jboss.org/mod_cluster/1.2.0/html/java.properties.html
Actions
4. Re: Apache rewrite rules interfering with node registration

welsh Feb 25, 2012 1:34 AM (in response to jfclere)

Hey,

The server configuration is still in development right now so I'm aware / not suprised it may be unsafe,

But if I understand correctly, we can utilize a VirtualHost listening for example on port 81 to have the nodes register themselves with Apache, then on the VirtualHost that is running on port 80 we utilize the registered nodes?

And I just looked at the proxyURL so would that mean if i set it up as "node-registration" the nodes would register themselves with Apache utilizing "/node-registration" instead of "/"?

Both options look feasible if I understand correctly, but is one way more preferred than the other or is it a more user preference type of deal? (If I understood correctly)

Thanks,

Welsh
Actions
5. Re: Apache rewrite rules interfering with node registration

jfclere Feb 27, 2012 5:04 AM (in response to welsh)

The idea to have 2 VirtualHost having one on 81 and the other one 81 is OK.
The proxyURL is just URL send in the METHOD /URL HTTP/1.,1 the mcpm is in the data of the request.
Actions
6. Re: Apache rewrite rules interfering with node registration

welsh Mar 1, 2012 1:03 AM (in response to jfclere)

Hey,

That worked perfectly for my needs and I have it working exactly how I want it.

Thanks for the hepl.

Welsh
Actions

Go to original post