Re: 500 internal error?

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 58446
interpreted = N
texte = I'd call webstar, it is most likely a server problem, not webdna. =20 according to this copy and pasted thing below(found on web) it could be anything Your Web server encountered an unexpected condition that prevented it=20= from fulfilling the request by the client (e.g. your Web browser or our=20= CheckUpDown robot) for access to the requested URL. This is a 'catch-all' error generated by your Web server. Basically=20 something has gone wrong, but the server can not be more specific =20 about the error condition in its response to the client. In addition to=20= the 500 error notified back to the client, the Web server should=20 generate some kind of internal error log which gives more details of=20 what went wrong. It is up to the operators of your Web server site to=20 locate and analyse these logs. 500 errors in the HTTP cycle Any client (e.g. your Web browser or our CheckUpDown robot) goes =20 through the following cycle when it communicates with your Web server: =95 Obtain an IP address from the IP name of your site (your = site URL=20 without the leading 'http://'). This lookup (conversion of IP name to=20 IP address) is provided by domain name servers (DNSs). =95  Open an IP socket connection to that IP address. =95  Write an HTTP data stream through that socket. =95  Receive an HTTP data stream back from your Web server = in =20 response. This data stream contains status codes whose values are=20 determined by the HTTP protocol. Parse this data stream for status=20 codes and other useful information. This error occurs in the final step above when the client receives an=20= HTTP status code that it recognises as '500'. On Jun 16, 2004, at 12:24 PM, Phil Herring wrote: > I'm running WebStar 5.x and webdna 4.5 on Mac OS 10.2 ... > > I've got one user who is getting a 500 internal server error. I've=20 > only > seen this from Apache/Perl/php installations, and this server has=20 > absolutely > none of that. > > Anyone with a similar setup ever run across a 500 error, and if so,=20 > what > caused it? > > > > ------------------------------------------------------------- > 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=20 > > 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: 500 internal error? ( Dylan Wood 2004)
  2. Re: 500 internal error? ( Tom Brent 2004)
  3. 500 internal error? ( Phil Herring 2004)
I'd call webstar, it is most likely a server problem, not webdna. =20 according to this copy and pasted thing below(found on web) it could be anything Your Web server encountered an unexpected condition that prevented it=20= from fulfilling the request by the client (e.g. your Web browser or our=20= CheckUpDown robot) for access to the requested URL. This is a 'catch-all' error generated by your Web server. Basically=20 something has gone wrong, but the server can not be more specific =20 about the error condition in its response to the client. In addition to=20= the 500 error notified back to the client, the Web server should=20 generate some kind of internal error log which gives more details of=20 what went wrong. It is up to the operators of your Web server site to=20 locate and analyse these logs. 500 errors in the HTTP cycle Any client (e.g. your Web browser or our CheckUpDown robot) goes =20 through the following cycle when it communicates with your Web server: =95 Obtain an IP address from the IP name of your site (your = site URL=20 without the leading 'http://'). This lookup (conversion of IP name to=20 IP address) is provided by domain name servers (DNSs). =95  Open an IP socket connection to that IP address. =95  Write an HTTP data stream through that socket. =95  Receive an HTTP data stream back from your Web server = in =20 response. This data stream contains status codes whose values are=20 determined by the HTTP protocol. Parse this data stream for status=20 codes and other useful information. This error occurs in the final step above when the client receives an=20= HTTP status code that it recognises as '500'. On Jun 16, 2004, at 12:24 PM, Phil Herring wrote: > I'm running WebStar 5.x and webdna 4.5 on Mac OS 10.2 ... > > I've got one user who is getting a 500 internal server error. I've=20 > only > seen this from Apache/Perl/php installations, and this server has=20 > absolutely > none of that. > > Anyone with a similar setup ever run across a 500 error, and if so,=20 > what > caused it? > > > > ------------------------------------------------------------- > 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=20 > > 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/ Dylan Wood

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.0 [format thousands .0f] no go (1997) Bug Report, maybe (1997) 2.01 upgrade problems (1997) BBEdit and WebCatalog 2.0? (1997) Unceremonious Unwanted Unsubscription (1999) Purchase Plugin Missing (1996) Adding Header Values with [SetHeader] (1998) OT: Collaborative Browsing (2000) [lookup] vs. [search] (1998) Math (1997) case=T and [showif] (2002) Potential Conflicts? (1997) PIXO Support (1997) webmerch and serials - almost there (1997) [OT] Disable/enable field (2003) .. more on sliding discounts... (1997) RE: Template not found error messages (1997) More on the email templates (1997) forming a SKU (1999) OT: Site Test (2006)