Re: port 16080 problem

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 52657
interpreted = N
texte = In my experience I have found that OSX, by default, uses port 16080 as opposed to port 80. This can be a huge pain especially when admin's will configure their firewalls to block that upper port, web surfers can't see your site! Go into Server Settings -> Internet -> Sites then change the port on the individual sites. You'll should find that WebDNA won't throw that error. Dennis Ott Smith Micro Software ----- Original Message ----- From: "Dave Hurley" To: "WebDNA Talk" Sent: Thursday, September 04, 2003 10:28 AM Subject: port 16080 problem > If I click on a link to my OS X/Apache 1.x/WebDNA v.5.1 server that > doesn't have a trailing slash, it appends port 16080 to the domain name > and webDNA throws an error that it isn't configured to serve from that > domain. Apparently this is also happening from some browsers that some > clients are using, even when clicking on a link that does have a > trailing slash. Is there a way I can configure Apache (I assume this is > the best place to change this behavior) to not do this? > > Thanks a heap. > > Dave Hurley > Department of Biology > University of Washington > > > ------------------------------------------------------------- > 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: port 16080 problem ( Paul Willis 2003)
  2. Re: port 16080 problem ( Dave Hurley 2003)
  3. Re: port 16080 problem ( 2003)
  4. port 16080 problem ( Dave Hurley 2003)
In my experience I have found that OSX, by default, uses port 16080 as opposed to port 80. This can be a huge pain especially when admin's will configure their firewalls to block that upper port, web surfers can't see your site! Go into Server Settings -> Internet -> Sites then change the port on the individual sites. You'll should find that WebDNA won't throw that error. Dennis Ott Smith Micro Software ----- Original Message ----- From: "Dave Hurley" To: "WebDNA Talk" Sent: Thursday, September 04, 2003 10:28 AM Subject: port 16080 problem > If I click on a link to my OS X/Apache 1.x/WebDNA v.5.1 server that > doesn't have a trailing slash, it appends port 16080 to the domain name > and webDNA throws an error that it isn't configured to serve from that > domain. Apparently this is also happening from some browsers that some > clients are using, even when clicking on a link that does have a > trailing slash. Is there a way I can configure Apache (I assume this is > the best place to change this behavior) to not do this? > > Thanks a heap. > > Dave Hurley > Department of Biology > University of Washington > > > ------------------------------------------------------------- > 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/

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:

Pithy questions on webcommerce & siteedit (1997) Ongoing group search problems ... (1997) Email Formatting and Encryption (1998) Bug? (1997) Running 2 two WebCatalog.acgi's (1996) PCS Frames (1997) [movefile] create stationery files (1998) Limit on nested [ShowIf]'s? (1997) can WC render sites out? (1997) New command suggestion (1997) Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997) Timer Values on [redirect] (1998) Is it IE6 hating rediercts? (2004) Google Web Accelerator (2005) New WebCatalog Version !!! (1997) [shownext] and descending order (1997) [OT] Authorizenet Costs (2005) WebCatalog2 Feature Feedback (1996) cc auth with [purchase] (1998) [WebDNA] v7 Stress Test and Strange Behaviour (2012)