3 ms·
It's quite easy to make this particular *.exe path return an "Internal Error" by fuzzing the GET parameters, which may or may not be due to someone having writt
by avar 11y ago
It's quite easy to make this particular *.exe path return an "Internal Error" by fuzzing the GET parameters, which may or may not be due to someone having written something that parses user-supplied data in C that then segfaults :)
- TeMPOraL 11y agoAssuming that they're even using C. It may as well be a dumped executable Lisp image.
- germanier 11y agoThe company behind that software, HAFAS (which is used almost everywhere in the German-speaking countries) constantly advertises for C++ and Java positions. As far as I'm aware the main part of the software, including the web facing portions, is written in C++. The software has a long history, the first webserver with it was started in 1995 and even that most likely reused logic from their first version of 1989. So the language choice is not too surprising.
- orless 11y agoSmall correction: the company is HaCon (http://www.hacon.de/ http://www.hacon.de/), HaFas is their software.
- Piskvorrr 11y agoWell, what else would you return? A `400 Bad Request` error might be more appropriate, but a `500 Internal Server Error` is "A generic error message, given when an unexpected condition was encountered and no more specific message is suitable." - you don't want to leak internal state, obviously, so just log the problem and respond with a 500. TL;DR: Might be a segfault, but it's 2015 - it probably isn't.