This is a Safari-specific issue. When using the fetch API in Javascript (but the same might happen when using XMLHttpRequest), safari refuses to send the content of the POST request.
Is there a way around this so it also works on Safari?
Ok so my problem was fixed by asking my tcp socket to continue receiving the request data until the body is equal to the content length:
headers, body = request_data.split("\r\n\r\n", 1) # Split request data into headers and body
# get the content length from the headers
content_length = 0
for line in headers.split("\r\n"):
if "Content-Length" in line:
content_length = int(line.split(": ")[1])
break
while len(body) < content_length:
body += conn.recv(1024).decode('UTF-8')
Basically what this means if you are not using a tcp socket and still wondering why this is happening:
Your web server did NOT receive the full request YET, safari sends it on chunks for some reason, hope this helps, keep receiving the request until the body of the POST is received.
Ok so my problem was fixed by asking my tcp socket to continue receiving the request data until the body is equal to the content length:
headers, body = request_data.split("\r\n\r\n", 1) # Split request data into headers and body
# get the content length from the headers
content_length = 0
for line in headers.split("\r\n"):
if "Content-Length" in line:
content_length = int(line.split(": ")[1])
break
while len(body) < content_length:
body += conn.recv(1024).decode('UTF-8')
Basically what this means if you are not using a tcp socket and still wondering why this is happening:
Your web server did NOT receive the full request YET, safari sends it on chunks for some reason, hope this helps, keep receiving the request until the body of the POST is received.
it works if make request api call with delay, like 500ms
No.
Apple has the interesting quality that it combines insane levels of attention in one place with insane levels of neglect elsewhere. This was also true for NeXT, so it might have been a cultural thing inherited when NeXT was acquired by Apple (and then the NeXT people started to run the show).
Hi Gerben,
It's really frustrating that this has been a problem for years and yet there is still not a definitive answer that I can find.
Did you have any luck elsewhere finding a solution?
This is madness. How can you ignore such a problem?
Safari doesn't properly send a http POST to a server, same code works on Chrome and Firefox)
