There seems to be servers/load balancers that insert one (or more?) whitespaces between the chunk-size number and \r\n. Most clients seems to accept this as I understand it, but fasthttp is more strict and fails. To fix it extra whitespaces needs to be thrown away in parseChunkSize()
There seems to be servers/load balancers that insert one (or more?) whitespaces between the chunk-size number and \r\n. Most clients seems to accept this as I understand it, but fasthttp is more strict and fails. To fix it extra whitespaces needs to be thrown away in parseChunkSize()