Parsing an apache access log line

a have a line to parse....

10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] "GET /star/images/main.gif
HTTP/1.1" 200 334

anyone has a better idea... got stuck coming up with one simple regex (
the double quote...) Need to tokenize the line,

token 1 = 10.88.90.75
token 2 = -
token 3 = -
token 4 = [16/Jul/2007:07:46:09 -0400]
token 5 = "GET /star/images/main.gif HTTP/1.1"
token 6 = 200
token 7 = 234

can some one help please.

Joe.

···

--
Posted via http://www.ruby-forum.com/.

a have a line to parse....

10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] "GET /star/images/main.gif
HTTP/1.1" 200 334

anyone has a better idea... got stuck coming up with one simple regex (
the double quote...) Need to tokenize the line,

token 1 = 10.88.90.75
token 2 = -
token 3 = -
token 4 = [16/Jul/2007:07:46:09 -0400]
token 5 = "GET /star/images/main.gif HTTP/1.1"
token 6 = 200
token 7 = 234

can some one help please.

Try this as a starting point:

line.scan %r{
  \S+

\[[^\]]*\]
"[^"]*"

}x

(untested)

Kind regards

robert

···

2007/7/16, Joe Nciri <dev@logixcel.com>:

hi joe!

Joe Nciri [2007-07-16 13:59]:

a have a line to parse....

10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] "GET /star/images/main.gif
HTTP/1.1" 200 334

maybe you want to have a look at log_parser:
<http://topfunky.net/svn/plugins/mint/lib/log_parser.rb&gt;

cheers
jens

···

--
Jens Wille, Dipl.-Bibl. (FH)
prometheus - Das verteilte digitale Bildarchiv für Forschung & Lehre
Kunsthistorisches Institut der Universität zu Köln
Albertus-Magnus-Platz, D-50923 Köln
Tel.: +49 (0)221 470-6668, E-Mail: jens.wille@uni-koeln.de
http://www.prometheus-bildarchiv.de/

/([0-9.]*) (-) (-) (\[.*\]) (\".*\") ([0-9]*) ([0-9]*)/ comes to mind,
although I'm probably wrong with the backslashes - some of the things
I escaped probably aren't significant characters and some other ones
probably are.

Could you provide a test suite with more lines?

Hey, wouldn't /(?^| )[^\S]*|\".*\")(?| )/, work to find each of the
tokens (that is, iterate it to find ALL matches)?

Aur

···

On 7/16/07, Joe Nciri <dev@logixcel.com> wrote:

a have a line to parse....

10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] "GET /star/images/main.gif
HTTP/1.1" 200 334

anyone has a better idea... got stuck coming up with one simple regex (
the double quote...) Need to tokenize the line,

token 1 = 10.88.90.75
token 2 = -
token 3 = -
token 4 = [16/Jul/2007:07:46:09 -0400]
token 5 = "GET /star/images/main.gif HTTP/1.1"
token 6 = 200
token 7 = 234

can some one help please.

Joe.

--
Posted via http://www.ruby-forum.com/\.

Joe Nciri schrieb:

a have a line to parse....

10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] "GET /star/images/main.gif
HTTP/1.1" 200 334

anyone has a better idea... got stuck coming up with one simple regex (
the double quote...) Need to tokenize the line,

token 1 = 10.88.90.75
token 2 = -
token 3 = -
token 4 = [16/Jul/2007:07:46:09 -0400]
token 5 = "GET /star/images/main.gif HTTP/1.1"
token 6 = 200
token 7 = 234

can some one help please.

Joe.

line = "10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] \"GET star/images/main.gif HTTP/1.1\" 200 334"
token = /^(.*?)\s+(.*?)\s+(.*?)\s+(\[.*?\])\s+(\".*?\")\s+(\d+)\s+(\d+)$/.match(line)

=> token[1] = 10.88.90.75
    token[2] = -
    token[3] = -
    etc.

BR Phil

> a have a line to parse....
>
> 10.88.90.75 - - [16/Jul/2007:07:46:09 -0400] "GET /star/images/main.gif
> HTTP/1.1" 200 334
>
> anyone has a better idea... got stuck coming up with one simple regex (
> the double quote...) Need to tokenize the line,
>
> token 1 = 10.88.90.75
> token 2 = -
> token 3 = -
> token 4 = [16/Jul/2007:07:46:09 -0400]
> token 5 = "GET /star/images/main.gif HTTP/1.1"
> token 6 = 200
> token 7 = 234
>
> can some one help please.

Try this as a starting point:

line.scan %r{
  \S+
> \[[^\]]*\]
> "[^"]*"
}x

(untested)

I think I got the order wrong. Rather do

line.scan %r{
  \[[^\]]*\]

"[^"]*"
\S+

}x

Or do an explicit parse like the one Aur suggested.

Kind regards

robert

···

2007/7/16, Robert Klemme <shortcutter@googlemail.com>:

2007/7/16, Joe Nciri <dev@logixcel.com>: