Solution
This is an issue that can happen while continuously calling the Create Session and Destroy Session VIs for each request, causing the browser to accumulate session cookies to a point that it reaches a maximum header size limit.
We can see this process as:
- Create session.
- Get information.
- Send HTTP response.
- Destroy session.
Since the acquisition is continuous, it's not optimal to be constantly opening and closing sessions, so it would be better to just keep one session for this and just keep reusing it to reduce the server-side overheard and resources. Considering that, we can fix this by modifying the process as follows:
- Check if there's an open session (with Check If Session Exists VI).
- Create session if there wasn't one already.
- Get information.
- Send HTTP response.