When trying to use this library with a 67 column wide DataTable, I encounter the 414 HTTP error - Request-URI Too Long on the initial data load. DataTables is trying to send the view definition data using GET, which makes the URL extremely long (just over 15k characters in my case) and this triggers the 414 error.
I tried switching to POST method, but the request gets interpreted as a create request instead of a list request, so DRF tries to create a new instance of the model, populated by default values.
Is there a setting I am missing that will make data requests over POST work, or is this not supported?
PS: I am aware that raising the URI length limit is possible on the server side, but it is not the "correct solution" in my opinion. It's possible that I can't edit my webserver settings (in a managed enterprise environment for example) and as far as I am aware, some browsers also impose their own limit on the URI length, which the server owner can do nothing about.
When trying to use this library with a 67 column wide DataTable, I encounter the 414 HTTP error - Request-URI Too Long on the initial data load. DataTables is trying to send the view definition data using GET, which makes the URL extremely long (just over 15k characters in my case) and this triggers the 414 error.
I tried switching to POST method, but the request gets interpreted as a create request instead of a list request, so DRF tries to create a new instance of the model, populated by default values.
Is there a setting I am missing that will make data requests over POST work, or is this not supported?
PS: I am aware that raising the URI length limit is possible on the server side, but it is not the "correct solution" in my opinion. It's possible that I can't edit my webserver settings (in a managed enterprise environment for example) and as far as I am aware, some browsers also impose their own limit on the URI length, which the server owner can do nothing about.