I need to be able to add proxy settings (including username, password and domain) for courier but having problems. Currently I'm getting
System.Net.WebException: The request failed with HTTP status 407: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. ). at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.GetAvailableRevisions(String username, String password) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.GetAvailableRevisions() at Umbraco.Courier.UI.Pages.editRepository.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoin
There's no way for Courier to pass the auth header to your proxy server on the way to the target instance unfortunately - hence the 407 error. One way I've seen folks work around this is to add a rule to the proxy that allows traffic between the instnaces running Courier.
I managed to get our network team to do exactly what you have just suggested and its worked so far. I do have another problem, but we do have support as well.
I'm going to give it another go tomorrow before logging a support call.
Problems with Courier behind our proxy server.
I need to be able to add proxy settings (including username, password and domain) for courier but having problems. Currently I'm getting
System.Net.WebException: The request failed with HTTP status 407: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. ).
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.GetAvailableRevisions(String username, String password)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.GetAvailableRevisions()
at Umbraco.Courier.UI.Pages.editRepository.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoin
@craig
There's no way for Courier to pass the auth header to your proxy server on the way to the target instance unfortunately - hence the 407 error. One way I've seen folks work around this is to add a rule to the proxy that allows traffic between the instnaces running Courier.
Thanks for getting back to me Paul.
I managed to get our network team to do exactly what you have just suggested and its worked so far. I do have another problem, but we do have support as well.
I'm going to give it another go tomorrow before logging a support call.
Craig
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.