<br><br><div class="gmail_quote">On Thu, May 6, 2010 at 6:54 PM, agentzh <span dir="ltr"><<a href="mailto:agentzh@gmail.com" target="_blank">agentzh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Fri, May 7, 2010 at 1:56 AM, Matthieu Tourne<br>
<<a href="mailto:matthieu.tourne@gmail.com" target="_blank">matthieu.tourne@gmail.com</a>> wrote:<br>
> The new version of the echo module looks great, and it's a very good source<br>
> of inspiration for writing my own module.<br>
<br>
</div>Glad to hear that :)<br>
<div><br>
> I think that would be amazing if the echo module could be used to "pipe"<br>
> echo directives to an upstream, in order to create completely custom queries<br>
> for example, instead of echoing data back to the user.<br>
<br>
</div>This is a very intriguing idea and I can see the benefits of debugging<br>
custom TCP upstream modules :)<br>
<br>
Just to confirm my understanding, I'd ask first...are you suggesting a<br>
telnet module for nginx upstreams? *grin*<br>
<div><br>
> Do you think that would be feasible ?<br>
<br>
</div>Given the flexibility of the nginx core, I'd say "yes" :)<br>
<br>
To be honest, I happen to be thinking about mudding with the<br>
ngx_http_upstream infrastructure a bit more these days ;)<br>
<br>
Cheers,<br>
<div><div></div><div>-agentzh<br></div></div></blockquote></div><div><br></div>Yes, I guess that could be done with a telnet upstream module,<div>then I could just do something like : </div><div><br></div><div>echo_subrequest /telnet_upstream -b "GET / HTTP/1.0\n ..." to completely craft queries.<br clear="all">
<br></div><div>That could also be useful to me, for example to let an untouched query go through,</div><div>using something like : </div><div><br></div><div>echo_read_request_body;</div><div>echo_subrequest $echo_request_method '/telnet_upstream' -b $echo_client_request_headers$echo_request_body;</div>
<div><br>-- <br>Matthieu Tourne<br>
</div>