33 marcus - Does this relate in any way to problems you report in this thread in our Apache forum?
Or is a separate issue?
No, I resolved that problem. This is a separate issue. Thanks
|with random urls ending like; |
OK, obvious question first:
What happens if you request an URL in this form? That's really a two-part question: What does a human see, AND what happens behind the scenes in the way of redirects or rewrites?
Those literal brackets make me uneasy. So does the absence of an initial ? before you start in on the & But it still shouldn't lead to anything more serious than a 404 ("sorry, couldn't find this page"). A 500-class error means "the server doesn't want to see a request in this form ever again".
|A 500-class error means "the server doesn't want to see a request in this form ever again". |
actually a 500 status code response simply means the server process failed to provide an expected response.
it doesn't necessarily imply anything about the request.
this may simply mean your script failed before a status code or any headers were provided in the response.
|500 Internal Server Error |
The server encountered an unexpected condition which prevented it from fulfilling the request.
Picky, picky :-P Sure, it's not a 400 ("The client SHOULD NOT repeat the request without modifications"). But if certain requests always result in an error, then there's a problem with the request. Or, of course, with your server's response to the request-- but the client doesn't know that :)
Hi lucy24, there are no redirects or rewrites & when I go to the urls I get;
"Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, firstname.lastname@example.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."
whenever there is a 500 Internal Server Error there is almost certainly a relevant entry in the server error log.
request the problem url, note the time, and go look in the error log for clues.
also, if there is a 500 Internal Server Error error encountered while trying to serve an ErrorDocument, it probably means you are using a script for an error document.
i would recommend using a static (.html) error document unless you really need a script.
you should also see the error log entry thrown by the ErrorDocument problem, so don't confuse these problems since they may have the same time stamp.