Web Server is designed to serve HTTP Content. Application Server can also serve HTTP Content but is not limited to just HTTP.
It can be provided other protocol support such as RMI/RPC
Web Server is mostly designed to serve static content, though most Web Servers have plugins to support scripting languages
like Perl, PHP, ASP, JSP etc. through which these servers can generate dynamic HTTP content.
Most of the application servers have Web Server as integral part of them, that means App Server can do whatever Web Server
is capable of. Additionally Application Server have components and features to support Application level services such as Connection Pooling,
Object Pooling, Transaction Support, Messaging services etc.
As web servers are well suited for static content and app servers for dynamic content, most of the production environments have
web server acting as reverse proxy to app server. That means while service a page request, static contents such as images/Static html is served
by web server that interprets the request. Using some kind of filtering technique (mostly extension of requested resource) web server identifies
dynamic content request and transparently forwards to app server
Example of such configuration is Apache HTTP Server and BEA WebLogic Server. Apache HTTP Server is Web Server and BEA WebLogic is