Hey there,
the server replies "Bad Request" when there is no whitespace between header-key and value.
Here is an example:
curl -v -H 'Accept:*/*' '192.168.178.144:8081/table/v1/driving/13.388860,52.517037;13.397634,52.529407;13.428555,52.523219'
Results in:
* Trying 192.168.178.144...
* TCP_NODELAY set
* Connected to 192.168.113.144 (192.168.178.144) port 8081 (#0)
> GET /table/v1/driving/13.388860,52.517037;13.397634,52.529407;13.428555,52.523219 HTTP/1.1
> Host: 192.168.178.144:8081
> User-Agent: curl/7.58.0
> Accept:*/*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 400 Bad Request
< Access-Control-Allow-Origin: *
< Content-Length: 0
< Content-Type: text/html
<
* Closing connection 0
But this is working:
curl -v -H 'Accept: */*' '192.168.178.144:8081/table/v1/driving/13.388860,52.517037;13.397634,52.529407;13.428555,52.523219'
The only difference between the two requests is one whitespace in the Accept-header. This whitespace is optional. For reference see here (in 3.2).
So the server should be able to deal with requests without whitespace in headers.
Hey there,
the server replies "Bad Request" when there is no whitespace between header-key and value.
Here is an example:
Results in:
But this is working:
The only difference between the two requests is one whitespace in the Accept-header. This whitespace is optional. For reference see here (in 3.2).
So the server should be able to deal with requests without whitespace in headers.