Re: Parsing a mostly partial url assupplied in a HTTP GET request-header
From: Eugene Gershnik (gershnik_at_hotmail.com)
Date: 02/28/04
- Next message: R.Wieser: "Re: Parsing a mostly partial url assupplied in a HTTP GET request-header"
- Previous message: Eugene Gershnik: "Re: Need help joining domains"
- In reply to: EricSten [MS]: "Re: Parsing a mostly partial url assupplied in a HTTP GET request-header"
- Next in thread: R.Wieser: "Re: Parsing a mostly partial url assupplied in a HTTP GET request-header"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 28 Feb 2004 02:44:35 -0800
EricSten [MS] wrote:
> "R.Wieser" <rwieser-killthis-@xs4all.nl> wrote
>> Not really. The program I'm writing is supposed to be the
>> "server" (a
> very
>> minimal one though :-).
>
> For which min OS platform are you targeting this minimal server?
> If you are
> on Windows Server 2003 and above, you have access to HTTPAPI, which
> is a
> very smooth way of servicing web requests without having to do all
> the heavy
> lifting of parsing the URLs. And let me tell you, URL
> canonicalization (c14n) is *the* hardest thing for a web server to
> get right... HTTP.SYS
> spent a lot of time making sure we did c14n right. <g>
>
Are you sure about that? ;-)
Being paranoid I would actually use anything _except_ MS APIs for server
side URL c14n. MS code makes you automatically vulnerable to all the
exploits people are so eager to develop.
-- Eugene
- Next message: R.Wieser: "Re: Parsing a mostly partial url assupplied in a HTTP GET request-header"
- Previous message: Eugene Gershnik: "Re: Need help joining domains"
- In reply to: EricSten [MS]: "Re: Parsing a mostly partial url assupplied in a HTTP GET request-header"
- Next in thread: R.Wieser: "Re: Parsing a mostly partial url assupplied in a HTTP GET request-header"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
