Http/Https - why doesn't google chrome send the entire request body to the server?

Question

JavaScript

There is a web server, self-written. During authorization, the browser exchanges data with the server. In Firefox, everything works fine (version 51.0 is the latest at the moment), but google chrome 1 request/response (post) goes well - I see in the console that all the OK data is correct, 2 the request from chrome is no longer complete, and specifically there is no request body - it is empty, I repeat that for some reason everything works fine in Firefox.
1st request I do like this

$.ajax({
          async: false,
          type: 'POST',
          url: 'https://127.0.0.1/',
          data: msg,
          success: function(data)

the second race is already a request coming from the html form

<form class="form-login" method="post" onsubmit="encryptAuthData();" enctype="text/plain" id="t_data">

                        <input type="text" id="user_name" class="login" required="" autofocus="" placeholder="Login or Email" name="AuthLogin">
                        <input type="password" id="user_pass" required class="password" placeholder="Password" name="AuthPass">
                        <input type="submit" class="to-send" value="sign in" id="send_login_data" form="t_data">
                        <input type="submit" class="to-send" value="forgot password" id="send_forgot_data" form="">

                    </form>

And another moment when I turn off https and use only http, everything works in chrome. I can't figure out what the problem is. I thought there were no restrictions on the length of the body - they don't seem to exist. Although it's strange that with http in chrome everything works fine too.

Answer 1

There is a web server, self-written.

State?
It seems that somewhere here the dog rummaged.
Well, it's not very clear about races and testing ...
Incomplete request body, empty request body - decide.
Where is the query dump itself?