Hot answers tagged

36

Purpose of keepalive.aspx Here's the full code of the page in Sitecore 8.0: <%@Page Language="C#" %> <%@ Import Namespace="Sitecore.Analytics" %> <!DOCTYPE html> <html> <head id="Head1" runat="server" enableviewstate="false"> <title>Keep Alive</title> <script runat="server"> protected override void ...


13

I think your best option (requiring no code or overwrites) would be to configure UrlRewrite to filter out the header. There are already half a dozen reasons why you might have this module installed already on your server - might as well use it. Open up UrlRewrite for your site, and click "View Server Variables". Then add your X-Frame-Options header. Then ...


13

I will recommend these specific settings for Sitecore in IIS: Ensure that Maximum Worker Processes for the Application Pool is set to 1 (under advanced settings) Ensure that Load User Profile settings of the Application Pool is set to "true" (under advanced settings) Ensure anonymous access is denied for: /App_Config /sitecore/admin /sitecore/debug /...


12

Adding to Dmytro's answer - indeed the KeepAlive.aspx serves to keep a heartbeat running. While in most cases this is the equivalent of setting the idle session timeout to 0, there are cases where you could end up with a shutdown of the Asp.Net worker process - idle timeout or keepalive alike. Your worker process may terminate due to a number of reasons, ...


11

It's added by an HttpModule. In the system.webServer/modules section of the web.config. <add type="Sitecore.Web.XFrameOptionsHeaderModule, Sitecore.Kernel" name="SitecoreXFrameOptionsHeaderModule" /> Interestingly, this is appears to be new to 8.1 update 3, but it is not mentioned in the release notes.


11

I personally think the KeepAlive page is there for people who don't understand or haven't bothered to tune their IIS application settings. Even with the KeepAlive page, if your site sits idle for 29 hours it's going to turn off if you haven't touched those default settings. That may be a problem if you have a Job Server that never fields requests. So, it ...


10

I don't know that your question needs more than 4 answers, maybe you've got what you wanted, but I do have another aspect not previously mentioned :) -- so let me add yet another answer. The KeepAlive.aspx page is also used for extending active sessions in the Sitecore Client (and prevent a timeout from spoiling a long duration form edit for a content ...


10

I don't have a definitive list anywhere, and without actually attempting to remove each service one at a time until it breaks, here is the list of role services we use on a "locked down" Content Delivery environment (no Sitecore shell): [X] Web Server (IIS) Web-Server [X] Web Server ...


9

Well in any case you will have to bind example.com as well as www.example.com on your website. Next you have multiple options. Either use IIS Rewrite rules. <rule name="Root Hit Force HTTPS Redirection" enabled="true" stopProcessing="true"> <match url="^$" ignoreCase="false" /> <conditions> <add input="{HTTPS}" pattern="^OFF$" /...


9

The only thing I can think off is the fact that renaming the IIS would change Sitecore's instance name if you haven't specified it explicitly with the setting "InstanceName". Sitecore has several queues and uses this "instance name" to keep track of which servers have done what. If you have a lot of elements in the EventQueue and PublishQueue tables, ...


7

You can use either, but I recommend ApplicationPoolIdentity whenever possible. TBH, your question really isn't Sitecore-specific, but the below info should help to get you started. Application Pool Identity vs NETWORK SERVICE The security of ApplicationPoolIdentity will always be greater than or equal to that of NETWORK SERVICE, given that the same access ...


7

You need to add your directory path to IgnoreUrlPrefixes settings: <setting name="IgnoreUrlPrefixes" value="...|/your-directory-path" /> and add a web.config file inside that directory with content: <configuration> <system.webServer> <directoryBrowse enabled="true" /> </system.webServer> </configuration>


7

Yes, You can achieve this requirement through Sitecore 301 Redirect Module or IIS URL Rewrite both. Paste the below Code inside your <system.webServer></system.webServer> element in the web.config <rewrite> <rules> <rule name="Redirect Maps Rule" stopProcessing="true"> <match url=".*" /> <conditions&...


6

Besides what has been mentioned on the other answers it can be useful if you have a load balancer and you want to configure a page where the load balancer can ping sitecore to know if the node is up or not. It can be done with other pages yes but I generally use this one


6

This is the reason it's there yes, it is so: Scheduled tasks run as expected, even when traffic is low / non-existent There is no delay hitting the site if the application pool has recycled - so no building up caches etc. Could you achieve the same thing with setting the application pool idle timeout to 0? Technically, I suppose you could - I've been ...


6

Do you have any additional customization in web.config? If yes, try breaking your web.config and put your customization in separate patch files. Meanwhile also have a look at the blog post below, if you are on 64 bit OS then the registry to be edited is different. https://himadritechblog.wordpress.com/2014/09/27/how-to-fix-cannot-read-configuration-file-...


5

The only site that needs to be https is the xConnect service, though your Sitecore site is extremely highly recommended to be https as well. Since you are an XP0 configuration where everything is on a single machine, you can create a self-signed certificate to use with the xConnect service. However, you will also need a SSL client certificate for your ...


5

The problem you are seeing is a "feature" of IIS that will recycle the application pool if too many files change inside the webroot. This includes that media cache folder. I'm not sure of the actual number of changes that will trigger the restart. Making any modifications in the Web Application’s Root Directory. This means creating files/...


4

Your Sitecore application should never use the same Data folder. If they do, they will override their indexes every time while index is rebuilt. I'm guessing that's exactly what's happening in your scenario - one application tries to update its index and another one tries to perform another operation on index files in the same moment. It's not supported. ...


4

This behavior is seen if the custom host header that you use does not match the local computer name. We had the same issue where despite providing the right credentials in the window prompt, we were gettung HTTP Error 401.2 - Unauthorized. (you may get HTTP Error 401.1 too!) For enabling SSO, the Sitecore Support pointed me to an article at https://sdn....


4

It is really not Sitecore specific but I'll answer this anyway. Regarding your first question: It's not the same since the web server running on your local machine routes the request to different sites depending on the url used in the request. In the case of Sitecore the web server is probably IIS. You can see and edit the configured sites in the IIS ...


4

From what I remember, ProviderIndexSearchConfiguration class (the return type of missing method) is a really old one. It was replaced with ContentSearchConfiguration. I just checked Sitecore.Solr.Support 1.0.0 rev. 151020 which is for Sitecore 7.2 rev. 151021 and it only has private static ContentSearchConfiguration SearchConfiguration property. From what ...


4

Sitecore is not designed to work with multiple individual instances in a single AppDomain. @RichardSeal reminded me that it makes use of shared (singleton) objects that would conflict between the two applications. These are used to improve performance and aid in caching certain resources, but make coexistence of two applications impossible.


4

I'm not aware of a way to do what you are asking because deny permissions are always stronger than grant permissions, so the instruction to deny access to /sitecore/* would beat the instruction to grant access to /sitecore/service/keepalive.aspx. Instead, I would recommend following Sitecore's Security Hardening Guide (section 1.5): To restrict access to ...


3

The issue is with the web.config being greater than 250KB. You can edit the registry but that is not recommended. The better way to do is to move your Sitecore configuration to patch files in the app_config/include folder. As Himadri's blog points out you should move the section to a new patch file. Make sure the patch file is the first one to load ...


3

As far as i know, Sitecore does not recommend this, Some issues you might run into : If your site have access to master Database and tries to update items, these updates will not be synced between all the Multi IIS sites because each IIS site will have its own inconsistent memory cache. Each IIS site will have its own Sitecore memory cache of item/media ...


3

That doesn't sound like a memory leak to me - just not enough information for me to make that conclusion -, but the described symptoms may still indicate a problem. Before doing anything, have a look at @VincentGaliana's answer, and try clearing out your EventQueue and PublishQueue tables. If the issue persists, proceed with with the below. To ...


3

From the installation guide I can see Sitecore recommend ApplicationPoolIdentity or NetworkService. Please see: https://dev.sitecore.net/~/media/Downloads/Sitecore_Experience_Platform/8_0/Sitecore_Experience_Platform_8_0/Non-secure/Installation-Guide-SC80-A4.ashx on chapter 4.3 Configuring the IIS More information about Application Pool Identities : ...


3

If you mean you want to by pass Sitecore all together and load up some static HTML for example, add your path on the end of this pipe separated setting in the Web.config or in Sitecore.config in later versions of Sitecore. Sitecore will then ignore the path an IIS should take effect. <setting name="IgnoreUrlPrefixes" value=".........|/YourPath" />


3

Sitecore has the ability to define port within the node for it's sites. While SXA does not have an explicit entry to put the port in, the "Site definition" item is the SXA's equivalent of this and has an ability to provide those additional properties even if the SXA team wasn't aware of a property that should be there. The following screenshot should give ...


Only top voted, non community-wiki answers of a minimum length are eligible