0
I have a banknote issuing service that was running normally on a VM on Azure. We migrated to a Google VM and now presents this error when the note has many products:
413 request Entity Too large
I have tried several possibilities by searching Google and we have found that, at first, the settings of the Service and IIS are the same in the two Vms, but Azure works and Google does not. This question may seem duplicated, but the solutions I found on other issues of the same problem did not help me.
You are passing the parameters by the url instead of the POST, that’s it! Probably the server may be set to accept a smaller number of characters than before.
– Wallace Maxters
But it’s by POST.
– Salatiel
If you enable the trace in the WCF service, does it arrive to log the message? If you do not know how to enable this, you can check this link: https://msdn.microsoft.com/pt-br/library/ms733025(v=vs.110). aspx I ask this to know who is limiting your post, whether it’s IIS or WCF.
– Ricardo Pontual
The same WCF on another server does not present this error. It is the same WCF publication (same files) on both servers and only on Google shows the error.
– Salatiel
If you have the same application and config, then probably the problem is with hosting on the Google VM. Have you tried to get support from them?
– Ricardo Pontual
We haven’t tried their direct support yet. We identified that when trying to import the WCF service installed in the Google VM, it presents an error, but when only changing the endpoint it works (but with error 413). We saw here that the DNS of the machine was changed and maybe the IIS had disfigured. We’re reinstalling everything and seeing if that’s the problem. If it doesn’t work, searching for Google support might be a good idea.
– Salatiel