Re: Problem with recognition of php links from CMS
- --- In email@example.com, "Bradford L. Barrett" <brad@m...> wrote:
advice for the correct syntax ;-): You mean line 1734ff in webalizer.c:
int isurlchar(unsigned char ch)
if (isalnum((int)ch)) return 1; /* allow letters,
if (ch > 127) return 1; /* allow extended chars...
return (strchr(":/\\.,' *-+_@~()",ch)!=NULL); /* and a few special
so, shall I just add something like this
if (ch == ('?' && '&' && '=') ) return 1; /* allow more extended
chars for php/CMS URLs - caution: may be dangerous */
- You can analyze query strings with this build:
You can't group them though.
--- In firstname.lastname@example.org, "thommie_es" <t.rother@g...> wrote:
> I have a problem with php links: I want webalizer to analyze links
> which are generated by a php-based CMS. The real URLs are like
> In the access.log (apache 1.3x) they appear as
> 188.8.131.52 - - [28/Jan/2005:19:43:56 +0100] "GET
> /index.php/pages/DisplayPage?id=185 HTTP/1.1" 200 7811
> I want them grouped so that I can see an article's request number
> (articles are identified by the "id=xxx" which corresponds to its ID
> in the SQL database) as a unique value. I played with the "PageType",
> "AllURL" and the "GroupURL" directives. "PageType php" is also set, so
> that php pages are recognized at all. No matter what I do, the
> DisplayPage?id= entries in the logs are always added to the entries
> from the default "/" top-level entries.
> I assume that the problem comes from the "unusual" composition of the
> URL-string ("index.php/.../DisplayPage?=" instead of
> "index.php?something") But how can I make Webalizer understand this
> syntax? Any ideas?
> PS. I'm using Webalizer V2.01-10 (Linux 2.6.8-24.11-default) German
> and apache 1.3.28.
> Bye & Thanks, Thomas