Navigation

    Hedgehack community

    • Login
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Error: HTTP header is not fromated properly

    YCServer
    2
    9
    861
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • d.castignone
      d.castignone last edited by

      Hello
      I used YCServer to get Data from a NTRIP-caster with Basic Authorization, which is placed behind a proxy server. The proxy server does not forward the request from YCServer because the authorization header is apparently not terminated correctly with CRLF. Tests with other client were successful.

      Log-Output...
      accf5ada-755a-41e5-92e5-b058ef93dbbc-image.png

      Errmsg from Proxy...
      4d113bbd-824a-48e0-8547-e14633e8fab3-image.png

      BR, Daniel

      1 Reply Last reply Reply Quote 0
      • d.castignone
        d.castignone last edited by

        ... Extract from the official specification:
        0257405d-4925-4436-a91b-ed49661f61f8-image.png

        ilyavialkov 2 Replies Last reply Reply Quote 0
        • ilyavialkov
          ilyavialkov @d.castignone last edited by

          Hi @d-castignone,
          Thank you for your bug report. I will check it.

          1 Reply Last reply Reply Quote 0
          • ilyavialkov
            ilyavialkov @d.castignone last edited by

            @d-castignone Good catch. It was a base 64 encode function that added an extra new line character. Fixed in 1.49

            d.castignone 1 Reply Last reply Reply Quote 0
            • d.castignone
              d.castignone @ilyavialkov last edited by

              @ilyavialkov perfect! thank you

              d.castignone 1 Reply Last reply Reply Quote 0
              • d.castignone
                d.castignone @d.castignone last edited by d.castignone

                @d-castignone hello,
                there is still an incompatibility with the HTTP 1.1 standard:
                Here the msg from widely used Apache Proxy Server:
                AH00569: client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /CHEnnnn

                it looks like the mandatory "Host" header is not sent:

                6fd471ca-8717-432f-8178-2d94c9b531b3-image.png

                6a3d9814-2c1e-4347-a3fe-39d2fe30a5da-image.png

                it would be awesome if this could be fixed as well
                BR, Daniel

                ilyavialkov 2 Replies Last reply Reply Quote 0
                • ilyavialkov
                  ilyavialkov @d.castignone last edited by

                  @d-castignone No problem. I will add this header next week.

                  1 Reply Last reply Reply Quote 0
                  • ilyavialkov
                    ilyavialkov @d.castignone last edited by

                    @d-castignone Host header was added in 1.50

                    d.castignone 1 Reply Last reply Reply Quote 0
                    • d.castignone
                      d.castignone @ilyavialkov last edited by

                      @ilyavialkov
                      works now perfectly. thank you!

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Powered by NodeBB | Contributors