Webcat not processed for CACHEd image error pages

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17383
interpreted = N
texte = I am having a problem with either Webcat 2.1.2 or the Webstar Data Cache plugin for 3.0.1) Set the Action for .gif to CACHE, BINARY for .jpg, and WEBCATALOG-PLUGIN for .html 2) Add some webcat code to your error.html file 3) Try to access http://www.yoursite.com/nonexistent.jpg (webcat processed) 4) Try to access http://www.yoursite.com/nonexistent.html (webcat processed) 5) Try to access http://www.yoursite.com/nonexistent.bogus (webcat processed) 6) Try to access http://www.yoursite.com/nonexistent.gif (webcat not processed) 7) Change the Action for .gif back to BINARY, and access nonexistent.gif again (webcat processed)So it looks like when the image is cached, webcat doesn't get a chance to process the code in the page. Is this a PIXO (or lack of PIXO) support issue? I would think the error.html page would be processed just like every other html page, regardless of how you got there. But then I'm not very familiar with how or in what order Webstar shuffles requests around internally...Can someone shed some light on this for me?Thanks,Dale ________________________ ______________________________ | Dale LaFountain | mailto:dalel@dhorse.com | | MIS Director,WebMaster | web: http://www.dhorse.com/ | | Dark Horse Comics, Inc.|Phone: 503-652-8815 x324 | \________________________|______________________________/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Webcat not processed for CACHEd image error pages (Peter Ostry 1998)
  2. Webcat not processed for CACHEd image error pages (Dale LaFountain 1998)
I am having a problem with either Webcat 2.1.2 or the Webstar Data Cache plugin for 3.0.1) Set the Action for .gif to CACHE, BINARY for .jpg, and WEBCATALOG-PLUGIN for .html 2) Add some webcat code to your error.html file 3) Try to access http://www.yoursite.com/nonexistent.jpg (webcat processed) 4) Try to access http://www.yoursite.com/nonexistent.html (webcat processed) 5) Try to access http://www.yoursite.com/nonexistent.bogus (webcat processed) 6) Try to access http://www.yoursite.com/nonexistent.gif (webcat not processed) 7) Change the Action for .gif back to BINARY, and access nonexistent.gif again (webcat processed)So it looks like when the image is cached, webcat doesn't get a chance to process the code in the page. Is this a PIXO (or lack of PIXO) support issue? I would think the error.html page would be processed just like every other html page, regardless of how you got there. But then I'm not very familiar with how or in what order Webstar shuffles requests around internally...Can someone shed some light on this for me?Thanks,Dale ________________________ ______________________________ | Dale LaFountain | mailto:dalel@dhorse.com | | MIS Director,WebMaster | web: http://www.dhorse.com/ | | Dark Horse Comics, Inc.|Phone: 503-652-8815 x324 | \________________________|______________________________/ Dale LaFountain

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] v7 Stress Test and Strange Behaviour (2012) [search] & [encrypt]/[decrypt] (2001) Ok, I'm stumped (1998) Directory Overload (1998) Question on TABLES (2003) WC2b15 - [HTMLx]...[/HTMLx] problems (1997) redirect with frames (1997) F*** you (1998) PCS Frames (1997) Summing fields (1997) Using Cookie for client specific info? (1997) RE: Custom error files (1998) Nested tags count question (1997) There's a bug in the math context ... (1997) [SubTotal] ??? (1998) still having shipCost.db Problem (1997) RAM variables (1997) cart converting to scientific notation format (2001) GoLive CyberStudio 1.0.1 (1997) [WebDNA] Updating WebDNA 8.x to WebDNA 8.2 (2016)