Debugging and troubleshooting problems in a production environment is always a tricky endeavour. You usually do not have the luxuries of having a debugger that allows you to step through your code and inspect you variables and stack trace. Some of the areas you might look at include the Event Viewer, to look for any error events or the application log files, to analyse any caught exceptions. If the application is crashing and there’s nothing obvious available in the logs, your best bet is to perform post-mortem analysis with DebugDiag/AdPlus and Windbg.
Some websites use security through obscurity as their main means of protection. This methodology relies on making the vulnerabilities hard to obtain by not making the system’s design known to the general public. As anyone knows, a secret is never a secret for very long. This is bad practice and careless. Concealing a vulnerability will only delay an attacker and not pass any form of security testing. The right approach is to have security as part of the design process of a system.
A global website needs to have relevant content for their multi-cultural, sometimes worldwide, audience. This content needs to be provided to a visitor as quickly as possible to engage them in a great experience. One solution is to deploy and mirror your application to several datacentres across the world. A much more cost effective solution is to use a CDN (Content Delivery Network) to serve your content from a geographical location close to your visitor.
EPiserver uses WCF to send and receive events between servers configured in a multi-server setup (load-balanced or enterprise). A site in a server will send events (publisher) to one or many sites in other servers (subscriber). This is an example of an enterprise setup, with one publishing server and two public facing web servers. To enable remote events (events between EPiServer sites), the following has to be enabled in your episerver.
In a production environment access between various servers is usually restricted to what is the minimum required for the solution to operate. In an enterprise scenario it is common to find a setup where you have multiple load-balanced servers for public users and a separate publishing environment for web editors. These environments usually follow a “deny all” approach where all access has to be explicitly permitted. EPiServer by default uses UDP multicast to transmit event messages (e.
