Does each HTTP Request have "Host:" header?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • mike

    Does each HTTP Request have "Host:" header?

    regards:

    Does each HTTP Request have "Host:" header?

    Any positive suggestion is welcome.
    thank you
    May goodness be with you all
  • Peter1968

    #2
    Re: Does each HTTP Request have "Host:&quo t; header?

    mike wrote:[color=blue]
    > regards:
    >
    > Does each HTTP Request have "Host:" header?
    >[/color]

    Yes.

    You're asking in the wrong place, though, as I'm sure you'll be told 14
    times by 12 other people. :)

    http://www.w3.org/Protocols/#Specs for some serious study on the subject.

    Comment

    • Peter1968

      #3
      Re: Does each HTTP Request have "Host:&quo t; header?

      Peter1968 wrote:[color=blue]
      > mike wrote:
      >[color=green]
      >> regards:
      >>
      >> Does each HTTP Request have "Host:" header?
      >>[/color]
      >
      > Yes.
      >
      > You're asking in the wrong place, though, as I'm sure you'll be told 14
      > times by 12 other people. :)
      >
      > http://www.w3.org/Protocols/#Specs for some serious study on the subject.[/color]

      Further to what I wrote; taken from RFC 2616:

      The most common form of Request-URI is that used to identify a
      resource on an origin server or gateway. In this case the absolute
      path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
      the Request-URI, and the network location of the URI (authority) MUST
      be transmitted in a Host header field. For example, a client wishing
      to retrieve the resource above directly from the origin server would
      create a TCP connection to port 80 of the host "www.w3.org " and send
      the lines:

      GET /pub/WWW/TheProject.html HTTP/1.1
      Host: www.w3.org

      followed by the remainder of the Request. Note that the absolute path
      cannot be empty; if none is present in the original URI, it MUST be
      given as "/" (the server root).

      Hope that helps you out.

      Comment

      • mike

        #4
        Re: Does each HTTP Request have "Host:&quo t; header?

        regards:

        Sorry,I am not very familiar with google NET forum.

        thank you for your patient reply and instructions.
        May goodness be with you all

        Comment

        • mike

          #5
          Re: Does each HTTP Request have "Host:&quo t; header?

          regards:

          Sorry,I am not very familiar with google NET forum.
          I will make a correction.

          thank you for your patient reply and instructions.
          May goodness be with you all

          Comment

          • Tim

            #6
            Re: Does each HTTP Request have "Host:&quo t; header?

            On 6 Apr 2005 00:06:30 -0700,
            s917124@mail.yz u.edu.tw (mike) posted:
            [color=blue]
            > Sorry,I am not very familiar with google NET forum.[/color]

            This is *usenet* (newsgroups), to which using Google is just one way to
            access it. It's usenet that you want to find out how to use. Don't pick
            up bad habits from web forums.

            Going from memory, there's a newsgroup with "newusers" as part of its name
            which has regular postings about how it all works, for new users to read.

            --
            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.

            Comment

            • John C. Ring, Jr.

              #7
              Re: Does each HTTP Request have "Host:&quo t; header?

              In article <E0y4e.1202$5F3 .203@news-server.bigpond. net.au>, Peter1968 <esmari@nonsens ebigpond.net.au > wrote:[color=blue]
              >mike wrote:[color=green]
              >> regards:
              >>
              >> Does each HTTP Request have "Host:" header?[/color]
              >
              >Yes.[/color]

              Off-topic, but...

              For HTTP/1.1, the Host: header is a required field. In HTTP/1.0, it is not
              even defined as a header. However, the Host: header became widely implemented
              in browsers before HTTP/1.1 to support name-based virtual web server hosting.

              So while your server *may* never see a HTTP request without a Host: header, it
              can certainly happen, so you should consider what to do in that case. Or if
              the Host: header provided makes no sense, or contains some type of system
              commands...

              Comment

              • Michael Stemper

                #8
                Re: Does each HTTP Request have &quot;Host:&quo t; header?

                In article <19r00l6mk4joq. 1hspd8cou0b74$. dlg@40tude.net> , Tim writes:[color=blue]
                >On 6 Apr 2005 00:06:30 -0700,[/color]
                s917124@mail.yz u.edu.tw (mike) posted:
                [color=blue][color=green]
                >> Sorry,I am not very familiar with google NET forum.[/color]
                >
                >This is *usenet* (newsgroups), to which using Google is just one way to
                >access it. It's usenet that you want to find out how to use. Don't pick
                >up bad habits from web forums.
                >
                >Going from memory, there's a newsgroup with "newusers" as part of its name
                >which has regular postings about how it all works, for new users to read.[/color]

                That would be "news.announce. newusers". Used to be most newsreaders were
                configured to come up subsciribed to that group until the user unsubscribed.
                Too bad that Web-based Usenet access providers can't be bothered to do that.

                --
                Michael F. Stemper
                #include <Standard_Discl aimer>
                Visualize whirled peas!

                Comment

                Working...