Re: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 103735
interpreted = N
texte = Terry Nair wrote: > Hi Donovan, > > IIS6 Windows 2003 does not handover the 400 Bad Request to WebDNA ...this I > can confirm. IIS 5 does. Simple test ...just point to a non-existent .htm > file (i.e. www.yyy.com/xxx.htm) and on IIS 5, the Errormessage DB is shown. > On IIS 6, it does not show up but the default kernel produced page (we are > all powerless to change this). Confirmed, kind of... technically, this is the description of a 404 status code, not 400. It appears IIS6 does a check for the existance of a file before the request is handed over to WebDNA... which is Wonky <-- Donovan's new favorite word. > Note that pointing to a non-existent folder (i.e. www.yyy.com/xxx/) will > point to the server default 400 page ...not through WebDNA Errormessage DB > ...both for IIS 5 and IIS 6. right... WebDNA only gets to look at files that are mapped to it via a suffix. Non existent directories would never be mapped to WebDNA for handling, nor would they assume an index file with appropriate mapping to WebDNA. > I am addressing the missing file and not folder URL type convention. You > see, when we run our monthly server maintenance back-up, we point the usual > domain URL link to an empty root directory. We want it that way so that we > can use the WebDNA Erromessage DB to issue codes in the return message when > a link is missing to a file that should be there. Meanwhile, we can do the > maintenance on the actual root folder. Maintenance completed, we switch back > the root to the original folder. We have POS terminal connected to the > WebDNA server DB 24/7 updating transactions ...so we have to issue one > paired value in the response when we take the system down for a short while. > The POS terminal are running our custom applications where if it finds the > maintenance code, escape to a holding page and prompts user. Anyway, this > works for ages on IIS 5 but not on our sparking new IIS 6 box which is 24 > days old ...damn. > > Hope that explain things a bit better and ...you bet, Status 400 is seen by > WebDNA for missing file (IIS 5 only) not folder ...;=) > > Cheers TDn Hmmm, Sorry, I'm not a Windows guy at heart and don't know of a solid solution.. however, it appears from some quick googlefu that you can create a custom page that is a redirect for use as your IIS 6 404 file. You may be able to build a system without too much trouble by taking the code you have in the 404 line of the errormessages.db and sticking it into some webdnafile... then, build that IIS redirect file and redirect to that new WebDNA file. The trick would then be making sure you are capturing all the original postdata... which I'm not sure how to do. Good luck, Donovan P.S. if you find that you would rather install linux on your new PC, We can do a free exchange of your recent Lic. purchase. -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 ("Terry Nair" 2009)
  2. Re: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 (Donovan Brooke 2009)
  3. RE: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 ("Terry Nair" 2009)
  4. RE: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 ("Terry Nair" 2009)
  5. Re: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 (Eddie Z 2009)
  6. Re: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 (Donovan Brooke 2009)
  7. RE: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 ("Terry Nair" 2009)
  8. [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2 ("Terry Nair" 2009)
Terry Nair wrote: > Hi Donovan, > > IIS6 Windows 2003 does not handover the 400 Bad Request to WebDNA ...this I > can confirm. IIS 5 does. Simple test ...just point to a non-existent .htm > file (i.e. www.yyy.com/xxx.htm) and on IIS 5, the Errormessage DB is shown. > On IIS 6, it does not show up but the default kernel produced page (we are > all powerless to change this). Confirmed, kind of... technically, this is the description of a 404 status code, not 400. It appears IIS6 does a check for the existance of a file before the request is handed over to WebDNA... which is Wonky <-- Donovan's new favorite word. > Note that pointing to a non-existent folder (i.e. www.yyy.com/xxx/) will > point to the server default 400 page ...not through WebDNA Errormessage DB > ...both for IIS 5 and IIS 6. right... WebDNA only gets to look at files that are mapped to it via a suffix. Non existent directories would never be mapped to WebDNA for handling, nor would they assume an index file with appropriate mapping to WebDNA. > I am addressing the missing file and not folder URL type convention. You > see, when we run our monthly server maintenance back-up, we point the usual > domain URL link to an empty root directory. We want it that way so that we > can use the WebDNA Erromessage DB to issue codes in the return message when > a link is missing to a file that should be there. Meanwhile, we can do the > maintenance on the actual root folder. Maintenance completed, we switch back > the root to the original folder. We have POS terminal connected to the > WebDNA server DB 24/7 updating transactions ...so we have to issue one > paired value in the response when we take the system down for a short while. > The POS terminal are running our custom applications where if it finds the > maintenance code, escape to a holding page and prompts user. Anyway, this > works for ages on IIS 5 but not on our sparking new IIS 6 box which is 24 > days old ...damn. > > Hope that explain things a bit better and ...you bet, Status 400 is seen by > WebDNA for missing file (IIS 5 only) not folder ...;=) > > Cheers TDn Hmmm, Sorry, I'm not a Windows guy at heart and don't know of a solid solution.. however, it appears from some quick googlefu that you can create a custom page that is a redirect for use as your IIS 6 404 file. You may be able to build a system without too much trouble by taking the code you have in the 404 line of the errormessages.db and sticking it into some webdnafile... then, build that IIS redirect file and redirect to that new WebDNA file. The trick would then be making sure you are capturing all the original postdata... which I'm not sure how to do. Good luck, Donovan P.S. if you find that you would rather install linux on your new PC, We can do a free exchange of your recent Lic. purchase. -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** Donovan Brooke

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:

MacAuthorize and WebMerchant (1997) searching for last file... WebCat solutions (1999) help wanted, still (1999) WebCat for paper collection, review and coordination ? (1998) WebMerchant docs and testing (2000) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Search in 2 or more catalogs (1997) Almost a there but..bye bye NetCloak (1997) I give up!! (1997) problems with WebCat-Plugin (1997) Formulas.db not working (2006) WCf2 and nested tags (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) more ! testing (1997) WCS Newbie question (1997) Post Test (2008) (1997) Subtotal help (1997) UPDATE PROBLEM (1997) [math] storage of variables (1997)