Re: Search Engine questions ...
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 44820
interpreted = N
texte = >>If you use the MIMEHeaders.inc file I have posted below, your pages >>will be cacheable and will be likely to be spidered. > >John, >Yes, and I've used them on WC stuff since you first posted them long >ago. Thanks. > >I also have a site with 100% static pages. Pure flat html. They >include only this for MIME stuff: > >[SETMIMEHEADER name=Pragma&value=no-cache] >[SETMIMEHEADER name=Expires&value=Sun, 31 Dec 2000 00:00:00 GMT] >[SETMIMEHEADER name=Cache-Control&value=max-age=0 I think you're using the wrong terminology here ...To me, the only truly 100% static pages are pages which webdna has nothing to do with. In other words, they have a file suffix which is NOT processed by webdna on the server, and they are not processed by any other CGI or plugin either.But you're serving your pages via webdna, so that means they *are* dynamic pages -- even if there's no webdna code in them. (Actually you have webdna code in them, it's just that your code does not change the HTML -- but it definitely changes the mime headers)Here's the key fact to remember:Whenever webdna uses a template as its basis for creating an on-the-fly page, webdna has created a DYNAMIC page. In this situation, webdna is *also* responsible for creating and sending the mime headers to the server, and then it is the server's responsibility to serve those mime headers to the browser, along with the dynamically-generated HTML.But webdna's mime headers are not the same as the mime headers created by the server when it serves a truly static web page. The search engines can easily observe the difference in these two types of mime headers -- and they can choose to follow or ignore the dynamically-generated mime headers such as the ones created by webdna.This is probably why John Peacock suggested that you use his mime header code -- because his code mimics the mime headers which the SERVER (and not webdna) will place into every html file it serves directly.Therefore, if you believe that some of the search engines look at the mime headers to determine whether or not the pages should be added to their database (and I believe that some of them do this) then it only makes sense to use John's mime header code. Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>>If you use the MIMEHeaders.inc file I have posted below, your pages >>will be cacheable and will be likely to be spidered. > >John, >Yes, and I've used them on WC stuff since you first posted them long >ago. Thanks. > >I also have a site with 100% static pages. Pure flat html. They >include only this for MIME stuff: > >[SETMIMEHEADER name=Pragma&value=no-cache] >[SETMIMEHEADER name=Expires&value=Sun, 31 Dec 2000 00:00:00 GMT] >[SETMIMEHEADER name=Cache-Control&value=max-age=0 I think you're using the wrong terminology here ...To me, the only truly 100% static pages are pages which webdna has nothing to do with. In other words, they have a file suffix which is NOT processed by webdna on the server, and they are not processed by any other CGI or plugin either.But you're serving your pages via webdna, so that means they *are* dynamic pages -- even if there's no webdna code in them. (Actually you have webdna code in them, it's just that your code does not change the HTML -- but it definitely changes the mime headers)Here's the key fact to remember:Whenever webdna uses a template as its basis for creating an on-the-fly page, webdna has created a DYNAMIC page. In this situation, webdna is *also* responsible for creating and sending the mime headers to the server, and then it is the server's responsibility to serve those mime headers to the browser, along with the dynamically-generated HTML.But webdna's mime headers are not the same as the mime headers created by the server when it serves a truly static web page. The search engines can easily observe the difference in these two types of mime headers -- and they can choose to follow or ignore the dynamically-generated mime headers such as the ones created by webdna.This is probably why John Peacock suggested that you use his mime header code -- because his code mimics the mime headers which the SERVER (and not webdna) will place into every html file it serves directly.Therefore, if you believe that some of the search engines look at the mime headers to determine whether or not the pages should be added to their database (and I believe that some of them do this) then it only makes sense to use John's mime header code. Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Kenneth Grome
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:
WebCat2b15MacPlugin - [protect] (1997)
Ampersands in database fields? (1998)
Bulletin Board (1998)
upgrading (1997)
For those of you not on the WebCatalog Beta... (1997)
using showpage and showcart commands (1996)
No luck with taxes (1997)
username/password dialogue (2001)
Public beta 2 for WebCatalog 4.0 is now available. (2000)
Showif, Hideif reverse logic ? (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Questions To Answer (1997)
[WebDNA] Clean URLS job - will pay (2010)
Generating Options for a Form. (1997)
No luck with taxes (1997)
[Semi-OT] Kinda cool tool (how does it work?) (2004)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
[ShowNext] (2007)
PROBLEM (1997)
So, does anyone have developer editon running on Win XP (2006)