Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

fascinating but strange server response!

0 views
Skip to first unread message

Yef

unread,
Mar 19, 2005, 12:54:39 PM3/19/05
to
Hi all,

Recently, I fetched a page from a server, its info is:

Server: Apache/1.3.33 (Unix) mod_fastcgi/2.4.2 PHP/4.3.10
mod_ssl/2.8.22 OpenSSL/0.9.7d
X-Powered-By: PHP/4.3.10

Within the HTML response I found numerous lines that had only
3 characters each, always 0..9 and a..f i.e. hexadecimal.

These were always inside of links.

Can someone tell me what these little buggers are all about?

Thanks.

Tim

unread,
Mar 20, 2005, 1:11:53 AM3/20/05
to
On 19 Mar 2005 09:54:39 -0800,
"Yef" <e9...@yahoo.com> posted:

Encoded characters. They might be trying to hide them from prying eyes, or
they could be characters that need encoding to be part of the URI (due to
the rules of what characters are allowed in them).

--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.

Yef

unread,
Mar 20, 2005, 7:08:17 AM3/20/05
to

Tim wrote:

> > Can someone tell me what these little buggers are all about?
>
> Encoded characters. They might be trying to hide them from prying
eyes, or
> they could be characters that need encoding to be part of the URI
(due to
> the rules of what characters are allowed in them).

But I've found that the URL works when I remove these
'characters'. Which incidentally, 3 hex digits is the wrong
number for either 1 or 2 characters. Also note, in one case
I found that these 3 character were within the http:// expression.
Clearly these characters are supposed to be ignored.
But when did this become a standard that browsers adhere to?
It seems to be an attempt at preventing spidering.

Juha Laiho

unread,
Mar 20, 2005, 2:28:58 PM3/20/05
to
"Yef" <e9...@yahoo.com> said:
>Recently, I fetched a page from a server, its info is:
...

>Within the HTML response I found numerous lines that had only
>3 characters each, always 0..9 and a..f i.e. hexadecimal.

It looks like you've seen "chunked content transfer encoding";
see RFC 2616, chapter 3.6.1.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)

kenish...@duskmail.com

unread,
Apr 10, 2005, 4:57:38 AM4/10/05
to

t...@mail.localhost.invalid wrote:
> On 19 Mar 2005 09:54:39 -0800,
> "Yef" <e9...@yahoo.com> posted:
> Encoded characters. They might be trying to hide them from prying eyes, or
> they could be characters that need encoding to be part of the URI (due to
> the rules of what characters are allowed in them).
> --
> If you insist on e-mailing me, use the reply-to address (it's real but
> temporary). But please reply to the group, like you're supposed to.
> This message was sent without a virus, please delete some files yourself.

Thanks!

kenish...@duskmail.com

0 new messages