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 = 102287
interpreted = N
texte = Govinda Sorry, I was not correct on that This is what I was thinking of: 2003/09/01 "The BinaryBody problem on Windows server has been fixed with the WebDNA 5.1 patch. It now works as documented, this problem was not apparent on *nix versions :)" There is a bit of chat about RETURNRAW in the OLD archives Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 28/03/2009, at 10:57 AM, Govinda wrote: > Thanks Stuart. > What were the symptoms of the bug? > When you say check, do you mean search the archives? Do you > remember a rough date range when this might have been talked about > on the list? > If not on the list, where else might I find something to help me > solve this? > Thanks again > -G > > On Mar 27, 2009, at 5:38 PM, Stuart Tremain wrote: > >> 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 Windows >> >> Regards >> >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >> >> On 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/ >> >> --------------------------------------------------------- >> 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/ > > --------------------------------------------------------- > 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:
Govinda Sorry, I was not correct on that This is what I was thinking of: 2003/09/01 "The BinaryBody problem on Windows server has been fixed with the WebDNA 5.1 patch. It now works as documented, this problem was not apparent on *nix versions :)" There is a bit of chat about RETURNRAW in the OLD archives Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 28/03/2009, at 10:57 AM, Govinda wrote: > Thanks Stuart. > What were the symptoms of the bug? > When you say check, do you mean search the archives? Do you > remember a rough date range when this might have been talked about > on the list? > If not on the list, where else might I find something to help me > solve this? > Thanks again > -G > > On Mar 27, 2009, at 5:38 PM, Stuart Tremain wrote: > >> 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 Windows >> >> Regards >> >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >> >> On 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/ >> >> --------------------------------------------------------- >> 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/ > > --------------------------------------------------------- > 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!
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:
NT - Thanks and Taxes (1997)
Sorting nested search (2003)
Emailer Q (2002)
PCS Frames (1997)
Replace/Commit not Replacing/Commiting (2000)
ssl and invoic.tpl and back bttn (2002)
WebCat2.0 [format thousands .0f] no go (1997)
Banners (1997)
emailer and bad addresses (1997)
Database changes (1998)
[OT] Connect to MySQL (Solved) (2004)
OSX Install error (2000)
Draft Manual, Tutorial, and more (1997)
WebCat for mass emailings (1997)
Questions To Answer (1997)
Help ..... with better explanation (2001)
Reversed words (1997)
tricky embedded[showifs/hideifs] (w/ code.. long) (2000)
# of real domains on 1 web server (1997)
date search not working when type=date specified (2007)