Neotys.com

Unanswered question

Request header too large

header_size_too_big.PNG header_size_too_big.PNG
header_size_too_b...
166 KB
November 10, 2017
Processed

When checking my userpath I get the following error:

Error detected by NeoLoad
Error Code: NL-NETWORK-01 Message: Network error: An IO error occurred sending the request.
Details: java.io.IOException: Request header too large
Please refer to the documentation for further details and advice

The script used to work and I didn't change anything.
I tried turning off cookies in the browser settings but this didnt work.

As you can see in the screenshot request it is pretty big and the Fedauth value is present 4 times. Should it not overwrite this value instead of adding a new addition each time?

header_size_too_big.PNG header_size_too_big.PNG
header_size_too_b...
166 KB
November 10, 2017
Processed
matthijs B.
matthijs B.

matthijs B.

Level
0
77 / 100
points
Answer count
10 answers
Category
NeoLoad Runtime
Author name
matthijs B.
Date
November 10, 2017
about 7 years ago
Hits
viewed 579 times
question
q

Answers

Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

The name of your cookies are different so from one i can see NeoLoad should not overwrite them since they are different.

You should check why the server is sending back those different cookies name. Is it when you run multiple iterations of your user in the check virtual user?

 

Author name
Nouredine A.
Date
answer
a
matthijs B.
matthijs B.

matthijs B.

Level
0
77 / 100
points

It happens with 1 iteration. It used to work so maybe they changed the cookies.

Author name
matthijs B.
Date
answer
a
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

Ok here is what you can try. In your NeoLoad script you can remove all the recorded cookies. They are just here for debugging purpose. But if for any reason your application is not sending back the same cookie names then NeoLoad might send back the old cookies too.

Backup your script in case and from the menu "Edit" use the Search&Replace feature. Select the fourth option "Search in request headers" then third option "Search in names and delete header".

String to search: Cookie

Nothing in the other field.

That should remove all your recorded cookies. Apply to all the occurrences and run again a check virtual user.

Author name
Nouredine A.
Date
answer
a
matthijs B.
matthijs B.

matthijs B.

Level
0
77 / 100
points

Now I get an assertion error. A certain variable can't be found so the response is wrong to continue with the script. The wrong response happens a bit before the "Request header too large" happens.
It doesn't run as far without the cookies.

Author name
matthijs B.
Date
answer
a
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

You should check the server response if it contains any error or any information regarding that assertion issue.

I'm wondering if your application has changed since your last recording. Could you try to make another recording and check again?

Author name
Nouredine A.
Date
answer
a
matthijs B.
matthijs B.

matthijs B.

Level
0
77 / 100
points

I get an error message because it seems to need to the cookies.

I have tried to record it again and got the same result.

Author name
matthijs B.
Date
answer
a
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

Removing the recorded cookies should not impact the runtime of the script except if your application is using client cookie.

I can't tell much about your issue without seeing the script and the check virtual user.

Author name
Nouredine A.
Date
answer
a
matthijs B.
matthijs B.

matthijs B.

Level
0
77 / 100
points

I rerecorded the script and then deleted the Cookies like you told me. Now it doesn't stop at an earlier step. That seemed to be a different program.

I do still get the same error message I'm afraid. Thanks for the help so far by the way.

Author name
matthijs B.
Date
answer
a
matthijs B.
matthijs B.

matthijs B.

Level
0
77 / 100
points

It seems that the cookie has doubled in size since the script has worked. I compared that recording to the new one.

There used to be FedAuth1 till FedAuth3
But now there is also
BNES_FedAuth1 till BNES_FedAuth3

There must have been a change somewhere in the code

cookie_doubled.JPG cookie_doubled.JPG
cookie_doubled.JPG
261 KB
November 14, 2017
Processed
Author name
matthijs B.
Date
answer
a