12

In my investigation and research into this issue I spoke with Andy Cohen the contributor for this module and he let me know that here is the proper format for Simple Redirect paths: http://xyzcompany.com/about would just be about in the Path field just the name of the page. However, if you have a page that is multiple pages deep you separate the folders ...


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$" /...


8

We faced the same issue about a month ago. You can use the following rewrite rule. <?xml version="1.0" encoding="utf-8"?> <configuration> <system.webServer> <rewrite> <rule name="Blog rewrite" enabled="true" > <match url="^blog/(.*)$" /> <action type="Rewrite" url="http://your.other....


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

This is possible with the IIS rewrite module. This example comes from the Microsoft iis.net site: to rewrite http://localhost/pag342 to: http://localhost/page2?id=342 you would need find a pattern by using a regular expression (^pag/([0-9]+) (this finds 342) and redirect it using an action: page2?id={R:1} A detailed guide on exactly your problem can be ...


5

Your CM and CD servers are available by different addresses.(e.g.: cms.test.com and www.test.com) It is possible to filter redirect rule before execution using {HTTP_HOST} variable: <rule name="Force SSL" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAny"> <add input="{HTTP_HOST}" pattern="...


5

The simple redirects assume that your matching url is at the root. There is no need for a beginning forward slash. When you installed the module, it comes with examples located at /sitecore/Content/Sample Rewrites. There is an example of both of these situations; one for external links and one for internal links, named accordingly: Simple External ...


4

This may happen when you have a sibling item (e.g. folder or item without a layout) with the same name or display name. Be aware that Sitecore replaces hyphens to spaces when it tries to find an item in the tree, so if your url is customer-care-support you have a sibling with a name customer care support next to your customer-care-support item, you can ...


3

The path should be the relative to the root of the site (no scheme or domain). It sounds like you also have an error page module or custom built functionality also installed. My guess is that module is running and returning your 404 page before the URL Rewrite module has a chance to run. Check the httpRequestBegin pipeline in /sitecore/admin/showconfig....


3

The Sitecore URL rewrite module is conceptually based on the IIS Rewrite Module Shiva referenced. You would essentially do the same thing Shiva outlined but withing Sitecore using the Inbound Rule with a Condition instead of the Simple Redirect way you are trying now. Steps: Create a new Inbound Rule item - call it whatever you want Pattern: (.*) Create ...


2

You could use Sitecore wildcard item(s) to achieve this. You create a page underneath searchpage and name it "*". Sitecore will map all request that are made to something underneath searchpage (and can't be resolved) to this wildcard item. The wildcard item itself is actually an item just like any other - so you can put a layout and renderings on it. In ...


2

From what I understand, you want to implement custom logic for generation of internal links added by content authors in Rich Text fields. If that's the case, you need to change the logic of renderField pipeline and its ExpandLinks processor. By default this processor calls DynamicLink.ExpandLinks(...) method. You would need to replace that with your custom ...


1

Turns out the solution was to add the naked domain xyz.com to the custom domains list. It involved pointing the A record and a TXT identifier in the DNS to Azure, so the custom domain system could detect it. Azure walks you through it pretty easily.


1

There is a wildcard module available in Sitecore marketplace which can exactly help you in your blog post with blog detail scenario. Module's marketplace link : https://marketplace.sitecore.net/en/Modules/Wildcard_module.aspx There is also an excellent demo (youtube video) of this module by Adam Conn : http://www.youtube.com/watch?v=ckbfIs9iqMY This module ...


1

It's quite difficult to answer this question with certainty as it may be a bit of trial and error, but you can try this rewrite rule <rule name="1" stopProcessing="true" patternSyntax="ExactMatch"> <match url="xxxx/yyy/page/19/?paged=20" /> <action type="Redirect" url="/aaaa/bbbbb"/> </rule>


1

As an alternative you can write your own processor. For example like you would create a 404 processor, but then let it hook into a Sitecore list where you map url's to external links. Like: public class NotFoundRedirectProcessor: HttpRequestProcessor { public override void Process(HttpRequestArgs args) { if (Sitecore.Context.Item != null || ...


1

You can write your own re-write rule: https://docs.microsoft.com/en-us/iis/extensions/url-rewrite-module/creating-rewrite-rules-for-the-url-rewrite-module It is not related to the Sitecore. If you want to handle inside the Sitecore, you have to use rewrite rule module available on the Sitecore Marketplace.


1

You can force the PageMode with a pipeline processor to set the display mode, this will cause the user to be redirected to the Sitecore Login page if they are not previously logged in: public class SetPageMode : HttpRequestProcessor { public override void Process(HttpRequestArgs args) { if (Sitecore.Context.PageMode.IsNormal) { Sitecore....


1

After changing DNS of the sub-domain to point to your server IP address, you have to redirect traffic from the sub-domain host name(location.mysite.com) to your target URL(www.mysite.com/locations) in URL redirect module. Use following redirect rule in URL redirect module <rule name="External Site" stopProcessing="true"> ...


1

After going through all the files in the package and checking the content of them I found the culprit. There was a file (Hi.UrlRewrite.Prefetch.Master.config) which references the master database which obviously doesn't exist on the CD server. Removing this file stopped the site dying and the redirects now work.


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