Requests that return "<url> malformed" also return last request's response #28

BigBlueHat opened this Issue Oct 17, 2011 · 3 comments


None yet
3 participants

If you:

resty http://localhost:5984
GET /test

It returns the expected result (information about the CouchDB database I'm getting info about).

However, if I do that, and then type it again--forgetting the opening slash:

GET test

I get:

* <url> malformed
* <url> malformed
* getaddrinfo(3) failed for test:80
* Couldn't resolve host 'test'
* Closing connection #0
* About to connect() to localhost port 5984 (#0)
*   Trying connected

and the remainder (headers and content) of my earlier request.

What I'd expect is the "Couldn't resolve host 'test'" response.


mdi commented Oct 1, 2012

This happens with a leading slash also.

@AdrieanKhisbe AdrieanKhisbe self-assigned this Nov 7, 2017

@AdrieanKhisbe AdrieanKhisbe added this to the v3.0 milestone Nov 7, 2017

@AdrieanKhisbe AdrieanKhisbe removed the bug label Nov 7, 2017


AdrieanKhisbe commented Nov 7, 2017

This is a feature

If the path parameter is not provided on the command line, resty will just use the last path it was provided with.

I'm gonna see if it's possible to disable it has a feature for 3.0

AdrieanKhisbe added a commit to AdrieanKhisbe/resty that referenced this issue Nov 7, 2017


AdrieanKhisbe commented Nov 7, 2017

there is now the feature to disable it

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