Hi Dave

What version of Umbraco are you using?

Are IIS settings the same?

Thanks,

Alex

Im using 7.6.1.

IIS has no difference in setup (that i can see at least)

also, here's the snippet from umbracosettings.config

<web.routing trySkipIisCustomErrors="true" internalRedirectPreservesTemplate="false" disableAlternativeTemplates="false" disableFindContentByIdPath="false"
    umbracoApplicationUrl="" disableRedirectUrlTracking="false">
  </web.routing>

Do you have "URL Rewrite" installed on both IISes?

https://www.iis.net/downloads/microsoft/url-rewrite

I dont have it on either IIS. But like i said, it works locally. I didnt think umbraco's build in redirect tracker used IIS anyway?

Do you have one of these dlls in bin folder?

  "InfoCaster.Umbraco.UrlTracker"
  "SEOChecker"
  "Simple301"
  "Terabyte.Umbraco.Modules.PermanentRedirect"
  "CMUmbracoTools"
  "PWUrlRedirect"

If the code is the same then IIS or database is the problem.

Nope, i don't have any of those dll's. should i?

So you can see why I've emssaged here. Nothing seems out of place compared between local and live...

update: i've upgeaded to version 7.6.4 of Umbraco and that made no difference.

Hi Dave

What is the difference between the test environment and live?

Is it the save server?

Are you using maybe CloudFlare? Host management in Umbraco?

Thanks,

Alex

There's 3 environments.

the dev environment local on my machine. Which works.

both the staging and live environments are exactly the same and neither work. They are within azure cloud, load balanced across multiple servers and use a CDN.

The IIS configuration is mostly the same. The only differences really are file compression and error logging.

I've just tried installing one of the third party packages that handle redirects, UrlTracker. https://www.nuget.org/packages/UrlTracker/

Just tried this out in my staging environment and it works.

Could the issue be something to do with Umbraco's tracker not working within azure?

It shouldn't be an issue.

Just came across the same issue myself. For future reference, the explanation (and a workaround) is here http://issues.umbraco.org/issue/U4-9511

Hi Dave,

You havent mention much about your environment, programming language, and framework, i will give you some common web framework like Express.js in Node.js:

const express = require('express');
const app = express();

// Redirect route
app.get('/old-url', (req, res) => {
  res.redirect(301, '/new-url');
});

// Other routes
app.get('/new-url', (req, res) => {
  res.send('This is the new URL');
});

// Start the server
app.listen(3000, () => {
  console.log('Server is running on port 3000');
});

when a user visits the /old-url route, the server responds with a 301 redirect to the /new-url route. You can define more redirect rules based on your specific requirements. You can get deep url redirection chain on any online tool such as this redirectchecker.com tool.

is working on a reply...