Re: I read the manual

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 28378
interpreted = N
texte = >>>-I took the tearoom folder and copied it into the webstar folder >>>-when I visit my store http://mydomain/tearoom >> >>This URL is not complete, so apparently webstar is trying to serve a >>default page based in webstar's default page settings. You can >>either enter a full URL to the actual default page for the store you >>created, or you can find out what page the web server is trying to >>serve, and remove the [protect] tag from that page ... > >Let's not jump to conclusions here. There are plenty of reasons why >a password dialog would be displayed, not all of which pertain to >[protect]. I agree that it may not be a [protect] tag that's causing the authentication box to be displayed, but that's probably not the primary issue here anyways. The real problem begins with the incomplete URL ...When webstar gets an incomplete URL like the one above, it has to try to *guess at* what page the visitor actually wants. The best solution is therefore to make the visitor use a complete URL instead of a partial URL, thus this was my first suggestion.If he doesn't want to do that, then he has to figure out what page the webstar is trying to serve -- so if the url is not displayed in the browser, he needs to go into the webstar settings and check it from there. Once he knows which page webstar is trying to serve, then he can either:1- make sure there's no [protect] tag in that page -- assuming there's not supposed to be a protect tag in that page -- or ...2- configure webstar to serve the *correct* error page when it gets an incomplete url, or ...3- check webstar realms to make sure there's no realm match preventing the page from being served.================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Associated Messages, from the most recent to the oldest:

    
  1. Re: I read the manual (Kenneth Grome 2000)
  2. Re: I read the manual (WebDNA Support 2000)
  3. Re: I read the manual (Kenneth Grome 2000)
  4. I read the manual (Single Guy 2000)
>>>-I took the tearoom folder and copied it into the webstar folder >>>-when I visit my store http://mydomain/tearoom >> >>This URL is not complete, so apparently webstar is trying to serve a >>default page based in webstar's default page settings. You can >>either enter a full URL to the actual default page for the store you >>created, or you can find out what page the web server is trying to >>serve, and remove the [protect] tag from that page ... > >Let's not jump to conclusions here. There are plenty of reasons why >a password dialog would be displayed, not all of which pertain to >[protect]. I agree that it may not be a [protect] tag that's causing the authentication box to be displayed, but that's probably not the primary issue here anyways. The real problem begins with the incomplete URL ...When webstar gets an incomplete URL like the one above, it has to try to *guess at* what page the visitor actually wants. The best solution is therefore to make the visitor use a complete URL instead of a partial URL, thus this was my first suggestion.If he doesn't want to do that, then he has to figure out what page the webstar is trying to serve -- so if the url is not displayed in the browser, he needs to go into the webstar settings and check it from there. Once he knows which page webstar is trying to serve, then he can either:1- make sure there's no [protect] tag in that page -- assuming there's not supposed to be a protect tag in that page -- or ...2- configure webstar to serve the *correct* error page when it gets an incomplete url, or ...3- check webstar realms to make sure there's no realm match preventing the page from being served.================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 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:

OS X permissions to write to Globals directory (2003) Webmerchant email misinterpreted tags (1998) Authorize.Net down 2 days in row (2004) RE: IIS4b2 and WebCatalog b19 (1997) Details of shipping - Totalqty calculations (1997) Execute Applescript (1997) PIXO Support (1997) Server Freeze (1998) WebCatalog NT beta 18 problem (1997) [OT] UK webcat job vacancy (2003) SOP for WebDNA talk - MSNBot Crashing (2004) pop up menu's (1998) XML Parse with XML WebDNA Syntax... (2004) [WebDNA] NOT serving WebDNA, just running it locally. (2012) Templates for Customer Database? (1997) Accepting credit cards (1997) PCS Frames (1997) E-mailer error codes (1997) WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997) WebCat2.0b15-to many nested [xx] tags (1997)