New answers tagged

1

Adding this condition <add input="{REQUEST_URI}" url="^nossl/.*" negate="true" /> resulted in a 500 Internal Server error. After reading the documentation a bit more I changed it to this and had a better result. <rule name="Redirect to HTTPS except nossl folder" stopProcessing="true"> <match url="(.*)" /> <conditions ...


2

In order for two servers to share the exact same domain (www.example.com) and your website to work properly the two servers would need to be a mirror of eachother in terms of content and functionality, ideally linked to the same databases and storage behind the scenes since the same user may access either server within the same session. This would be setup ...


3

There is a risk with URL changes of SEO problems, ranking loss, and traffic declines. When correctly implemented with 301 redirects, it can go perfectly fine, but it doesn't always do so. I recommend changing URLs only when there is an overwhelming need. If you do want to change URLs you should consider gentler changes as well: Chang the URL structure ...


4

If you correctly put in 301 redirects and update your sitemap, the site will be fine. However... What are you trying to gain from this change? The Stack Exchange-style hierarchy doesn't make sense for what it seems you're trying to accomplish (a Wikipedia-style website?). What you currently have makes more sense in terms of organizing the information: ...


1

It would seem "the problem" is in your PHP code, not .htaccess as you seem to suggest. RewriteRule ^(.+)$ index.php?page=$1 [QSA,L] All requests are rewritten to index.php (your "front-controller") which then routes your URLs. It is this PHP script that determines whether /login or /login/asdasdasd, etc. resolve to a valid page on your site. This has ...


Top 50 recent answers are included