features request in KHTML for interaction with another KDE project
Sebastien Raveau
sebastien.raveau at epita.fr
Mon Apr 18 21:33:45 BST 2005
On Monday 18 April 2005 21:01, Kevin Krammer wrote:
> On Monday 18 April 2005 20:51, Sebastien Raveau wrote:
> > It's only to be able to distinguish, in case of HTTP transmissions,
> > between content (usually images) that was viewed included in a webpage,
> > and content that was request separately, as explained at the bottom of
> > http://hawkeye.sourceforge.net/developers.html
> >
> > That way I'll be able to group entries, instead of having webpages and
> > images all at the same level in the list, which would be very annoying in
> > cases of webpages that load a lot of small images, like spacer.gif etc...
>
> As you are the proxy for the viewer application, you see which files it
> requests when displaying the content, no?
Please consider the following scenario:
" a user is visiting http://www.arctic.org/~trockij/ "
As you can see, the homepage embeds 3 images: trockij.gif,
trockij-parappa.jpg and good-for-the-company.png
The user then clicks on the link called "not very impressive to look at",
which points to http://www.arctic.org/~trockij/kernel.org.jpg
Now, hawKeye will indeed know that the user saw trockij.gif,
trockij-parappa.jpg, good-for-the-company.png and kernel.org.jpg, but only by
parsing the HTTP requests, there is no way of distinguishing between the
images that were embedded in the homepage, and the kernel.org.jpg that was
viewed separately, as illustrated by the following 2 HTTP requests:
GET /~trockij/trockij.gif HTTP/1.1
Connection: Keep-Alive
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.0 (like
Gecko)
Referer: http://www.arctic.org/~trockij/
Pragma: no-cache
Cache-control: no-cache
Accept: image/png, image/jpeg, video/x-mng, image/jp2,
image/gif;q=0.5,*/*;q=0.1
Accept-Encoding: x-gzip, x-deflate, gzip, deflate
Accept-Charset: iso-8859-1, utf-8;q=0.5, *;q=0.5
Accept-Language: en
Host: www.arctic.org
and
GET /~trockij/kernel.org.jpg HTTP/1.1
Connection: Keep-Alive
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.0 (like
Gecko)
Referer: http://www.arctic.org/~trockij/
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*
Accept-Encoding: x-gzip, x-deflate, gzip, deflate
Accept-Charset: iso-8859-1, utf-8;q=0.5, *;q=0.5
Accept-Language: en
Host: www.arctic.org
Well, the first one has indeed some extra headers (Pragma and Cache-control)
but I doubt they can be used for distinguishing between the embedded image
and the one viewed separately.
Anybody got a better idea?
Kind regards,
--
Sébastien Raveau
computer and network security student
head of the hawKeye network monitor project
http://hawkeye.sourceforge.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20050418/316b0c2c/attachment.sig>
More information about the kfm-devel
mailing list