hi sometimes i connect local fiddler to another fiddler that is on my server
i intend use fiddler and filtering while bypassing my network's filters
but sometimes i receive this error
"The client failed to send a complete request on this REUSED connection before the timeout period elapsed; 0 bytes were read from client."
but its not always
after waiting 10~ seconds everything goes on
what may be the problem
http://i.imgur.com/tHzXLMJ.png
6 Answers, 1 is accepted
0
Hi, Mustafa--
What's the exact build number of the Fiddler in use?
You haven't mentioned how you "connect local fiddler to another fiddler"?
When a client fails to reuse a connection within the allotted time period, Fiddler will close the connection and return a HTTP/408 message (the text below). A client is expected to simply retry the request on a new connection.
Regards,
Eric Lawrence
Telerik
What's the exact build number of the Fiddler in use?
You haven't mentioned how you "connect local fiddler to another fiddler"?
When a client fails to reuse a connection within the allotted time period, Fiddler will close the connection and return a HTTP/408 message (the text below). A client is expected to simply retry the request on a new connection.
Regards,
Eric Lawrence
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items
0
Mustafa
Top achievements
Rank 1
Rank 1
answered on 27 Dec 2015, 12:18 AM
they are both latest windows version
i am connecting the fiddler at my pc to fiddler that is on my server
how should i configure to not get this error
0
Hello, Mustafa--
Two SAZ files (one from the client Fiddler instance and the simultaneous one from the server Fiddler instance) would probably help us see exactly what is going on here.
Having said that, you could probably fix this by going to your server instance of Fiddler and in the QuickExec box type each of the following lines and hitting enter after each:
prefs set fiddler.network.timeouts.clientpipe.receive.initial 115000
prefs set fiddler.network.timeouts.clientpipe.idle 115000
Restart that instance.
On the client instance of Fiddler, in the QuickExec box, type the following line and hit enter:
prefs set fiddler.network.timeouts.serverpipe.reuse 100000
Restart that instance:
Regards,
Eric Lawrence
Telerik
Two SAZ files (one from the client Fiddler instance and the simultaneous one from the server Fiddler instance) would probably help us see exactly what is going on here.
Having said that, you could probably fix this by going to your server instance of Fiddler and in the QuickExec box type each of the following lines and hitting enter after each:
prefs set fiddler.network.timeouts.clientpipe.receive.initial 115000
prefs set fiddler.network.timeouts.clientpipe.idle 115000
Restart that instance.
On the client instance of Fiddler, in the QuickExec box, type the following line and hit enter:
prefs set fiddler.network.timeouts.serverpipe.reuse 100000
Restart that instance:
Regards,
Eric Lawrence
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items
0
Mustafa
Top achievements
Rank 1
Rank 1
answered on 30 Dec 2015, 02:05 AM
i set the values as like you said i will inform you if same error happens again thanks
regards
0
Mustafa
Top achievements
Rank 1
Rank 1
answered on 08 Jan 2016, 01:19 PM
it doesnt happen any more
0
Hi Mustafa,
We are happy to hear that.
Let us know if you need further assistance.
Regards,
Boyan Boev
Telerik
We are happy to hear that.
Let us know if you need further assistance.
Regards,
Boyan Boev
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items