I did it, and the post request never reach the server again, maybe it's the firewall but I have another form with post request that works (http://isc.unsaac.edu.pe/academico/login), that's a strange thing, could firewalls block specific segments of my domain?, I've changed the name from mydomain.com/domjudge to mydomain.com/cuscontest but it stills doesn't work, any suggestions I would appreciate.

Cheers,

Dennis

On Tue, Dec 8, 2015 at 2:08 AM, Thijs Kinkhorst <thijs@kinkhorst.com> wrote:

On Tue, December 8, 2015 07:39, Dennis Huillca Portilla wrote:
> Sorry, I've stopped the apache server for a while, but I'm not getting
> incorrect password, it keeps loading till I get this message at google
> chrome:
> this web page is not available
> ERR_CONNECTION_RESET
> like if it were trying to connect to some place (it takes about 30 seconds
> before I get that error message on the browser)

It's strange that it only happens in an interactive browser and not with
cURL. I really have no idea what could cause this but I doubt that it's
something in DOMjudge since DOMjudge really doesn't care whether you use
cURL or something else. Perhaps it helps to find the cause though to debug
it a bit by adding output statements in the DOMjudge code to find out at
what point it's hanging specifically.

And just a wild guess: there's not some 'smart/'next-generation'
firewalling equipment active that messes with the requests?

Cheers,
Thijs

Best Regards.
Dennis Huillca Portilla