Fix all invalid API doc links

wouterj · wouterj · commit a858888fee5f · 2015-08-22T11:16:07.000+02:00
diff --git a/book/http_cache.rst b/book/http_cache.rst
@@ -627,7 +627,7 @@ doing so much work.
 
     Symfony also supports weak ETags by passing ``true`` as the second
     argument to the
-    :method:`Symfony\\Component\\HttpFoundation\\Response::setETag` method.
+    :method:`Symfony\\Component\\HttpFoundation\\Response::setEtag` method.
 
 .. index::
    single: Cache; Last-Modified header
diff --git a/components/config/definition.rst b/components/config/definition.rst
@@ -121,9 +121,9 @@ Numeric Node Constraints
     The numeric (float and integer) nodes were introduced in Symfony 2.2.
 
 Numeric nodes (float and integer) provide two extra constraints -
-:method:`Symfony\\Component\\Config\\Definition\\Builder::min` and
-:method:`Symfony\\Component\\Config\\Definition\\Builder::max` -
-allowing to validate the value::
+:method:`Symfony\\Component\\Config\\Definition\\Builder\\IntegerNodeDefinition::min`
+and :method:`Symfony\\Component\\Config\\Definition\\Builder\\IntegerNodeDefinition::max`
+- allowing to validate the value::
 
     $rootNode
         ->children()
diff --git a/components/dom_crawler.rst b/components/dom_crawler.rst
@@ -188,7 +188,7 @@ The crawler supports multiple ways of adding the content::
 .. note::
 
     When dealing with character sets other than ISO-8859-1, always add HTML
-    content using the :method:`Symfony\\Component\\DomCrawler\\Crawler::addHTMLContent`
+    content using the :method:`Symfony\\Component\\DomCrawler\\Crawler::addHtmlContent`
     method where you can specify the second parameter to be your target character
     set.
 
diff --git a/components/http_foundation/session_testing.rst b/components/http_foundation/session_testing.rst
@@ -21,16 +21,16 @@ The mock storage drivers do not read or write the system globals
 ``session_id()`` or ``session_name()``. Methods are provided to simulate this if
 required:
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::getId`: Gets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::getId`: Gets the
   session ID.
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::setId`: Sets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::setId`: Sets the
   session ID.
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::getName`: Gets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::getName`: Gets the
   session name.
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::setName`: Sets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::setName`: Sets the
   session name.
 
 Unit Testing
diff --git a/components/http_foundation/sessions.rst b/components/http_foundation/sessions.rst
@@ -226,9 +226,6 @@ has a simple API
 :method:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface::has`
     Returns true if the attribute exists.
 
-:method:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface::keys`
-    Returns an array of stored attribute keys.
-
 :method:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface::replace`
     Sets multiple attributes at once: takes a keyed array and sets each key => value pair.
 
diff --git a/components/process.rst b/components/process.rst
@@ -158,7 +158,7 @@ To make your code work better on all platforms, you might want to use the
     method was introduced in Symfony 2.3.
 
 In case you are building a binary driver, you can use the
-:method:`Symfony\\Component\\Process\\Process::setPrefix` method to prefix all
+:method:`Symfony\\Component\\Process\\ProcessBuilder::setPrefix` method to prefix all
 the generated process commands.
 
 The following example will generate two process commands for a tar binary
@@ -194,7 +194,7 @@ timeout (in seconds)::
     $process->run();
 
 If the timeout is reached, a
-:class:`Symfony\\Process\\Exception\\RuntimeException` is thrown.
+:class:`Symfony\\Component\\Process\\Exception\\RuntimeException` is thrown.
 
 For long running commands, it is your responsibility to perform the timeout
 check regularly::
diff --git a/components/security/authentication.rst b/components/security/authentication.rst
@@ -101,7 +101,7 @@ Each provider (since it implements
 has a method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::supports`
 by which the ``AuthenticationProviderManager``
 can determine if it supports the given token. If this is the case, the
-manager then calls the provider's method :class:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate`.
+manager then calls the provider's method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate`.
 This method should return an authenticated token or throw an
 :class:`Symfony\\Component\\Security\\Core\\Exception\\AuthenticationException`
 (or any other exception extending it).
diff --git a/components/security/authorization.rst b/components/security/authorization.rst
@@ -177,7 +177,7 @@ Roles
 
 Roles are objects that give expression to a certain right the user has.
 The only requirement is that they implement :class:`Symfony\\Component\\Security\\Core\\Role\\RoleInterface`,
-which means they should also have a :method:`Symfony\\Component\\Security\\Core\\Role\\Role\\RoleInterface::getRole`
+which means they should also have a :method:`Symfony\\Component\\Security\\Core\\Role\\RoleInterface::getRole`
 method that returns a string representation of the role itself. The default
 :class:`Symfony\\Component\\Security\\Core\\Role\\Role` simply returns its
 first constructor argument::
diff --git a/cookbook/bundles/configuration.rst b/cookbook/bundles/configuration.rst
@@ -353,7 +353,7 @@ In order to use the schema, the XML configuration file must provide an
 ``xsi:schemaLocation`` attribute pointing to the XSD file for a certain XML
 namespace. This location always starts with the XML namespace. This XML
 namespace is then replaced with the XSD validation base path returned from
-:method:`Extension::getXsdValidationBasePath() <Symfony\\Component\\DependencyInjection\\ExtensionInterface::getXsdValidationBasePath>`
+:method:`Extension::getXsdValidationBasePath() <Symfony\\Component\\DependencyInjection\\Extension\\ExtensionInterface::getXsdValidationBasePath>`
 method. This namespace is then followed by the rest of the path from the base
 path to the file itself.
 
diff --git a/cookbook/controller/service.rst b/cookbook/controller/service.rst
@@ -324,7 +324,6 @@ controller:
     controller action method called ``Request $request``. The order of the
     parameters is not important, but the typehint must be provided.
 
-
 .. _`Controller class source code`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php
 .. _`base Controller class`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php
 .. _`FrameworkExtraBundle documentation`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/routing.html
diff --git a/cookbook/controller/upload_file.rst b/cookbook/controller/upload_file.rst
@@ -156,8 +156,9 @@ There are some important things to consider in the code of the above controller:
    provides methods for the most common operations when dealing with uploaded files.
 #. A well-known security best practice is to never trust the input provided by
    users. This also applies to the files uploaded by your visitors. The ``Uploaded``
-   class provides methods to get the original file extension (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getExtension`),
-   the original file size (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getSize`)
+   class provides methods to get the original file extension
+   (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getExtension`),
+   the original file size (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getClientSize`)
    and the original file name (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getClientOriginalName`).
    However, they are considered *not safe* because a malicious user could tamper
    that information. That's why it's always better to generate a unique name and
diff --git a/cookbook/routing/redirect_in_config.rst b/cookbook/routing/redirect_in_config.rst
@@ -17,7 +17,7 @@ Redirecting Using a Path
 
 Assume there is no default controller for the ``/`` path of your application
 and you want to redirect these requests to ``/app``. You will need to use the
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::urlRedirect`
+:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::urlRedirectAction`
 action to redirect to this new url:
 
 .. configuration-block::
@@ -97,7 +97,7 @@ Redirecting Using a Route
 Assume you are migrating your website from WordPress to Symfony, you want to
 redirect ``/wp-admin`` to the route ``sonata_admin_dashboard``. You don't know
 the path, only the route name. This can be achieved using the
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::redirect`
+:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::redirectAction`
 action:
 
 .. configuration-block::
diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst
@@ -311,7 +311,7 @@ instance), the host might have been manipulated by an attacker.
     You can read "`HTTP Host header attacks`_" for more information about
     these kinds of attacks.
 
-The Symfony :method:`Request::getHost() <Symfony\\Component\\HttpFoundation\\Request:getHost>`
+The Symfony :method:`Request::getHost() <Symfony\\Component\\HttpFoundation\\Request::getHost>`
 method might be vulnerable to some of these attacks because it depends on
 the configuration of your web server. One simple solution to avoid these
 attacks is to whitelist the hosts that your Symfony application can respond
