Hi,

I am using Wuzz to test my JSON API endpoint. The problem is Wuzz doesn't format the response body. From the code I see that Wuzz only format if the config is true and Content-Type is application/json while JSON API require the server endpoint return the Content-Type as application/vnd.api+json.

Do you have suggestion to solved this?

You've done a great work with Wuzz.

Thank you.

the query syntax is using https://github.com/tidwall/gjson

If there is a need, we can create a new query syntax but that is not necessary at this moment.

I also took out the search code into search.go, I hope that is okay. This way, we can put all the searching code in one place.

Issue https://github.com/asciimoo/wuzz/issues/40

I think we're reaching the point where wuzz could use a config file. For syntax, I suggest TOML, which I've used before and is quite easy to integrate into Go.

There are a couple things that need to be decided on for the config file:

• Config sections and keys
• Available settings
• Default config location
• Command-line flag to specify a different config location

codecat@codecat-HP:~/mycode/go/src/github.com/asciimoo/wuzz$ go install
# github.com/nwidger/jsoncolor
../../nwidger/jsoncolor/jsoncolor.go:225: enc.SetEscapeHTML undefined (type *json.Encoder has no field or method SetEscapeHTML)

I thought this was a really neat tool, but I don't currently have go set up on my computer, so I set it up to run in docker and published an image here: https://hub.docker.com/r/nevon/wuzz/

I would much rather have that be automatically built whenever there's a push to master in here, though, so I thought I'd do a PR and see if you were interested. If you are, all you have to do in order to have an automated build is to go to docker hub, click the "automated build" thing, choose this repo and you should be good to go. By default it will build and tag with latest for master, and tag with branch-name for branch pushes.

It's nothing special, really, the only weird thing is that I had to sleep for a tiny duration before running wuzz, because otherwise I would get an error from gocui. I think it has something to do with docker run -it running the command before actually attaching.

This PR uses the jsoncolor package to colorize JSON bodies. It changes the imports to use my forked version of github.com/jroimartin/gocui which includes a small patch to support zero-parameter CSI escape sequences. I have submitted a PR upstream:

https://github.com/jroimartin/gocui/pull/98

Once that PR is merged the import can be switched back to github.com/jroimartin/gocui if desired.

Hi,

First of all, thank you for the utility. It is just great!

I wanted to propose a feature (which will let me forget about CocoaRest app) of saving requests (with its parameters.

Usually, how I use the utility, I have some small number of requests that have to work on my API. I test my API (same endpoints) with the utility until they work.

It would be much easier for me if I could save the requests.

Thank you!

The new configuration system, using TOML, loads into app.config using a TOML config file. This can be specified on the command-line with the -c option, or it can be at one of the following default locations:

• Linux: $XDG_CONFIG_HOME/wuzz/config.toml (by default this is ~/.config/wuzz/config.toml)
• Other OSs: ~/.wuzz/config.toml

Currently the following keys can be set, along with their default values:

[general]

timeout = "1m" # string parsed into time.Duration
formatJSON = true # toggles JSON formatting
preserveScrollPosition = true # currently unused
defaultURLScheme = "https" # when a URL is not provided, this is the scheme used by default

In addition, a [keys] section can also be set and will be successfully parsed, but it is currently non-functional.

• Disable multiline on url, method & search views by creating a singlelineEditor
• Add HOME END shortcuts to theses views to jump at beginning and end of line according to #27
• Arrow up & down on url and search view jumps at beginning and end of line
• Arrow up & down on method view change the method in the same order of the method-list popup

If you have not previously installed termbox-go you will get an error when you attempt to install the project.

$ go get github.com/asciimoo/wuzz
# github.com/jroimartin/gocui
../../.gocode/src/github.com/jroimartin/gocui/keybinding.go:74: undefined: termbox.MouseRelease

Informing the user they need termbox-go would be helpful so I have included it in the readme.

First off, thanks for a great tool for exploring web apis.

I was using it to access Github's API and went to put in the auth header (eg Authorization: Basic dGVzdHVzZXI6bm9wYXNzbm9wYXNzbm9wYXNzbm9wYXNzbm9wYXNzbm9wYXNzbm9wYXNzbm9wYXNz), the display shows some characters on the next line:

If I adjust the characters to be on the line above, like this, it works:

Thanks again.

What happened？

There are 1 security vulnerabilities found in github.com/tidwall/gjson v1.6.0

• CVE-2020-36066

What did I do？

Upgrade github.com/tidwall/gjson from v1.6.0 to 1.9.3 for vulnerability fix

What did you expect to happen？

Ideally, no insecure libs should be used.

The specification of the pull request

PR Specification from OSCS

When i try and edit something in the request fields using my cursor all i get is A, B, C, D. This makes using wuzz really frustrating when I'm editing requests and trying different things. The same goes for the copy and paste issue.

Try using wuzz to play around with something like https://overthewire.org/wargames/natas/ and you'll see what i mean.

I cannot build wuzz with go 1.18:

$ go version
go version go1.18 darwin/amd64

$ sw_vers
ProductName:	macOS
ProductVersion:	12.3
BuildVersion:	21E230

$ go install github.com/asciimoo/wuzz@latest
# golang.org/x/sys/unix
go/pkg/mod/golang.org/x/[email protected]/unix/syscall_darwin.1_13.go:29:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.1_13.go:27:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.1_13.go:40:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:28:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:43:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:59:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:75:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:90:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:105:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:121:3: //go:linkname must refer to declared function or variable
go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_amd64.go:121:3: too many errors

Go net/http request can be traced using net/http/httptrace.

This extension enables tracing, capturing of relevant events in a ring buffer and introduces a new view, displaying the buffers contents.

Sometimes it would be quite useful to not only see the request result headers and body, but also connection handling information.

Especially with HTTPS connections any packet tracer is not sufficient, so gathering tracing information from within HTTP client library seems to be the best option.