Re: [WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file?

This WebDNA talk-list message is from

2009

It keeps the original formatting. numero = 102285
interpreted = N
texte = There was a bug in Return Raw, you may want to check. Not sure which version or if it affected all platforms. I know the bug was in v5.x on WindowsRegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 28/03/2009, at 8:20 AM, Govinda wrote:> Hi all>> Despite 10+ years of successful HTML,WebDNA, (and other related > languages) I've only just now been doing my reading about HTTP > status codes, etc.>> Anyway I have a page from a new clients' inherited site that has an > include that uses [ReturnRaw] in order to set a cookie and then > redirect.., and when I inspect the html source sent back I see that > there is nothing coming back at all from the include, and there is > also none of the HTML below that include in the original file > either. So somewhere it is choking on the included file. This file > was working fine on the previous Mac os x 10.2.8 server, wc 5.1c, > Webstar V host. (Now I am trying to get this to work on RedHat 4 64 > bit. ) To troubleshoot, I have commented out the entire contents > of the include and just started with this (uncommented) test:>> -----------------------start source code------------> [ReturnRaw]HTTP/1.0 200 OK> Status: 200> Content-type: text/html>> >> [/ReturnRaw]> [!]> my previously-working code here commented out.> [/!]> -----------------------end source code------------>> I also tried this:>> -----------------------start source code------------> [ReturnRaw]HTTP/1.0 302 Found>> Location: http://www.google.com/[!]---[Lookup db=../ > preferences > .db&lookinfield=PrefName&value=PrimaryDomain&returnfield=PrefValue]/ > admin---[/!]>>> [/ReturnRaw]> [!]> my previously-working code here commented out.> [/!]> -----------------------end source code------------>> But I am getting the same behavior. (Nothing is coming back from > the include, nor even any of the code in the file that includes this > include *after* the [include ..] tag.) I.e. it is dying somewhere > while trying to parse the include. (When I view source from the > browser then all I see is the html that the including file spits out > before we get to the include.)>> On my new imac I see in BBedit that the local copy of the file does > indeed have windows CRLF set for the line endings. and encoding is > set to 'western MacOS Roman'. But after I upload and then open that > file directly on the server via BBedit, then it shows it has Unix > (LF) line endings, and western ISO Latin 1 encoding. If I said that > all right. Not sure what to make of that, nor how to change it (if > I need to).>> Can anyone help me troubleshoot this?>> Thanks> -Govinda> ---------------------------------------------------------> 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/ Associated Messages, from the most recent to the oldest:

Re: [WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file? (Govinda 2009)
Re: [WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file? (Stuart Tremain 2009)
Re: [WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file? (Govinda 2009)
Re: [WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file? (Stuart Tremain 2009)
[WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file? (Govinda 2009)

There was a bug in Return Raw, you may want to check. Not sure which version or if it affected all platforms. I know the bug was in v5.x on WindowsRegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 28/03/2009, at 8:20 AM, Govinda wrote:> Hi all>> Despite 10+ years of successful HTML,WebDNA, (and other related > languages) I've only just now been doing my reading about HTTP > status codes, etc.>> Anyway I have a page from a new clients' inherited site that has an > include that uses [returnraw] in order to set a cookie and then > redirect.., and when I inspect the html source sent back I see that > there is nothing coming back at all from the include, and there is > also none of the HTML below that include in the original file > either. So somewhere it is choking on the included file. This file > was working fine on the previous Mac os x 10.2.8 server, wc 5.1c, > Webstar V host. (Now I am trying to get this to work on RedHat 4 64 > bit. ) To troubleshoot, I have commented out the entire contents > of the include and just started with this (uncommented) test:>> -----------------------start source code------------> [returnraw]HTTP/1.0 200 OK> Status: 200> Content-type: text/html>> >> [/ReturnRaw]> [!]> my previously-working code here commented out.> [/!]> -----------------------end source code------------>> I also tried this:>> -----------------------start source code------------> [returnraw]HTTP/1.0 302 Found>> Location: http://www.google.com/[!]---[Lookup db=../ > preferences > .db&lookinfield=PrefName&value=PrimaryDomain&returnfield=PrefValue]/ > admin---[/!]>>> [/ReturnRaw]> [!]> my previously-working code here commented out.> [/!]> -----------------------end source code------------>> But I am getting the same behavior. (Nothing is coming back from > the include, nor even any of the code in the file that includes this > include *after* the [include ..] tag.) I.e. it is dying somewhere > while trying to parse the include. (When I view source from the > browser then all I see is the html that the including file spits out > before we get to the include.)>> On my new imac I see in BBedit that the local copy of the file does > indeed have windows CRLF set for the line endings. and encoding is > set to 'western MacOS Roman'. But after I upload and then open that > file directly on the server via BBedit, then it shows it has Unix > (LF) line endings, and western ISO Latin 1 encoding. If I said that > all right. Not sure what to make of that, nor how to change it (if > I need to).>> Can anyone help me troubleshoot this?>> Thanks> -Govinda> ---------------------------------------------------------> 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/ Stuart Tremain

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] help with [ReturnRaw] - why is it killing the parse of the [include] file?

2009

Top Articles:

Related Readings: