In ASP.NET applications, specifically in ASP.NET Web Forms and ASP.NET MVC (pre-Core), the compilation process is dynamic and happens at runtime if source files like .cshtml, .aspx, and .cs files are present on the server.
ASP.NET uses just-in-time (JIT) compilation for views (.cshtml, .aspx, .ascx, etc.) and sometimes for code-behind files (.cs).
When a request hits a page, ASP.NET dynamically compiles these files into temporary assemblies.
If there’s a syntax error, missing semicolon, incorrect type, or any other compilation issue, the process will fail and throw a 500 error.
even if you have like a student learning platform so they don't have to install anything, surely it would wrap the code that's submitted so it doesn't crash the application
If the file failed to compile the server wouldn't execute it because a file wouldn't be created. A compile error stops the process, It doesn't result in a corrupted output, since that would be really stupid.
For the same reason our OS memory management class was in Java, a language without pointers, because some idiot decided all courses had to be standardized on the same language because the industry says they need people who know that language now.
this is not always true. many tutorials encourage people to do a setup that does not output a PHP error to the web, as it can leak info that may help an attacker, such as the file path the error occurred in. in setups like these PHP will log the error to a file an attacker can't access (often /var/log/php/error.log ) and exit with a failure status code, which many common web server setups will turn into an HTTP 500 error. Some server setups will just send an empty file though, which will be a blank white page shown in a browser.
Any programming language that runs on the web server and doesn't gracefully handle its errors. There are many web servers implemented in Javascript, but it could also be Java, it could be Perl, it could even be C/C++ if someone is being masochistic.
Javascript also exists on the server, and an exception would cause a 500 error. Semicolons are optional in JavaScript, except for a handful of cases. One of those is in a for loop. I'm guessing the professor was running a nodejs app and did something like this (intentionally bad style because professor):
for (x = 0; x < 5 x++)
{}
return x
Boom, syntax error, which would return a 500 air status in a nodejs web server framework.
how tf would a missing semicolon result in a http server error
In ASP.NET applications, specifically in ASP.NET Web Forms and ASP.NET MVC (pre-Core), the compilation process is dynamic and happens at runtime if source files like .cshtml, .aspx, and .cs files are present on the server.
ASP.NET uses just-in-time (JIT) compilation for views (.cshtml, .aspx, .ascx, etc.) and sometimes for code-behind files (.cs). When a request hits a page, ASP.NET dynamically compiles these files into temporary assemblies.
If there’s a syntax error, missing semicolon, incorrect type, or any other compilation issue, the process will fail and throw a 500 error.
why would you use asp in an introductory course
even if you have like a student learning platform so they don't have to install anything, surely it would wrap the code that's submitted so it doesn't crash the application
my guess is he had all the boilerplate written, and was using a single line or two of "working code" to show what the technology was capable of
but it's 4chan greentext so it could be fake and gay
Yeah, what he said.
File fails to compile, web server tries to run the file, error.
Nodejs exists. Here's a JS snippet that would throw an exception:
if your server runs user-submitted code server side, that's a paddlin
It never said user code.
This could as well be an intro to php and the server may be set to not show errors and instead just fail.
The lecturer then writes some code, forgets a semicolon and gets a 500.
If the file failed to compile the server wouldn't execute it because a file wouldn't be created. A compile error stops the process, It doesn't result in a corrupted output, since that would be really stupid.
You must have never used the eclipse Java compiler.
If the web server is implemented in any of the languages that require semicolons.
why would you demo a for loop with a web server
For the same reason our OS memory management class was in Java, a language without pointers, because some idiot decided all courses had to be standardized on the same language because the industry says they need people who know that language now.
As one step of building a bigger project that demonstrates something web-ish.
What programming language returns a 500 error because it fails?
A 500 error code is a critical server failure, It isn't something that can happen because a piece of JavaScript failed.
Maybe PHP? Since it runs as a server and returns computed results in a browser... Though I'm pretty sure it'd just return the compiler error text
Php outputs HTML at the end of the process. If it didn't run because of a missing semicolon it would just output an error. It wouldn't crash
this is not always true. many tutorials encourage people to do a setup that does not output a PHP error to the web, as it can leak info that may help an attacker, such as the file path the error occurred in. in setups like these PHP will log the error to a file an attacker can't access (often /var/log/php/error.log ) and exit with a failure status code, which many common web server setups will turn into an HTTP 500 error. Some server setups will just send an empty file though, which will be a blank white page shown in a browser.
Any programming language that runs on the web server and doesn't gracefully handle its errors. There are many web servers implemented in Javascript, but it could also be Java, it could be Perl, it could even be C/C++ if someone is being masochistic.
Couldn't be a compiled language, those wouldn't even get to the point where you send a request.
Javascript also exists on the server, and an exception would cause a 500 error. Semicolons are optional in JavaScript, except for a handful of cases. One of those is in a for loop. I'm guessing the professor was running a nodejs app and did something like this (intentionally bad style because professor):
Boom, syntax error, which would return a 500 air status in a nodejs web server framework.
Old IIS versions with PHP would do this when running in production mode. Talking about 2010-2012
IIS. That brought back bad memories.
Intro to IT on some webform stuff is truly the darkest timeline.
Where have the good old times gone when peeps were tortured with plain C in some atrocious outdated IDE from the ancient times?!
Ugh, I don't want to touch codeblocks again