-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input query/post data and return script stdout in response? #7
Comments
Yeah, placeholders aren't interpreted. Since this looks like a common use-case I will add that functionality. |
Any Update on this issue? |
git001
added a commit
to git001/caddy-exec
that referenced
this issue
May 4, 2022
xcaddy build \
--with github.com/aksdb/caddy-cgi/v2 maybe you want a cgi extension |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, and thanks so much for this great module. <3
I have looked for caddy-exec related issues and in the caddy documentation to see if I am missing something. But now I come to you, my last hope. :-)
My setup:
I'm building a caddy image with caddy-exec and caddy-hmac like so:
$PWD\docker-compose.yml
My
$PWD/config/secrets/local.env
file:$PWD/config/caddy/caddy.Dockerfile
And my
$PWD/config/caddy/Caddyfile
:My issue(s):
1.- So far I can pass my env vars to the scripts (not only python, but bash and other unforeseen languages), but the {query} shows up in the logs as {http.request.uri.query}, and not the intended string.
2.- Then I only see a JSON response giving a
success
status, orerror
status, but I do not see how to pass my scripts output to the response.Any insight about something that I'm obviously missing is appreciated. And thank you again for the support, documentation and development you have provided so far.
The text was updated successfully, but these errors were encountered: