I was reading a discussion on another forum and someone said they once ran a web server off of a router, to which another person replied:
"And no, you did not run a web server on an old router. I don't even know where to begin with this one. Routers have so little RAM the web server would not even be able to run, not to mention the CPUs are not designed for such things to be ran on them, usually they are hardware specific so not only would the code not even run but you would never get it to run.
Web servers use a LOT of RAM, and old routers have no more than 8-16MB of RAM, only newer ones have any more than that (and it's usually no more than 46MB or so). The web server couldn't even initiate with so little.
Not to mention the clock speed, older routers run anywhere from 20MHz to 70MHz. Only newer ones run higher, but even then only between 100MHz and 200MHz."
After some back and forth bickering, it was said (in reply to the quoted bit):
"So you're basically saying that if someone hosts a website on a small VPS using a web server software, and it only serves a few pages/handles a few hundred to a few thousand requests over a week or so, that it's not a web server?"
No, because they are using web server software, not displaying a .html document via http access.
Web server:
Client > website/IP > web server software > web pages
Not a web server:
Client > website/IP > publicly accessible .html file that displays a web page with links
You can host a website without server software.
IMO, if a piece of software listens for a network connection and responds to properly formatted requests and sends back HTML data, it's a web server. The web configuration ability inherent in most routers I would call a built in "web server". Sure, it's not a web server that you can put your own content on (unless you edit the firmware), but the firmware does contain a filesystem with pages that are served and the router runs code to handle the requests. I don't see how that functionality doesn't count as a web server.
...or am I off base and not understanding something?
"And no, you did not run a web server on an old router. I don't even know where to begin with this one. Routers have so little RAM the web server would not even be able to run, not to mention the CPUs are not designed for such things to be ran on them, usually they are hardware specific so not only would the code not even run but you would never get it to run.
Web servers use a LOT of RAM, and old routers have no more than 8-16MB of RAM, only newer ones have any more than that (and it's usually no more than 46MB or so). The web server couldn't even initiate with so little.
Not to mention the clock speed, older routers run anywhere from 20MHz to 70MHz. Only newer ones run higher, but even then only between 100MHz and 200MHz."
After some back and forth bickering, it was said (in reply to the quoted bit):
"So you're basically saying that if someone hosts a website on a small VPS using a web server software, and it only serves a few pages/handles a few hundred to a few thousand requests over a week or so, that it's not a web server?"
No, because they are using web server software, not displaying a .html document via http access.
Web server:
Client > website/IP > web server software > web pages
Not a web server:
Client > website/IP > publicly accessible .html file that displays a web page with links
You can host a website without server software.
IMO, if a piece of software listens for a network connection and responds to properly formatted requests and sends back HTML data, it's a web server. The web configuration ability inherent in most routers I would call a built in "web server". Sure, it's not a web server that you can put your own content on (unless you edit the firmware), but the firmware does contain a filesystem with pages that are served and the router runs code to handle the requests. I don't see how that functionality doesn't count as a web server.
...or am I off base and not understanding something?