Log in Register
× Here you can get community support related to ReDJ.

Redirects not Working in IIS

  • adam.hughes
  • Topic Author
  • Offline
  • New Member
  • New Member
More
10 years 11 months ago #1155 by adam.hughes
Redirects not Working in IIS was created by adam.hughes
I have just installed ReDJ enterprise 1.7.2 into my Joomla 2.5.11 installation, enabled the plugin and set up a simple redirect, but it is not redirecting at all.

All I get is the standard 404 error page for the site.
I have looked at the forums and the only fix for this is to update the .htaccess file, but this is for apache web servers and mine is IIS.

Does this component work under IIS (it does not list anything on your site about requiring apache) ?

Cheers

Please Log in or Create an account to join the conversation.

More
10 years 11 months ago - 10 years 11 months ago #1156 by admin
Replied by admin on topic Redirects not Working in IIS
Hi,
could you pls send me an example of your rule, and the error you get? I need to check this, so you can send me an email at info(at)selfget.com or post here, as you prefer.

If you need the ErrorDocument feature for your IIS, you must use the web.config file, and add this:
<httpErrors>
               <remove statusCode="404" subStatusCode="-1" />
               <error statusCode="404" prefixLanguageFilePath="" path="/index.php" responseMode="ExecuteURL" />
           </httpErrors>

Nested inside the "<system.webServer>" (same level of <rewrite></rewrite>).

Attached the Joomla 3 web.config.txt file modified with the error document option.

Kind regards,
Luigi

This message has an attachment file.
Please log in or register to see it.

Last edit: 10 years 11 months ago by admin.

Please Log in or Create an account to join the conversation.

  • adam.hughes
  • Topic Author
  • Offline
  • New Member
  • New Member
More
10 years 11 months ago #1157 by adam.hughes
Replied by adam.hughes on topic Redirects not Working in IIS
Thank you for the quick response.

I'm not sure how I export the example of teh url so I've copied it from the admin gui :

From URL : /videos/instantporch2
To URL : www.youtube.com/questleisure
Comments : Video link in AWning instructions. Redirecting direct to You Tube Channel

Case sensitive: no
Request Only: yes
Decode URL: yes
Placeholders: 0

From the stats it says that I have had 0 hits and the rule is published.
The error I get in the browser is a standard http 404

I'm not looking to use the errordocument feature (yet), but may do in teh future (once my other url redirects are done).

Cheers

Please Log in or Create an account to join the conversation.

More
10 years 11 months ago #1158 by admin
Replied by admin on topic Redirects not Working in IIS
Check that ReDJ plugin is enabled. And I would like to check what you call "standard http 404", cause if this is the one provided by your IIS, this is the moment for you to add the ErrorDocument feature. Please, send me an email with the full URL to call.

Kind regards

Please Log in or Create an account to join the conversation.

  • adam.hughes
  • Topic Author
  • Offline
  • New Member
  • New Member
More
10 years 11 months ago #1159 by adam.hughes
Replied by adam.hughes on topic Redirects not Working in IIS
I can confirm that the following reDJ components are enabled :
Site Package
Administrator Component
Site Plugin

The error from the IIS logs is shown below
2013-06-03 09:53:44 87.106.101.61 GET /videos/instantporch2 - 80 - 217.36.1.254 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 404 0 2 46

The url to test it is :

www.questleisure.com/videos/instantporch2

Cheers

Please Log in or Create an account to join the conversation.

More
10 years 11 months ago #1160 by admin
Replied by admin on topic Redirects not Working in IIS
Ok,
this is the server error page, so in this case the response comes from IIS, no way for Joomla or ReDJ to do nothing. This is the reason why you need to add the ErrorDocument, you tell IIS to let Joomla (and ReDJ) manage 404 errors...

Please Log in or Create an account to join the conversation.

Time to create page: 0.100 seconds