> I can really exclude an error in the server-side code.
Your code, perhaps, but not the entire server side of the
interaction. "500 Internal Server Error" is a _server-side_ error.
That's not happening in Prototype, or in the browser at all.
Something on the client-side may (or may not) be triggering it, but
it's happening on the server. There should be details about the error
in the server's log -- what went wrong, why, etc. If there aren't,
look at the logging configuration of your server, it really should be
recording the detail of 500s.
Other than finding out from the server why it failed, like Diodeus all
I can suggest is further and more intensive debugging. For instance,
use Firefox+Firebug and look at the requests and responses in
Firebug's Net tab to see whether there's some difference in the
request that fails vs. the ones that don't.
tj / crowder software / com
Independent Software Engineer, consulting services available
On May 6, 5:35 pm, Nobody <stefan.e...@googlemail.com> wrote:
> Hi Diodeus,
> as i wrote, i ran the code several times without errors, but other
> times it crashed.
> I can really exclude an error in the server-side code. I replaced my
> code with a simple Perl one line script "print '123test';" and even
> with this simple code it sometimes worked, sometimes didn't...
> On 6 Mai, 18:29, Diodeus <diod...@gmail.com> wrote:
> > All I can suggest is performing some error-trapping in your server-
> > side code to see where it's crapping-out.
> > On May 5, 2:55 pm, Nobody <stefan.e...@googlemail.com> wrote:
> > > Hi guys,
> > > i got a problem with prototype in connection with a perl script. I'm
> > > performing AJAX-requests with Ajax.Request of prototype calling a perl
> > > script for performing the backend functions.
> > > Somehow i get random "500 Internal Server Error" messages. I tried so
> > > many things (checking permissions, checking error.log, etc.) but i got
> > > no further with this.
> > > The cryptic part is that i can run the AJAX-request several times,
> > > every time succesfully, but if i run it once more, it crashes with the
> > > mentioned error. I can exclude an error within the perl script. I ran
> > > it several times without an AJAX-request just through a normal POST-
> > > call and i never got errors. Even more weird is the fact that the perl
> > > script evidently performs the commands it should perform even if i get
> > > the internal server error.
> > > Anybody got me any idea how to solve this?
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to
For more options, visit this group at