Web services remote FAILS

Discussion for developers using MailEnable.
Post Reply
lweidig
Posts: 15
Joined: Thu Nov 14, 2013 8:19 pm

Web services remote FAILS

Post by lweidig »

We are trying to make use of the webservices to integrate with our site more completely. However, every time we try to POST remotely this fails with something like:

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>



HOWEVER, if we make the exact same POST request from localhost (even specifiying the FQDN name) it succeeds just fine. Seems like this might be an IIS setting or similar only allowing local access but we are Nginx / Linux guys and have no idea what is blocking this. We are sure they requests are 100% identical other than the host they originate from. We are testing using Postman.

Any help would be greatly appreciated!

lweidig
Posts: 15
Joined: Thu Nov 14, 2013 8:19 pm

Re: Web services remote FAILS

Post by lweidig »

Interestingly if I just access a page like:

http://mydomain.com/webservices/SystemO ... =SetOption

I do not get the HTTP POST section in the result that shows how to use the command only the SOAP 1.1 and SOAP 1.2 sections. However, that same URL locally then adds the HTTP POST section which is of course how we would like to access this.

Post Reply