Support for query string

[ELC]

It would be nice if one could use kutt.it to shorten an API and pass parameters as query string

Example:

API url: https://wt-5fc6cb60e41eaeeb967dd305f92ba74a-0.sandbox.auth0-extend.com/hello
Shorten: https://kutt.it/elc-webtask-tutorial

Call API with parameters: https://wt-5fc6cb60e41eaeeb967dd305f92ba74a-0.sandbox.auth0-extend.com/hello?name=John
Desired: https://kutt.it/elc-webtask-tutorial?name=John

[trgwii]

This sounds doable, we're not currently using query parameters for anything, but maybe as an option during link creation in case we decide we need query parameters in the future?

[ELC]

It could be something like a checkbox with "Is this a link to an API?" If so all the query parameters in the shorten link will be passed to the original link. Security issues should be taken into consideration by the API developers and not by Kutt.it

An even more complete solution would be to, instead of redirect, send the same request object to the original URL, this would enable redirecting POST, PUT and DELETE, so one can have a FullRest with kutt.it.

[trgwii]

An even more complete solution would be to, instead of redirect, send the same request object to the original URL, this would enable redirecting POST, PUT and DELETE, so one can have a FullRest with kutt.it.

We don't want to be a full on proxy, so that won't happen

[ThreeDeeJay]

This sounds like a great idea. Any updates/consideration on the implementation?

[abett]

also very interested in this feature.

can you point me towards where we could add such a functionality in the code? (and also at concerns that kept you from implementing, if there are any)
I'd be happy to contribute to a solution that allows passing through the path / url-params.

[mariodian]

@ELC Please let me know whether the above change works for you. If so, I'll create a PR.

[ELC]

Seems like that will do