Nordin Ahdi wrote:

What details do you need to know?

As soon as it tries to connect to the web services the error occurs, that's all I know.

We have other SOAP web services that work perfectly fine but were made in OS9/OS10. I understand that SOAP has had an update, would this be the cause for this to happen? i would have thought that seeing as the web service was exposed using OutSystems and then consumed in OutSystems also they would work together well.

Nordin Ahdi wrote:

This is the stack from service center

[1] The remote server returned an unexpected response: (431) Request Header Fields Too Large.

Server stack trace:
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at ssHapiMobileApp.CcEmployeeSuggestions.ActionGetHomepageSuggestions(HeContext heContext, ICcEmployeeSuggestionsCallbacks _callbacks, Int32 inParamClientId, Int32 inParamPage, String inParamOrderBy, STArrayOfSuggestionItemStructure& outParamSuggestionList, STResponseStructure& outParamResponse)
   at ssHapiMobileApp.Actions.ActionGetHomepageWrapper(HeContext heContext, Int32 inParamPage, String inParamOrderBy, Boolean& outParamSuccess, String& outParamMessage, STArrayOfSuggestionItemStructure& outParamSuggestions)

[2] The remote server returned an error: (431) Request Header Fields Too Large.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Nordin Ahdi wrote:

Request Headers:

Request message:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
  <s:Header>
   
  </s:Header>
  <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <GetHomepageSuggestions xmlns="http://www.outsystems.com">
      <ClientId>136</ClientId>
      <Page>0</Page>
      <OrderBy>MostPopular</OrderBy>
    </GetHomepageSuggestions>
  </s:Body>
</s:Envelope>

Response Headers:

Response message:

Just changed the log level for the integration and it appears that the headers are empty

Migalhas wrote:

Yes I had a look but I didn't find it helpful when trying to solve the issue.