Hi David,

I highly recommend that you work with some sort of URL rewriting.  It is 
absolutely key to effective placement and indexing in search engines.  It 
sounds like a lot of work, but it really is worth it.

In addition to using mod_rewrite in Apache, you can handle this entirely inside 
of Java Servlets.  If you are using a compliant servlet container, you can use 
wildcard matching to have all URLs that include a certain string (such as 
"RoutingServlet", in your example below) get directed to a single servlet.  
Then, you can have that servlet parse out the URL and turn it into the chosen 
parameters.

Also, check out javax.servlet.Filter (if you're using a servlet container).  I 
think there is some potential here, but it would take some more Google 
searching.  At the very least, it's a useful tool:
  http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/Filter.html

If you're using Tomcat, you also can use their "Valve" interface.  There may 
even be existing implementations for URL rewriting.  Here are a couple useful 
links:
  http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/valve.html
        
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Valve.html

Regarding the existing logs, you could probably use a linux tool like "sed" or 
use regular expressions in Java or perl to transform the existing logs to the 
URL patterns you eventually settle upon.  Then, your old reports and your new 
reports will match.

Kind Regards,
Justis Peters

David Cooper [EMAIL PROTECTED] wrote:
>    Tony,
>    
>    A good option!  Thanks.  I can do an impact analysis on this option.
>    
>    It is frustrating that all the information I need is already in the apache
>    log files and yet I might have to touch some code that works just to get
>    reports to look a certain way.  :(.  Sorry, your suggestion is right on,
>    I'm just blowing off steam at the products I'm working with :)
>    
>    
> 
>      ----- Original Message -----
>      From: [1]Tony Spencer
>      To: [2]'Research Triangle Java User's Group mailing list.'
>      Sent: Friday, January 07, 2005 9:29 AM
>      Subject: RE: [Juglist] web page access statistics are
>      misleadingthroughanalyzer tool
>      David,
>      If you are running Apache you could use mod_rewrite to create static
>      URL's which would fix your stats.
>      
>      For example:
>      [3]http://www.mysite.com/RoutingServlet?directive=viewproducts&categoryid
>      =1234
>      
>      could become:
>      [4]http://www.mysite.com/routing-viewproducts-1234.html
>      
>      I don't know if it would require too large of a code rewrite for you but
>      this is how I do it.
>      
>      Tony
> 
>    ---------------------------------------------------------------------------
> 
>        From: David Cooper [mailto:[EMAIL PROTECTED]
>        Sent: Friday, January 07, 2005 9:19 AM
>        To: [email protected]
>        Subject: [Juglist] web page access statistics are misleading
>        throughanalyzer tool
> 
>        Anyone on here use Webalizer ([5]http://www.mrunix.net/webalizer/)
>        for stat tracking on their Web site? We use it on our company site,
>        but have recently changed URL structure.
> 
>        Using a command pattern we have one request routing servlet that all
>        requests go through which causes all the URLs to start with the same
>        servlet name.
> 
>        Does anyone know if Webalizer can differentiate based on parameter
>        values (it doesn't seem to be looking past the servlet name (i.e. We
>        want to track /gateway?cmd=AboutUs separately from /gateway?cmd=Home)
>        Currently, all hits are being reported against just /gateway.
> 
>        Or, does anyone know of a FREE analysis tool that will accomplish my
>        goal.  My client is perturbed and blaming the Java technology.
> 
>        Thanks,
> 
>        David
> 
>        
> 
>        
> 
>    ---------------------------------------------------------------------------
> 
>      _______________________________________________
>      Juglist mailing list
>      [email protected]
>      http://trijug.org/mailman/listinfo/juglist_trijug.org
> 
> References
> 
>    Visible links
>    1. [EMAIL PROTECTED]
>       mailto:[EMAIL PROTECTED]
>    2. [email protected]
>       mailto:[email protected]
>    3. http://www.mysite.com/RoutingServlet?directive=viewproducts&categoryid
>    4. http://www.mysite.com/routing-viewproducts-1234.html
>    5. http://www.mrunix.net/webalizer/

> _______________________________________________
> Juglist mailing list
> [email protected]
> http://trijug.org/mailman/listinfo/juglist_trijug.org


_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org

Reply via email to