Is it possible for Apache to randomly select different URLs to serve up? For example: User1 -> http://my.domain.com/1 User2 -> http://my.domain.com/2 User3 -> http://my.domain.com/3 And after a certain point, start over again? I'm not really looking for random, ordered would work. For more information, please read more below. Thanks, Matt [More] I have configured Apache with mod_jk and mod_rewrite to forward to different applications deployed in Tomcat based on a parameter. For example: http://my.domain.com/?v=1 --> tomcat/webapps/app1 http://my.domain.com/?v=2 --> tomcat/webapps/app2 If this parameter is not in the URL, the default Tomcat application (tomcat/webapps/ROOT) will be served up. The reason I'm doing this for A/B Testing - so a new app can be deployed with small changed and users will get routed to it. The reason for the "v" parameter is to ensure users are routed to a particular app when they pass URLs around to friends and such. In addition to a "v" parameter, I'm looking for a "v" cookie and routing appropriately. This all works great and I'm happy with my current setup. If you need more details, please see my blog entry[1] where I documented my experience. For those users who come in w/o a "v" parameter or "v" cookie, I'd like to evenly distribute them to the different version of the site. I'm not so concerned about the "evenly" aspect, but I would like to send users to different applications. Is this something that's possible with Apache or should I do this in the ROOT webapp in Tomcat? [1] http://raibledesigns.com/rd/entry/mixing_apache_http_server_mod -- View this message in context: http://www.nabble.com/Is-it-possible-for-Apache-to-randomly-select-different-URLs-to-serve-up--tf3603013.html#a10065662 Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|