Re: mod_perl memory
Pavel Georgiev wrote: Thanks, that did the job. I'm currently testing for side effects but it all looks good so far. Glad someone could help you. I have been meaning to ask a question, and holding back. In one of your initial posts, you mentioned sending a response with a Content-type "multipart/x-mixed-replace". What does that do exactly ? A pointer would be fine. Thanks
Re: protecting internal redirects
Thanks for all of the suggestions. Looking for REDIRECT_* environment variables seems like it will work for me. 2010/3/19 Torsten Förtsch : > On Thursday 18 March 2010 21:59:26 E R wrote: >> To serve the file the CGI script issues an internal redirect to a url >> which points to the cached results. >> >> My question is: can the url which points to the cached results be >> protected so that it cannot be directly accessed by external clients? >> > When it creates the new redirected request (can I say "redirectee"?) apache > copies the environment variables of the original request to the new one. All > variable names are prefixed with "REDIRECT_". mod_rewrite should be able to > check the presence of one of them. > > Torsten Förtsch > > -- > Need professional modperl support? Hire me! (http://foertsch.name) > > Like fantasy? http://kabatinte.net >
Re: protecting internal redirects
On Thursday 18 March 2010 21:59:26 E R wrote: > To serve the file the CGI script issues an internal redirect to a url > which points to the cached results. > > My question is: can the url which points to the cached results be > protected so that it cannot be directly accessed by external clients? > When it creates the new redirected request (can I say "redirectee"?) apache copies the environment variables of the original request to the new one. All variable names are prefixed with "REDIRECT_". mod_rewrite should be able to check the presence of one of them. Torsten Förtsch -- Need professional modperl support? Hire me! (http://foertsch.name) Like fantasy? http://kabatinte.net
