RE: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 103733
interpreted = N
texte = 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). 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. 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 ------------------------------------ Hi Terry, Status code 400 would not generally be seen by WebDNA would it? " 10.4.1 400 Bad Request The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. " In otherwords, IIS would have to be able to know to send the parsing to WebDNA in order for WebDNA to see it.. and a request that is not understood would never make it there.... Now, if you are trying to emulate a 400 Bad Request.. perhaps by requiring a certain syntax to hit some WebDNA, you may be able to use [returnraw]? [showif [tUrlRequest]=NotformedRightForMyWebDNAApp] [returnraw]blah[/returnraw] [/showif] You are correct that each WebServer deals with this in different ways. We recently fixed the [returnraw] bugs that were in the apache 2.1x / WebDNA 6.x configs (such as in the 301 redirect). Apache changed the way they deal with status codes between 1.3 and 2.x as well and it seems this is one area that does change consistently in individual web servers. However, the bugs for ReturnRaw were not reported on the IIS side, so we have not looked at IIS in this regard as of yet. Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us old archives: http://dev.webdna.us/TalkListArchive/ Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288
Associated Messages, from the most recent to the oldest:
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). 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. 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 ------------------------------------ Hi Terry, Status code 400 would not generally be seen by WebDNA would it? " 10.4.1 400 Bad Request The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. " In otherwords, IIS would have to be able to know to send the parsing to WebDNA in order for WebDNA to see it.. and a request that is not understood would never make it there.... Now, if you are trying to emulate a 400 Bad Request.. perhaps by requiring a certain syntax to hit some WebDNA, you may be able to use [returnraw]? [showif [tUrlRequest]=NotformedRightForMyWebDNAApp] [returnraw]blah[/returnraw] [/showif] You are correct that each WebServer deals with this in different ways. We recently fixed the [returnraw] bugs that were in the apache 2.1x / WebDNA 6.x configs (such as in the 301 redirect). Apache changed the way they deal with status codes between 1.3 and 2.x as well and it seems this is one area that does change consistently in individual web servers. However, the bugs for ReturnRaw were not reported on the IIS side, so we have not looked at IIS in this regard as of yet. Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us old archives: http://dev.webdna.us/TalkListArchive/ Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288
"Terry Nair"
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:
WebCat2b13MacPlugIn - [include] (1997)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
Possible to reset Linux file permissions w/in webcat [shell] ? (2000)
Help! WebCat2 bug (1997)
WebCatalog not running after upgrade (2000)
recommendations for credit card software (1998)
Snake Bites (1997)
Not really WebCat (1997)
Search Folder? (1998)
WebDNA + SQL Server (2003)
converchars in sendmail context.... (2004)
WebCat2b12 - nesting [tags] (1997)
Was: Variables not being passed *back* (2000)
Beta 18 (1997)
Problems with [Applescript] (1997)
WebCat editing, SiteGuard & SiteEdit (1997)
Banner DNA (1997)
Navigator 4.01 (1997)
RAM problems, [appendfile] problems (1998)
Cart ID Duplication (2001)