Laurent Demailly

it would be good to see relatively new optional `-access-log-path` maybe tracks per connection ``` C1. --- - ----- C2. -- --- - ... ``` maybe diagonal so back to...

So it's supported through `-stdclient` standard go environment vars (e.g. HTTP_PROXY) but could be - explicit flag - working for fast client ## Discussed in https://github.com/fortio/fortio/discussions/539 Originally posted by **koustabhchatt**...

When viewing a report in the UI (make a run, then visit http://localhost:8080/fortio/browse to see results and click one or 2 (or n) having a table of the results similar...

tbd

migrate to github actions (from circleci)

5

maybe that'll help with the random failures; though the ssh to debug feature in circle is nice

when doing continuous runs, export stats periodically

9

when running with constant traffic, no stats are emitted until "the end" which isn't that useful it's also related to #134

investigate quic (then h3)

Support http proxy for fast client too

2

Follow up from #317 https://golang.org/pkg/net/http/#ProxyFromEnvironment

echo-server-default-params dflag showing up when fortio is used as library

2

fhttp/http_server.go: defaultEchoServerParams = dflag.DynString(flag.CommandLine, "echo-server-default-params", "", should be in fortio_main / commandline flags instead and passed

see what code can be simplified using go 1.14 (from 1.8)

1

follow up on #323