First rule of POST requests. Do not F*ck the URLs! URLs and query strings are only used to GET the data. When you are issuing an HTTP GET request, use Query Strings or URL routings etc. to get the data, add the filtering to the content. But when you are going to post the data, always use the request body and that is one of the reasons why you do not see a password field being appended to the URL when you log in, that data should be with (or in) headers or in the request body as a separate object. The request body is well suited for containing the data to be passed with the request, and then you can later access that data.
For more on request body, please read,
html - What does it mean http request body? - Stack Overflow[
^].
Quote:
All possible configuration settings tried in web.config, but still i am unable to post the request data.
Finally, a good group of server admins who are blocking poorly written API consumption. Take my advice, remove that query string, and start to accept the data as either a header as you would access data from any header, otherwise use the body and add the
[FromBody] attribute. Locally, you can tinker the server's good practices, and consider the bad ones.
Parameter Binding in ASP.NET Web API | The ASP.NET Site[
^]
Plus, there is a limit on the URL size itself; 2000 characters. Read more about it here,
http - What is the maximum length of a URL in different browsers? - Stack Overflow[
^]. This might be reason why your request is being invalid every time.
* Sorry, but this was the first expression that came to me when I read the question.
Submit an article or tip