OVH Community

Bienvenue sur votre espace communautaire. Posez des questions, recherchez des informations, publiez du contenu et interagissez avec d’autres membres OVH Community.

BBD/Index.PHP/HTTPS


#17

google search n'a rien à voir avec les redirections!
heureusement google ne gouverne pas encore tout le net

les redirections données sont correctes et REQUISES!
elles ne sont toujours pas mises en oeuvre


#18

Oui mais je perd tous le SEO.... xD


#19

non... justement!
les redirections 301 sont là pour ça, mais si tu crois que je ne connais pas le métier, renseignes toi avant d'affirmer (WebRankInfo, alsacreations,...)


#20

Ba je remet dans htaccess toutes les lignes donné pour te montré ce que ca donne :)

https://www.google.fr/search?ei=3xbnW-T0Hs2uatqogpgM&q=anarkia+333+data&oq=anarkia+333+data&gs_l=psy-ab.3..33i160k1l2.2828.10091.0.10652.16.16.0.0.0.0.171.1028.15j1.16.0....0...1c.1.64.psy-ab..0.12.786...0j0i131k1j0i67k1j0i131i67k1j0i30k1j33i21k1.0.TsgBylk4QcY

tous est rediriger sur la page d'aceuil :(


#21

arrete de psychoter sur google

le htaccess n'a rien à voir sur ce qui s'affichent dans l'index google
déjà dit, l'index évolue sur des semaines, lit et renseigne toi

voire google ralentirait volontairement l'évolution, mais personne ne le sait ;)


#22

oki donc je laisse et les redirection seront bonne plus tard?.... :)


#23

non
les redirection sont bonnes dès maintenant:

curl --head -XGET http://anarkia333data.center/
   HTTP/1.1 301 Moved Permanently
   Location: https://anarkia333data.center/

curl --head -XGET http://www.anarkia333data.center/
   HTTP/1.1 301 Moved Permanently
   Location: https://anarkia333data.center/

curl --head -XGET https://anarkia333data.center/
   HTTP/2 200 

curl --head -XGET https://www.anarkia333data.center/
   HTTP/2 301 
   location: https://anarkia333data.center/

location utilisée:
   https://anarkia333data.center/

plus tard tu en verras les bénéfices dans google search
comme tu ne verras pas les bénéfices chez les autres ;)


#24

Ok, mais les 600 pages ne redirige plus vers les bonnes pages xD...

Google, Yahoo, pareil... xD

Problème non corrigé.

Quelqu'un d'autre à une idée?


#25

ok, as tu seulement essayé?
enlèves et on en parles plus


#26

Ah le Glossaire mache maintenant en HTTPS mais pas les autres.... xD

Faut pt attendre une routine de google alors.... :)


#27

Apperement elle a été indexer today par Google c'est la seul pour l'instant.... xD

Donc j'en reviens a ce que je disais faut que Google Re-Index tous en HTTPS. :)


#28

Bonsoir,

peux-tu poster ton .htaccess complet ?

Cordialement,
Boris.


#29

Apache/PHP/Drupal settings:

Protect files and directories from prying eyes.

<FilesMatch ".(engine|inc|install|make|module|profile|po|sh|.sql|theme|twig|tpl(.php)?|xtmpl|yml)(~|.sw[op]|.bak|.orig|.save)?$|^(.(?!well-known).|Entries.|Repository|Root|Tag|Template|composer.(json|lock))$|^#.#$|.php(~|.sw[op]|.bak|.orig|.save)$">

Require all denied


Order allow,deny

Don't show directory listings for URLs which map to a directory.

Options -Indexes

Set the default handler.

DirectoryIndex index.php index.html index.htm

Add correct encoding for SVGZ.

AddType image/svg+xml svg svgz
AddEncoding gzip svgz

Most of the following PHP settings cannot be changed at runtime. See

sites/default/default.settings.php and

Drupal\Core\DrupalKernel::bootEnvironment() for settings that can be

changed at runtime.

PHP 5, Apache 1 and 2.


php_value assert.active 0
php_flag session.auto_start off
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_flag mbstring.encoding_translation off
# PHP 5.6 has deprecated $HTTP_RAW_POST_DATA and produces warnings if this is
# not set.
php_value always_populate_raw_post_data -1

Requires mod_expires to be enabled.


# Enable expirations.
ExpiresActive On

# Cache all files for 2 weeks after access (A).
ExpiresDefault A1209600


# Do not allow PHP scripts to be cached unless they explicitly send cache
# headers themselves. Otherwise all scripts would have to overwrite the
# headers set by mod_expires if they want another caching behavior. This may
# fail if an error occurs early in the bootstrap process, and it may cause
# problems if a non-Drupal PHP file is installed in a subdirectory.
ExpiresActive Off

Set a fallback resource if mod_rewrite is not enabled. This allows Drupal to

work without clean URLs. This requires Apache version >= 2.2.16. If Drupal is

not accessed by the top level URL (i.e.: http://example.com/drupal/ instead of

http://example.com/), the path to index.php will need to be adjusted.


FallbackResource /index.php

Various rewrite rules.


RewriteEngine on

# Set "protossl" to "s" if we were accessed via https://. This is used later
# if you enable "www." stripping or enforcement, in order to ensure that
# you don't bounce between http and https.
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]

# Make sure Authorization HTTP header is available to PHP
# even when running as CGI or FastCGI.
RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Block access to "hidden" directories whose names begin with a period. This
# includes directories used by version control systems such as Subversion or
# Git to store control files. Files whose names begin with a period, as well
# as the control files used by CVS, are protected by the FilesMatch directive
# above.
#
# NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
# not possible to block access to entire directories from .htaccess because
# is not allowed here.
#
# If you do not have mod_rewrite installed, you should remove these
# directories from your webroot or otherwise protect them from being
# downloaded.
RewriteRule "/.|^.(?!well-known/)" - [F]

# If your site can be accessed both with and without the 'www.' prefix, you
# can use one of the following settings to redirect users to your preferred
# URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
#
# To redirect all users to access the site WITH the 'www.' prefix,
# (http://example.com/foo will be redirected to http://www.example.com/foo)
# uncomment the following:
# RewriteCond %{HTTP_HOST} .
# RewriteCond %{HTTP_HOST} !^www. [NC]
# RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
#
# To redirect all users to access the site WITHOUT the 'www.' prefix,
# (http://www.example.com/foo will be redirected to http://example.com/foo)
# uncomment the following:
# RewriteCond %{HTTP_HOST} ^www.(.+)$ [NC]
# RewriteRule ^ http%{ENV:protossl}://%1%{REQUEST_URI} [L,R=301]

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
# RewriteBase /drupal
#
# If your site is running in a VirtualDocumentRoot at http://example.com/,
# uncomment the following line:
# RewriteBase /

# Redirect common PHP files to their new locations.
RewriteCond %{REQUEST_URI} ^(.*)?/(install.php) [OR]
RewriteCond %{REQUEST_URI} ^(.*)?/(rebuild.php)
RewriteCond %{REQUEST_URI} !core
RewriteRule ^ %1/core/%2 [L,QSA,R=301]

# Rewrite install.php during installation to see if mod_rewrite is working
RewriteRule ^core/install.php core/install.php?rewrite=ok [QSA,L]

# Pass all requests not referring directly to files in the filesystem to
# index.php.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^ index.php [L]

# For security reasons, deny access to other PHP files on public sites.
# Note: The following URI conditions are not anchored at the start (^),
# because Drupal may be located in a subdirectory. To further improve
# security, you can replace '!/' with '!^/'.
# Allow access to PHP files in /core (like authorize.php or install.php):
RewriteCond %{REQUEST_URI} !/core/[^/]*.php$
# Allow access to test-specific PHP files:
RewriteCond %{REQUEST_URI} !/core/modules/system/tests/https?.php
# Allow access to Statistics module's custom front controller.
# Copy and adapt this rule to directly execute PHP files in contributed or
# custom modules or to run another PHP application in the same directory.
RewriteCond %{REQUEST_URI} !/core/modules/statistics/statistics.php$
# Deny access to any other PHP files that do not match the rules above.
# Specifically, disallow autoload.php from being served directly.
RewriteRule "^(.+/.*|autoload).php($|/)" - [F]

# Rules to correctly serve gzip compressed CSS and JS files.
# Requires both mod_rewrite and mod_headers to be enabled.

# Serve gzip compressed CSS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}.gz -s
RewriteRule ^(.*).css $1.css.gz [QSA]

# Serve gzip compressed JS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

# Serve correct content types, and prevent mod_deflate double gzip.
RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

<FilesMatch "(\.js\.gz|\.css\.gz)$">
  # Serve correct encoding type.
  Header set Content-Encoding gzip
  # Force proxies to cache gzipped & non-gzipped css/js files separately.
  Header append Vary Accept-Encoding
</FilesMatch>


Various header fixes.


# Disable content sniffing, since it's an attack vector.
Header always set X-Content-Type-Options nosniff
# Disable Proxy header, since it's an attack vector.
RequestHeader unset Proxy

http -> https ET www -> no-www

RewriteCond %{HTTP_HOST} ^www.(.+)$
RewriteRule ^ https://%1%{REQUEST_URI} [R=301,L,NE,QSA]
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE,QSA]


#30

les redirections se mettent en tête de fichier... tu t'es bien renseigné je vois


#31

tu dois mettre les 4 dernières lignes en haut.

Cdlt,
Boris


#32

Ah merci! je le fais de suite xD


#33

enfin tout en haut juste dessous la ligne

RewriteEngine on

#34

Yeaaaaaaaaa ca marche merci!!! xD


#35

Re-bonjour :)

J'ai commander une offre pro Samedi et on est Dimanche je dois attendre Lundi je pense??? xD


#36

C'est bon je suis passé à l'abonement PRO mais ma BDD est passé de 200Mo à 400Mo j'aurai bien aimé plutot qu'elle sois passé à la BDD de 2Giga.

Je peux changé comme ca de BDD avec l'interface OVH???