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!

404 Error when pushing to .config endpoints



  • Hi guys,

    I think i found a bug, when i am trying to push a file (of any extension) to an endpoint that ends with .config, I receive a 404 as response. For example:

    When i send this request:

    curl https://<<domain>>/endpoints/<<feed>>/content/somepath/exampleEndpoint.config --upload-file somefile.config --user user:pass

    I receive:

    <div id="content">
    <div class="content-container"><fieldset>
    <h2>404 - File or directory not found.</h2>
    <h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>
    </fieldset></div>
    </div>
    </body>

    But if i change my request to:

    curl https://<<domain>>/endpoints/<<feed>>/content/somepath/exampleEndoipint.config.xpto --upload-file somefile.config --user user:pass

    It responds with success.

    The 404 doesn't make sense because the asset at that endpoint doesn't exist because i am trying to push/create the asset. And if I change the endpoint from .config to other extension it gives me a success response. I am consuming this API 'https://docs.inedo.com/docs/proget/reference/api/asset-directories-api'. The previous requests are PUT.

    Can someone tell me if its a bug or I am making some mistake.
    Thanks for your time.


  • inedo-engineer

    That's strange, but it sounds like request filtering, WebDav, or some other security feature (outside of ProGet)... ProGet doesn't restrict anything by extension or anything like that.

    There's a few places to look, but i'd start here:

    https://stackoverflow.com/questions/12828476/what-file-extensions-are-blocked-by-default-in-iis

    Is that helpful?


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation