The Linux Administration group is for the discussion of technical issues technical issues that arise during the administration of Linux systems, including maintaining the operating system and supporting end-user applications.

I heard Apache is slow in Surfing on Directories ! But Ngix doesn't ! Or conversely i don't know !!!

Vanilla Apache httpd is slower than Ngix out of the box by many metrics. It is also less secure. However, it is my understanding that Apache will scale and outperform Ngix with the proper setup. Also, keep in mind, Apache is an entire range of products so you can't just focus on the httpd server. http://projects.apache.org/indexes/category.html

@mansouripeyman

Are YTS and GWS developed by their owner companies from beginning?

It's hard to say with google. Since google is not forthcoming on GWS, without inside knowledge, it would be speculation to answer.

YTS was originally Inktomi Traffic Server. Inktomi was purchased by Yahoo so the original development was not by Yahoo. It continues to be developed by Yahoo and is part of the Apache line.

When discussing web servers for linux, security is about misconfiguration. Apache, nginx and lighttpd are mature enough products that the only real risk is if you do not configure them according to the products best practices.

Zeus was considered one of the most secure web servers out there. It is not cheap either. The project looks dead however since the last version is 2010.

With all of that in mind, the metric I use is vulnerability discovery to patch release time. With Apache it is usually just a few hours. No one else offers that level of security patching that I'm aware of.

- In your Mozilla Firefox, click '*Tools*' menu, click '*Add-ons*' option.
- In 'Search all add-ons' box in top right hand side, type Server Spy
- Once you find this add-on, click the 'Install' button next to it, this
will download and install the plug-in.
- Now restart the browser and access any website. You would see a orange
color round shape icon next to website address in address bar.
- Read below to know the letter mentioned under orange color round icon
means, you can find web server information by clicking this icon.

If the icon letter is '*I*' then it is IIS Web server.
If the icon letter is '*A*' then it is Apache Web server.
If the icon letter is '*G*' then it is Google Web server.
If the icon letter is '*?*' then web server name is unknown.

I am not an expert on any Webserver, but I am a long time IT veteran, and I've been around longer that the Web. The Apache Web server, while perhaps not the very first Web server ever, was one of the early Web servers that was widely deployed, and it has undergone numerous enhancements, security changes, module additions, and so forth.

What may have started as a relatively straight forward Web server has become a very complex Web server indeed. So it would not surprise me at all if, for certain isolated cases, that you could achieve a much smaller footprint, and possibly a faster Web server solution using something else.

When it comes to scale, flexibility, features, and overall performance, if you invest the time and research into Apache, I am certain that you can achieve a very well performing Web server that can accomplish just about anything you want it to do. It may still be possible to outperform it by installing some other Web server that is specifically engineered for a specific particular purpose. but if you want a good, solid, reliable Web server that is likely understood by a fairly broad audience - and CAN be tuned to perform well, I'd still recommend Apache, or at least something that has descended out of an Apache lineage.

What I have explained are generalities; you can find a variety of opinions on the subject; as a researcher, but not necessarily a Webserver expert, what I've shared are opinions based on research that I've compiled over many years of reading and observation.

Apache is very good. It has gotten to be somewhat bloated - mainly because it's normally delivered with almost all "modules" (think "plugins") loaded and enabled in the config file. Our standard practice is to comment out all modules, and then only enable those absolutely critical to functioning - much smaller footprint, and dramatically tighter security (especially with anything to do with WebDAV - great way to expose your server to attacks).