-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy server not supported #83
Comments
Hi @MichelDaoust. Could you please share some more information? what exactly do you expect to achieve and what's the exact issue you're currently facing (a reference to the code and a full error stacktrace would be very appreciated). Thanks! |
Hi @roeeba , In project CloudinaryDotNet.Core.csproj If you look the result of the response in Api.Parse returned when you upload a file (from the CallAndParse function) you receive this HTTP reponse : {StatusCode: 407, ReasonPhrase: 'authenticationrequired', Version: 1.1, Content: System.Net.Http.NoWriteNoSeekStreamContent, Headers:\r\n{\r\n Cache-Control: no-cache\r\n Date: Mon, 05 Feb 2018 20:16:14 GMT\r\n Proxy-Authenticate: NTLM\r\n Proxy-Authenticate: Basic realm="xxxxxxxx.com"\r\n Proxy-Connection: Keep-Alive\r\n Content-Length: 4076\r\n Content-Type: text/html\r\n}} So look the authenticationrequired and there is not valid JSON in the body. So the result is when you get the JSON object from the response, you have this exception (because your HTTP response is now how you expect it) : fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[0] thank you. |
Hi @MichelDaoust, thank you very much for sharing the details and apologize for not responding earlier. I've opened a ticket with our dev team. We'll do our best to address this issue as soon as we can. |
Hi @MichelDaoust. While it's still on our roadmap to support this in-house, you may find the following solution helpful - https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/network/defaultproxy-element-network-settings |
Hi,
Thank you for you API but ...
Should return a good error (Proxy authentication) or better : Allow passing proxy info in the API. Now, the exception is a JSON token error, not really helpful.
Thank you.
The text was updated successfully, but these errors were encountered: