Re: [WebDNA] How to code a 301 redirect

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 100367
interpreted = N
texte = --Apple-Mail-1--17652661 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit > I don't think WebDNA ever was intended to manipulate/control the > basic server software at such a deep level. It actually was designed to manipulate the output stream at that low level, but with great power comes great responsibility ;) The most common source of problems when writing HTTP headers is forgetting that the HTTP spec requires cr/lf, not just cr for linebreaks. If you're going to write your own headers, then you must conform to the spec. Browsers will just ignore it otherwise. [!] [/!][!] ------------------------------------ ### 301 Redirect ### [/!][returnraw]HTTP/1.1 301 Moved Permanently Location: http://revolutionaries.ie [!] --Apple-Mail-1--17652661 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
I = don't think WebDNA ever was intended to manipulate/control the basic = server software at such a deep level.

It = actually was designed to manipulate the output stream at that low level, = but with great power comes great responsibility = ;)

The most common source of problems when = writing HTTP headers is forgetting that the HTTP spec requires cr/lf, = not just cr for linebreaks.  If you're going to write your own = headers, then you must conform to the spec. Browsers will just ignore it = otherwise.

[!]<!-- HAS_WEBDNA_TAGS -->
[/!][!]


------------------------------------
###  301 Redirect =  ###

[/!][returnraw]HTTP/1.1 301 Moved = Permanently
<cr><lf>
<cr><lf>[!]

= --Apple-Mail-1--17652661-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [BULK] Re: [WebDNA] How to code a 301 redirect (Donovan Brooke 2009)
  2. Re: [BULK] Re: [WebDNA] How to code a 301 redirect (Donovan 2009)
  3. [BULK] Re: [WebDNA] How to code a 301 redirect (Clint Davis 2009)
  4. [BULK] Re: [WebDNA] How to code a 301 redirect (Clint Davis 2009)
  5. Re: [WebDNA] How to code a 301 redirect (=?ISO-8859-1?Q?Claude_G=E9linas?= 2008)
  6. Re: [WebDNA] How to code a 301 redirect (Chris 2008)
  7. RE: [WebDNA] How to code a 301 redirect ("Sue Blesch" 2008)
  8. Re: [WebDNA] How to code a 301 redirect (Donovan Brooke 2008)
  9. Re: [WebDNA] How to code a 301 redirect (Gary Krockover 2008)
  10. Re: [WebDNA] How to code a 301 redirect (Bob Minor 2008)
  11. Re: [WebDNA] How to code a 301 redirect ("Dan Strong" 2008)
  12. Re: [WebDNA] How to code a 301 redirect ("Tom Duke" 2008)
  13. Re: [WebDNA] How to code a 301 redirect (Grant Hulbert 2008)
  14. Re: [WebDNA] How to code a 301 redirect (Gary Krockover 2008)
  15. Re: [WebDNA] How to code a 301 redirect ("Dan Strong" 2008)
  16. Re: [WebDNA] How to code a 301 redirect ("Tom Duke" 2008)
  17. Re: [WebDNA] How to code a 301 redirect ("Dan Strong" 2008)
  18. Re: [WebDNA] How to code a 301 redirect (Bob Minor 2008)
  19. Re: [WebDNA] How to code a 301 redirect ("Dan Strong" 2008)
  20. Re: [WebDNA] How to code a 301 redirect (Frank Nordberg 2008)
  21. Re: [WebDNA] How to code a 301 redirect ("Tom Duke" 2008)
  22. Re: [WebDNA] How to code a 301 redirect ("Dan Strong" 2008)
  23. Re: [WebDNA] How to code a 301 redirect ("Tom Duke" 2008)
  24. Re: [WebDNA] How to code a 301 redirect ("Dan Strong" 2008)
  25. [WebDNA] How to code a 301 redirect ("Tom Duke" 2008)
--Apple-Mail-1--17652661 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit > I don't think WebDNA ever was intended to manipulate/control the > basic server software at such a deep level. It actually was designed to manipulate the output stream at that low level, but with great power comes great responsibility ;) The most common source of problems when writing HTTP headers is forgetting that the HTTP spec requires cr/lf, not just cr for linebreaks. If you're going to write your own headers, then you must conform to the spec. Browsers will just ignore it otherwise. [!] [/!][!] ------------------------------------ ### 301 Redirect ### [/!][returnraw]HTTP/1.1 301 Moved Permanently Location: http://revolutionaries.ie [!] --Apple-Mail-1--17652661 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
I = don't think WebDNA ever was intended to manipulate/control the basic = server software at such a deep level.

It = actually was designed to manipulate the output stream at that low level, = but with great power comes great responsibility = ;)

The most common source of problems when = writing HTTP headers is forgetting that the HTTP spec requires cr/lf, = not just cr for linebreaks.  If you're going to write your own = headers, then you must conform to the spec. Browsers will just ignore it = otherwise.

[!]<!-- HAS_WEBDNA_TAGS -->
[/!][!]


------------------------------------
###  301 Redirect =  ###

[/!][returnraw]HTTP/1.1 301 Moved = Permanently
<cr><lf>
<cr><lf>[!]

= --Apple-Mail-1--17652661-- Grant Hulbert

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:

WebCat2 - Getting to the browser's username/password data (1997) New Command prefs ... (1997) Integration? (1999) [OT] RSS Feeds (2007) Credit back woes (2000) Date/Sort/Read Date Format? (1999) WebCatalog for guestbook ? (1997) japanese characters (1997) Hideif on IP range (2004) any suggestions for creating a multi-lingual site? (1999) Make sure I understand this??? (1997) Secure server question (1997) NT version (1997) Showif, Hideif reverse logic ? (1997) ErrorMessage.db and redirect URL (1998) It's working (1997) Locking up with WebCatalog... (1997) [searchString] (1997) SSL and Webcat (2000) WCS Newbie question (1997)