Creating Tests for Plugins Integration with Jenkins REST The Simple Setup Accepting Input in Other Formats Modifying the default REST routes Custom REST Routing Dispatcher Filters Configuring Filters Filter find out what user your webserver runs as. You can run inside any PHP file your webserver can execute. You should see a username printed. Change the ownership of the app/tmp CakePHP’s database configuration file is found in /app/Config/database.php.default. Make a copy of this file in the same directory, but name it database.php. The config file should be pretty straightforward:

find out what user your webserver runs as. You can run inside any PHP file your webserver can execute. You should see a username printed. Change the ownership of the app/tmp CakePHP’s database configuration file is found in /app/Config/database.php.default. Make a copy of this file in the same directory, but name it database.php. The config file should be pretty straightforward: you’ve saved your new database.php file, you should be able to open your browser and see the CakePHP welcome page. It should also tell you that your database connection file was found, and that CakePHP can

Plugin Routes SEO-Friendly Routing Matching Specific HTTP Methods Matching Specific Hostnames Routing File Extensions Route Scoped Middleware Grouping Middleware RESTful Routing Creating Nested Resource Response Objects Request ServerRequest Request Parameters Query String Parameters Request Body Data File Uploads PUT, PATCH or DELETE Data Environment Variables (from $_SERVER and $_ENV) XML or JSON Data Manipulating URIs Response Response Dealing with Content Types Sending Files Sending a String as File Setting Headers Setting the Body Setting the Character Set Interacting with Browser Caching Fine Tuning

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Getting an Excerpt From a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Editor Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751 Plugin Map File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Accepting Input in Other Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755 RESTful Routing

Plugin Routes SEO-Friendly Routing Matching Specific HTTP Methods Matching Specific Hostnames Routing File Extensions Connecting Scoped Middleware Grouping Middleware RESTful Routing Creating Nested Resource Request & Response Objects Request Request Parameters Query String Parameters Request Body Data File Uploads PUT, PATCH or DELETE Data Environment Variables (from $_SERVER and $_ENV) XML or JSON Data Checking Accept Headers Cookies Response Dealing with Content Types Sending Files Sending a String as File Setting Headers Setting the Body Setting the Character Set Interacting with Browser Caching Fine Tuning

Plugin Routes SEO-Friendly Routing Matching Specific HTTP Methods Matching Specific Hostnames Routing File Extensions Route Scoped Middleware Grouping Middleware RESTful Routing Creating Nested Resource Response Objects Request ServerRequest Request Parameters Query String Parameters Request Body Data File Uploads PUT, PATCH or DELETE Data Environment Variables (from $_SERVER and $_ENV) XML or JSON Data Manipulating URIs Response Response Dealing with Content Types Sending Files Sending a String as File Setting Headers Setting the Body Setting the Character Set Interacting with Browser Caching Fine Tuning

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 Getting an Excerpt From a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 Editor Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Plugin Map File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . view template containing it, or a XML formatted result for others to consume: // In a view template file, we'll render an 'element' for each user.