Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add socket closed/opened count to fast http client #165

Closed
ldemailly opened this issue Feb 28, 2018 · 1 comment
Closed

add socket closed/opened count to fast http client #165

ldemailly opened this issue Feb 28, 2018 · 1 comment
Assignees
@ldemailly

Comments

@ldemailly
Copy link
Member

so we can detect unexpected non reuse of socket
This was referenced Mar 2, 2018
Closed
Merged
ldemailly added a commit that referenced this issue Mar 4, 2018
@ldemailly
Add socket use count and don't consider early EOF an error
807aed0 
fixes #165
Added a test for close
Partial fix for #168 (show the result map on UI text part)
@ldemailly ldemailly self-assigned this Mar 4, 2018
ldemailly added a commit that referenced this issue Mar 5, 2018
@ldemailly
Multiple improvements/fixes (#173)
d33aeb7 
- add both link to UI and Json data from run results and browse UI
And a back to top link

- Fix #172 (error logged when using -H)

- Initial version of #170
 &close option for echo server

- Build with both go1.8 and 1.10; put 1.10 binaries in docker images/release

- Add StdClient option for the web UI runs

- Misc cleanups to front page (grpc secure option)

- Add socket use cout (#165)

- don't consider early EOF or other an error (fix 50% errors for some call client closes - like /fortio/fetch/ does)

- Reminder of fix for #168 show grpc result codes in UI/text

* Use submodule for docker test

* Fixed logging level for payload, add close= to doc, prep 0.7.3

* Code review comment - thx Doug
@ldemailly
Copy link
Member Author

fixed in #173

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ldemailly ldemailly

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ldemailly