On 8 Jun 2013, at 10:40, Peter Gutbrod wrote: > Is it really necessary to discriminate between all these status codes for > your production site
Just to clarify, we are programmers. We don't worry about this type of stuff too much. On the other hand, our customers operate in highly competitive commercial environments. Have a look at these status codes, they constitute a "language" which the web server uses to communicate with search engines, browsers and other automated site clients...http://httpstatus.es. To our customers, it makes a huge difference to tell a search engine (or a browser for that matter) that the site is malfunctioning when it isn't. The search engine will happily bat your site back to the dark ages in rankings if it gets confusing information. Similarly, browsers use response codes to react appropriately to different types of server conditions. For example, http response codes allow retailers to superceed one product code with another and use a response code to inform the search engine exactly what's happened so that the search engine doesn't treat it as a bad URL and so on. The sites also now supply XML shopping feeds which have to agree with the organically discovered site architecture. Response codes are the meat and potatoes of all this stuff in a competitive environment and it's essential to have them right in every instance. Our customers check their competitors sites who comply appropriately with http protocol and they check their own sites with analysers. They want their own sites to behave optimally in this regard and I think that's only reasonable. Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
