Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    [ProGet] Invalid URI when accessing feed

    Scheduled Pinned Locked Moved Support
    4 Posts 3 Posters 26 Views
    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.
    • P Offline
      pariv_0352
      last edited by

      I run proget behind reverse-proxy. And that proxy sits on non-standard port.
      And all works fine, but when I'm trying to access feed through browser it fails with Server Error 500: Invalid URI: The hostname could not be parsed.

      If I run proget on non-standard port without reverse-proxy feed access works.
      Looks like when proxy sets header X-Forwarded-Host to something with explicit port, it fails.
      e.g. www.testdomain.com:82.

      I found out that X-Forwarded-Host header is not very well defined in the case of ports. But I think proget shouldn't throw exceptions in this scenario and show feed page.

      There is a workaround to set Web.BaseUrl, but its not suitable for me, because port may change over time. And I dont want to change Web.BaseUrl every time it changes.

      dean-houstonD 1 Reply Last reply Reply Quote 0
      • dean-houstonD Offline
        dean-houston inedo-engineer @pariv_0352
        last edited by dean-houston

        Hi @pariv_0352,

        What version of ProGet are you using?

        Perhaps this is related to this:
        https://forums.inedo.com/topic/3596/proget-2022-6-the-hostname-could-not-be-parsed

        Dean

        1 Reply Last reply Reply Quote 0
        • P Offline
          pariv_0352
          last edited by

          I use Version 2023.9. And yes, I saw that thread, but looks like it is a bit different.

          stevedennisS 1 Reply Last reply Reply Quote 0
          • stevedennisS Offline
            stevedennis inedo-engineer @pariv_0352
            last edited by

            Hi @pariv_0352,

            Thanks for clarifying; looking closer, ProGet requires that X-Forwarded-Host is simply a hostname. You're right, there is no "standard" for this, but that's what ProGet does for the time being.. and if the input is invalid, then you get the error you'll see.

            I would change your reverse-proxy header configuration to:

            • X-Forwarded-Host: www.testdomain.com
            • X-Forwarded-Port: 82

            Hope that helps,
            Steve

            1 Reply Last reply Reply Quote 1

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post
            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation