Quantcast
Channel: [Q&A - FAQ Neotys] Last questions
Viewing all articles
Browse latest Browse all 2283

Сlipped response in "User Path Validity"

$
0
0

Dear colleagues,

I am requesting using postman/fiddler using:

GET clipped
https://XXXX/XXX_demo2/Account/Login?Token=XXX&Client... with header(see image.png).

Without changing anything in header and in request url I always get constant expected result length 4475 characters with header:

and body starting with <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;
<html xmlns="http://www.w3.org/1999/xhtml&quot; style="height: 100%;"> ,

same response was recorded during neoload recording :

But when I replay it using NeoLoad, response body is correct but starts with der">&nbsp;<span class(middle of HTML header), the begging of response body is clipped by some reason, and in response header it mentioned Content-Length: 6270(should be 4475).

It is very confusing, because such behavior tracked only in NeoLoad, when Explorer, Chrome and Postman and fidler works as expected with absolutely same parameters.

Please, advice what could cause such issue, because it is a limitation only on NeoLoad(version 6.9 was used) side.


Viewing all articles
Browse latest Browse all 2283

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>