Re: [WebDNA] IIS 6.0 Custom Errors & WebDNA 6.2
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 103731
interpreted = N
texte = Terry Nair wrote: > Hi again, > > OK, after hours of research ....the conclusion, Errormessage DB the WebDNA > works fine for all HTTP Error Codes on IIS 5 on Win2003 server. As of IIS 6 > and higher ...ONLY HTTP Error Code 400 will NEVER be processed internally by > WebCat (ISAPI) through the Errormessage DB ....no matter what you do. You > can even try doing it the manual way through IIS Manager - Custom Error tag > and choose a different 400.htm file, URL or even change the 400.htm in the > system ...it will not work. > > Why ....damn MS hard coded that particular error response in the kernels > ....not like the rest of the custom errors (files). No way to view, modify > or change it. So, if you expect error response for type 400 to come out of > your WebCat on IIS6 ...keep dreaming because it would not. Real bummer > ....and damn you MS for not sticking a note somewhere to override what is in > your online technical manual ....heck, their tech manual still mentions it > as if it can be done. > > Hope this tidbit will save some poor soul using WebDNA on IIS 6 or higher on > the HTTP 400 response ... > > Cheers Terry Nair 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]**
Associated Messages, from the most recent to the oldest:
Terry Nair wrote: > Hi again, > > OK, after hours of research ....the conclusion, Errormessage DB the WebDNA > works fine for all HTTP Error Codes on IIS 5 on Win2003 server. As of IIS 6 > and higher ...ONLY HTTP Error Code 400 will NEVER be processed internally by > WebCat (ISAPI) through the Errormessage DB ....no matter what you do. You > can even try doing it the manual way through IIS Manager - Custom Error tag > and choose a different 400.htm file, URL or even change the 400.htm in the > system ...it will not work. > > Why ....damn MS hard coded that particular error response in the kernels > ....not like the rest of the custom errors (files). No way to view, modify > or change it. So, if you expect error response for type 400 to come out of > your WebCat on IIS6 ...keep dreaming because it would not. Real bummer > ....and damn you MS for not sticking a note somewhere to override what is in > your online technical manual ....heck, their tech manual still mentions it > as if it can be done. > > Hope this tidbit will save some poor soul using WebDNA on IIS 6 or higher on > the HTTP 400 response ... > > Cheers Terry Nair 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]**
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:
possible, WebCat2.0 and checkboxes-restated (1997)
Listfiles on network with NT (2000)
blank page from template (1997)
WC2b15 File Corruption (1997)
[numFound] inside [showIf]? (2000)
AppleScript: Tell application:app location? (1998)
Using Cookie for client specific info? (1997)
Template Not Found (1998)
test (2000)
Upgrading old WebCat Database Files (1997)
taxTotal (1997)
MacAuthorize and WebMerchant (1997)
Hosts who have upgraded to v5.0? (2003)
WebCat2b12 CGI Mac - [shownext] problem (1997)
WebDNA-Talk Digest mode broken (1997)
Error.html (1997)
Help with ShowNext (1998)
Shownext never shows next...still (1997)
WebCatalog can't find database (1997)
Max Record length restated as maybe bug (1997)