I've already realized something, looks like someone/something (I imagine a firewall I'm not an expert on networks), is preventing requests made with a hidden input field with *cmd* as a name (as the field with the value equal to *login* in the login form), I've created another form with that input hidden and the same name and the same problem is happening, but when I change the name instead of *cmd* it works fine, how can I make this to work?. you can test it here: http://isc.unsaac.edu.pe/cuscontest/public/test.php you can (in chrome) press F12 key to inspect document and change the name of the hidden input field to whatever not being *cmd *and it will post fine, but if you left *cmd *it won't do post. hope you can give me some suggestions, maybe contact the network administrator (I think they are very strong headed), in that case I should replace all occurences with the name *cmd *in project files?. Cheers, Dennis
On Tue, Dec 8, 2015 at 12:18 PM, Dennis Huillca Portilla < dennisbot@gmail.com> wrote:
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 http://about.me/dennisbot