Re: 302 Found

From: Christian (cgregoir99_at_yahoo.com)
Date: 03/11/05 

Date: Fri, 11 Mar 2005 19:04:46 +0100

"Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> a écrit dans le message
de news:OBnzpFmJFHA.2648@TK2MSFTNGP14.phx.gbl...
> "Christian" <cgregoir99@yahoo.com> wrote in message
> news:d0sghm$goa$1@reader1.imaginet.fr...
> > "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> a écrit dans le
message
> > de news:%23rToSIlJFHA.2132@TK2MSFTNGP14.phx.gbl...
> > > "Christian" <cgregoir99@yahoo.com> wrote in message
> > > news:d0s7tk$f1k$1@reader1.imaginet.fr...
> > > > Hello,
> > > >
> > > > On a Win 2000 SP4 server running IIS/5.0, when requesting a URL,
like
> > > > www.foo.com, I get the following reply from the server :
> > > >
> > > > HTTP/1.1 302 Found
> > > > Server: Microsoft-IIS/5.0
> > > > Location: /Default.aspx
> > > >
> > > > though, default.aspx is defined in the default documents for that
> site.
> > > >
> > > > Any idea what's wrong here, and why I don't get the 200 OK error
code.
> > >
> > > Does this explain the 302?
> > > http://support.microsoft.com/kb/298408/EN-US/
> > >
> >
> > Thanks for the reply, though I don't think this article is related to
this
> > issue since I do not access a subdir without the trailing slash.
> >
> > Here is what I get from the command line :
> >
> > C:> telnet www.foo.com 80
> > GET / HTTP/1.1
> > Host: www.foo.com
> >
> > HTTP/1.1 302 Found
> > Server: Microsoft-IIS/5.0
> > Date: Fri, 11 Mar 2005 16:25:54 GMT
> > X-Powered-By: ASP.NET
> > X-AspNet-Version: 1.1.4322
> > Location: /Default.aspx
> > Cache-Control: private
> > Content-Type: text/html
> >
> > <html><head><title>Object moved</title></head><body>
> > <h2>Object moved to <a href='/Default.aspx'>here</a>.</h2>
> > </body></html>
> >
> >
> > This server holds several other web sites developed using ASP.NET and
all
> > but this one work as expected. Having a look at their configurations, I
> > couldn't find any clear difference between them.
> >
> > Any other idea ?
>
> What happens if you "telnet www.foo.com/ 80"?
>

www.foo.com is one way to access the web server, the other being its IP
adress (say, telnet 123.45.67.89 80). Adding a trailing slash is useless.
Actually, it would not be a valid name.

Relevant Pages

  • Re: Restricting access to a web server by IP
    ... if you web server is windows 2k the use the rras function to filter the ... the internet you open up security issues. ... because you login into telnet using plain text and anyone using a sniffer ... I would look at the following security holes ...
    (comp.security.misc)
  • Re: Restricting access to a web server by IP
    ... if you web server is windows 2k the use the rras function to filter the ... the internet you open up security issues. ... because you login into telnet using plain text and anyone using a sniffer ... I would look at the following security holes ...
    (comp.security.firewalls)
  • Re: Restricting access to a web server by IP
    ... if you web server is windows 2k the use the rras function to filter the ... the internet you open up security issues. ... because you login into telnet using plain text and anyone using a sniffer ... I would look at the following security holes ...
    (alt.computer.security)
  • Re: Telnet and Apache
    ... You can telnet to any open port on a machine, and run the command manually. ... In terms of the web server, try telnetting in on port 80 (or whatever port ...
    (Security-Basics)
  • Re: Open Ports
    ... >Connection closed by foreign host. ... >Failure To Connect To Web Server ... different services: telnet, ftp, and http. ... The other daemon that I don't see, and should probably be running, is ...
    (comp.os.linux.security)