Use it. http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule :# включаем mod_rewrite RewriteEngine on # все перенаправления будут указываться относительно корня сайта RewriteBase / перенаправляем game в index.php без редиректа RewriteRule ^game$ index.php In doing so, file .htaccess should lie at the root of the site (on index.php).

I don't know why you need to hide the link from the outside eye - that a priori must be known to the client. Any request to be made by a browser is not important, by compressing the user to a reference or by a "cut" request for ajax, can be traced. All the logic that the client doesn't have to face should be on the server. Describe what you want to do with this action.

You do that:List elementTurn it off.Incorporate the development panel in chrome/ffLocking up the file and remembering url loading.You add an exception to...htaccess.

RewriteCond %{QUERY_STRING} PAGE=(\d+) [NC] RewriteRule ^([a-zA-Z_0-9-]+)/([a-zA-Z_0-9-]+)/(\d+)/$ /$1/$2/$3/? [R=301,L]

It's called Hotlinking protection. But it can also be used to protect me from downloading. It's based on the referer title check and described in https://httpd.apache.org/docs/2.4/rewrite/access.html#blocked-inline-images ♪Of course, if you wish, the file could still be downloaded by putting its head on Referer, because that headline is sent by the user. Or download with a flame. But from a simple download, this way protects.In .htaccess, the type rule should be added:RewriteCond "%{HTTP_REFERER}" "!www.example.com" [NC] RewriteRule "\.(mp4|avi|mov)$" "-" [F,NC]

If in the case of apache, the file says:<IfModule mod_rewrite.c> RewriteEngine On RewriteRule ^poka$ /privet [R=301] </IfModule> Also, you can just put a symbolic reference to "poka" referring to "privet," and include:<IfModule mod_rewrite.c> Options +FollowSymLinks </IfModule> Actually, mod_rewrite has many different possibilities, googling.

from robots to robots.txt:Disalow:/your/ajax/url The user &apos; s sense of the act does not justify its implementation. Since you make a request and the browser tracks it. Conclusion:The robots should be closed. You don't even have to get excited.

RewriteCond %{HTTP_HOST} ^([^www].*)$ RewriteRule ^(.*)$ http://www.%1/$1 [L,R=301] That's what we've been dealing with for all the addresses, without a bunch of extra notes.

RewriteRule /name/detail.php-ID=(\d+) /name/detail.php?ID=$1 So?

There's a point where you need to: (1) It is the re-addressRewriteEngine On RewriteRule ^$ /frontend [R=301,L] #или RedirectMatch permanent ^$ /frontend #--- RewriteRule ^admin(/(.*))?$ /new-admin$1 [R=301,L] #или RedirectMatch permanent ^/admin(/(.*))?$ /new-admin$1 (2) The possibility of receiving information from another location without redirectionRewriteEngine On RewriteRule ^admin(/(.*))?$ /new-admin$1 [L] #или RewriteRule ^admin(/(.*))?$ /myscript.php?url=$1 [L] Something like that. ♪ ♪P.s. and it's just as a working example... you're still getting drunk.

It's possible to deny access to this file. .htaccess with such contents<Limit GET POST PUT> Order Allow,Deny Deny from All </Limit>

RewriteRule "^(.*)//+(.*)$" "$1/$2" [R=301,L] RewriteCond "%{HTTP_HOST}" "^www\.(.+)$" [NC] RewriteRule "^" "http://%1%{REQUEST_URI}" [L,R=permanent] RewriteCond "%{REQUEST_FILENAME}" !-f RewriteCond "%{REQUEST_FILENAME}" !-d RewriteRule "^" "index.php" [L] # index.php в папке с htaccess track in the slog LogLevel rewrite:trace8

Try doing that in the file.RewriteEngine On # если после расширения .php идет слэш и потом может встретиться подстрока .png RewriteCond %{REQUEST_URI} \.php/.*\.png [NC] # то вернем стандартую 404 ошибку сервера RewriteRule ^ - [R=404,L] Better.RewriteEngine On # если после расширения .php идет слэш, а такого не должно быть RewriteCond %{REQUEST_URI} \.php/ [NC] # то вернем стандартую 404 ошибку сервера RewriteRule ^ - [R=404,L]

In the structure you described, I don't quite understand why you've got a Router on the counteraller. I mean, I figured out the sequence.index.php - municipal loader.php - constant controller.php -article router.phpWhat's the dealer responsible for? It's just a roller connection?I think a common approach can be organized in such a way as:index.php - municipal loader.php - channelr.php - controller.phpWhere controller.php is the controller of every single page, that is CatalogController, ProductController.Moment 2Why do you have to connect a template in the router? The main and only task of the Router is to clear the url and connect the controller. We need to connect the necessary templates to the counteraller. To this end, an abstract Controller class, which is a method, for example, renders, which will include the appropriate template.MultilingualismThe general solution is that:Dissolve the url and if there's anything like the local after the site's address, we'll load the necessary language file, and if we don't find a standard load. In the template, the full statistical withdrawal of the information is obtained through a function which, by code, produces the necessary text from the language file.

The reason for such conduct may be:Relative, not absolute, to the required fileFile doesn't exist.Therefore, in order to correct this error, it is necessary:Check the way to the Apache fileIndicate the absolute path to core/sitemap.phpCheck verify the existence of the file on the specified routeI don't see any mistakes in syntax.One observation: regular expression sitemap_(.*)([0-9]+)\.xml$ Not only do these website maps match: sitemap_index0.xmlsitemap_product0.xmlBut also:sitemap_0.xmlsitemap_1.xmlIf such behaviour is undesirable, it should be corrected. (.*) ♪ (.+)Having finally received such a regular expression: sitemap_(.+)([0-9]+)\.xml$♪

Not strong in htaccess, but I saw it in one move.# если директория или файл существуют, использовать их напрямую RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d

I guess it's like this:RewriteEngine on RewriteCond %{HTTP_COOKIE} ^.*test=true.*$ [NC] RewriteRule 403 /notfound.html

I already have.<rule name="rule 1G" stopProcessing="true"> <match url="^(.*)\.html$" /> <action type="Rewrite" url="/{R:1}.php" /> </rule>

http://httpd.apache.org/docs/2.4/mod/core.html#filesmatch ! In the documentation for Apache, a similar example was considered in the most detailed manner:The <FilesMatch> directive limits the scope of the enclosed directives by filename, just as the <Files> directive does. However, it accepts a regular expression. For example:<FilesMatch ".+\.(gif|jpe?g|png)$"> # ... </FilesMatch> would match most common Internet graphics formats.The .+ at the start of the regex ensures that files named .png, or .gif, for example, are not matched. From 2.4.8 onwards, named groups and backreferences are captured and written to the environment with the corresponding name prefixed with "MATCH_" and in upper case. This allows elements of files to be referenced from within expressions and modules like mod_rewrite. In order to prevent confusion, numbered (unnamed) backreferences are ignored. Use named groups instead.<FilesMatch "^(?<sitename>[^/]+)"> require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example </FilesMatch>

Put it in the right folder (in which you want to ban access to files with txt expansion) file ...htaccess with such contents:<FilesMatch "\.txt$"> Order Deny,Allow Deny from all </FilesMatch>