Changelog History
Page 3
-
v1.6.1 Changes
July 21, 2020🛠 Fixes #373 (security patch) + some docs and small improvements
Reminder from 1.6.0:
👍 Big new change in the new dflag support, when adding the flags debug endpoint handler you can now also add a SetFlag handler and URL to enable edits
👀 See standalone example and how it's used in fortio UI
🌲 Also simplified the api and better logging for dflag, configmap etc
-
v1.6.0 Changes
July 21, 2020👍 Big new change in the new dflag support, when adding the flags debug endpoint handler you can now also add a SetFlag handler and URL to enable edits
👀 See standalone example and how it's used in fortio UI
🌲 Also simplified the api and better logging for dflag, configmap etc
-
v1.5.0 Changes
July 17, 2020🚀 Pretty big change in this release!
↔ Integrated the (originally
go-flagz
now dflag) dynamic flag library in fortio
(usable independently as fortio.org/fortio/dflag)
it gives a new flags debugging endpoint: http://localhost:8080/fortio/flags
and a new configmap directory; e.g;-config /etc/fortio
and where you can change theloglevel
flag dynamically👀 See dflag for more details on dynamic flags
-
v1.3.1 Changes
February 02, 2019🔄 Changes/bug fixes:
- 🛠 Fixed #312 - 100% error erroneously shown in UI for GRPC tests - thanks @olimpias
- 📦 Debian sbuild working (#307) - Help to turn this into an accepted package welcome - @ldemailly
- When using the standard (slow) http(s) client, proxy settings from environment are respected (#317) - thanks @costinm
- 💻 In the UI, new + button to add more custom headers (#308) - thanks @SeriyBg
-
v1.3.0 Changes
September 14, 2018🆕 New/Changes:
✅ Debian packaging support, new makefile targets:
dist
,dist-sign
,official-install
,debian-dist-test
,debian-dist
🆕 New location in docker image :
/usr/bin/fortio
for the binary,/usr/share/fortio
for the resources🐳 Docker volume for data is
/var/lib/fortio
but the default data directory is "." (current directory) for all installs. That data dir location is now printed at startup, e.g.:Fortio 1.3.0 grpc 'ping' server listening on [::]:8079 Fortio 1.3.0 https redirector server listening on [::]:8081 Fortio 1.3.0 echo server listening on [::]:8080 Data directory is /Users/ldemailly/go/src/fortio.org/fortio UI started - visit: http://localhost:8080/fortio/ (or any host/ip reachable on this server) 11:53:00 I fortio_main.go:213> All fortio 1.3.0 bf3f2d9ff07ed03ef16be56af20d58dc0300e60f go1.11 servers started!
- ⚡️ updated grpc to 1.15
-
v1.2.2 Changes
September 07, 2018🔄 Changes since v1.2.1: #302 we now build Debian (.deb) and RPM (.rpm) packages
Note: still to do (and help welcome) push those to official ubuntu, etc.. apt repositories (how?)
-
v1.2.1 Changes
August 29, 2018🚀 This is a minor bug fix (#298) compared to Fortio v1.2.0 + switched the build to use go 1.11 (and corresponding new lint warning fixes), while still being compatible with go 1.8
-
v1.2.0 Changes
August 28, 2018🚀 Early September release, Fortio is now standalone from Istio (while still being the synthetic load testing of choice of Istio) at https://github.com/fortio/fortio
🐛 Bug fixes:
- 🛠 Fixed duplicate Content-Type and Authorization headers (in connections past the first one) #292
- 🛠 Fixed doc lint errors #285
- 🛠 Fixed UI link to use https://fortio.org instead of http #286
- 🛠 Fixed the
fortio.fcurl
andfortio.echosrv
smaller docker images build (now at https://hub.docker.com/r/fortio/ , from istio/ previously)
🔄 Changes (incompatible with 1.1, thus 1.2 version) :
- 📚 Across the documentation and code base: changed vanity package url from istio.io/fortio to fortio.org/fortio #289
- Changed http client user agent to
fortio.org/fortio-*
(fromistio/fortio-*
) and default volume data directory to/var/lib/fortio
(from/var/lib/istio/fortio
) - 🔄 Changed JSON for GRPC results to use names/string from numerical code #290 - thanks @olimpias for the contribution.
-
v1.1.0 Changes
August 13, 2018A couple of cool new features in fortio 1.1:
👌 Support for Unix Domain Sockets for both the server and the client (#276)
eg.
fortio server -http-port /tmp/fortio/http-uds1
and
fortio load -unix-socket /tmp/fortio/http-uds1 http://localhost/echo
🚀 Support for random payload generation or file based POST content for both gRPC and http (#270, #273 / #280 - Thanks @olimpias for the contributions) - Note there is a bug (#291) in header generation in this release which is fixed in 1.2.0
- You can switch http client calls from GET to POST using
-content-type
- Or using
-payload-file
to specify the the content of the POST body - Or using
-payload-size
to generate a random binary body of that size - Or using
-payload
to send a small string as the body
🛠 And host of fixes and minor improvements (bug fix around custom headers and user authentication header, better
fortio help
output, etc...) - You can switch http client calls from GET to POST using
-
v1.0.1 Changes
June 28, 2018🚀 Very minor patch release for fortio 1.0 with a couple of code and build clean up (in part for Mac homebrew so
brew install fortio
andfortio version
shows the correct version)Also
fortio help
(andfcurl -help
) will show the help on stdout instead of stderr (#264).👀 See full change list.