inline C code and post data

[Cal Heldenbrand]

How difficult do you think it would be to provide this to the VRT level?
I'd be happy to do the coding if you point me in the right direction of
where the post data is handled in the source.

I think it would be a useful tool for the rest of the community as well.  (I
remember some mailing list post on doing security matching, similar to
Apache's mod_security)

Thanks, and happy hangover day!

--Cal


On Fri, Jan 1, 2010 at 5:18 AM, Poul-Henning Kamp <phk at phk.freebsd.dk>wrote:

> In message <6d0f643a0912311432v1e594e5cl601f1a5b19b59956 at mail.gmail.com>,
> Cal H
> eldenbrand writes:
>
> >I just started experimenting with the coolness of using inline C in VCL,
> and
> >I've run into a bit of a hurdle -- I can't find any VRT functions that
> allow
> >me to dig into the request body where the post data is at.
>
> The post data is not available at any point near VCL, it is transferred
> to the backend as part of the backend fetch.
>
> Poul-Henning
>
> PS: Happy NewYear
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20100101/9503f13a/attachment-0002.html>