Thanks for the response. I tried compiling it and ran into issues. However, I am not sure that fundamentally this is the best approach. Replacing or injecting content into the proxied site content will work. I've tried modifying the body, head, html, script tags. It just hasn't worked reliably for me... for example with google.com or yahoo.com. I was wondering if doing an internal redirect, framing the url (so that it renders as normal) and placing my ads outside would be better. On Mon, Oct 26, 2009 at 2:59 PM, William A. Rowe, Jr. <wrowe@xxxxxxxxxxxxx> wrote: > Marcos Mendez wrote: >> Does anyone have any suggestions about what is the best way to >> implement an ad-supported proxy? I've got mod_substitute injecting >> some content, but it only seems to work on simple websites. Should I >> be looking at redirecting urls to a frame, and putting the ads there? >> Is there any other way of doing it? > > Take a look at mod_sed in trunk/; because it's a -full- implementation > of sed rather than just substitute-lines, so you can do line-oriented > insert/delete/buffer merge etc etc etc. > > mod_substitute is replaced with mod_sed in the next major httpd release > but you should be able to compile in that module without too much trouble > into 2.2. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|