When I send a request where its URI has parameters' values causing it to be very long, the server endpoint's handler is not even called to function.
I placed a print statement at the beginning of the handler, and when I send a request with long URI, even this print statement is not triggered meaning that the handler is not called.
When I use shorter values for the parameters, it works.
Example :
Handler :
// handlers "/hello"
func CallbackHandler(ctx *fasthttp.RequestCtx) {
log.Println("/hello endpoint's handler is called")
url := ctx.Request.URI()
log.Printf("Callback URL: %s\n", url.String())
// Extract the authorization code from the query parameters
xVal := string(url.QueryArgs().Peek("X"))
log.Println("X value is : ", xVal )
}
when I send a request where the length of 'X' parameter's value is short (say 128char) to the endpoint, the server processes the request and executes the log.Println statements and I can see their outputs.
But, when I send a request where the length of 'X' parameter's value is long (say 1024char) to the endpoint, I do not get a valid response and I do not even see the log.Println statements' results.
What could be the problem here ?
Does fasthttp imply any constraints or limitations to URI length ?
When I send a request where its URI has parameters' values causing it to be very long, the server endpoint's handler is not even called to function.
I placed a print statement at the beginning of the handler, and when I send a request with long URI, even this print statement is not triggered meaning that the handler is not called.
When I use shorter values for the parameters, it works.
Example : Handler :
when I send a request where the length of 'X' parameter's value is short (say 128char) to the endpoint, the server processes the request and executes the log.Println statements and I can see their outputs. But, when I send a request where the length of 'X' parameter's value is long (say 1024char) to the endpoint, I do not get a valid response and I do not even see the log.Println statements' results.
What could be the problem here ? Does fasthttp imply any constraints or limitations to URI length ?