Re: How Should IIS permissions be set to prevent hacking?
From: Karl Levinson [x y] mvp (levinson_k_at_despammed.com)
Date: 07/05/04
- Next message: StarView: "Re: How Should IIS permissions be set to prevent hacking?"
- Previous message: etm: "Re: TCP/IP Filtering and DNS problems"
- In reply to: Ken Schaefer: "Re: How Should IIS permissions be set to prevent hacking?"
- Next in thread: StarView: "Re: How Should IIS permissions be set to prevent hacking?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 5 Jul 2004 17:51:01 -0400
I know that's the way it's supposed to work. Based on past posts here, I'm
not sure that's the way it really works. There's this certain large
software company that makes browsers that tends to not read or follow RFCs.
"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:%23bd0bnpYEHA.2736@TK2MSFTNGP10.phx.gbl...
> Actually, the HTTP v1.1 spec says that each client should only open 2
> connections, so 10 concurrent connections = 5 clients. Also, you can edit
> the metabase so that you can get 40 concurrent HTTP connections (if you
try
> to set it to more, it will be reset to 10).
- Next message: StarView: "Re: How Should IIS permissions be set to prevent hacking?"
- Previous message: etm: "Re: TCP/IP Filtering and DNS problems"
- In reply to: Ken Schaefer: "Re: How Should IIS permissions be set to prevent hacking?"
- Next in thread: StarView: "Re: How Should IIS permissions be set to prevent hacking?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Loading