Deploying a Nozzle to the Loggregator Firehose.Installing the Loggregator Plugin for cf CLI.Monitoring and Testing Diego Components.

Configuring Health Monitor Notifications.Configuring Diego Cell Disk Cleanup Scheduling.Configuring SSH Access for Cloud Foundry.Running and Troubleshooting Cloud Foundry.Configuring Load Balancer Health Checks for CF Routers.Getting Started with the Notifications Service.Creating and Managing Users with the UAA CLI (UAAC).Creating and Managing Users with the cf CLI.Cloud Controller Blobstore Configuration.Backup and Restore for External Blobstores.Configuring Your Cloud Foundry for BOSH Backup and Restore.Migrating from cf-release to cf-deployment.Deploying Cloud Foundry with cf-deployment.Using the cf CLI with a Self-Signed Certificate.Cloud Foundry Command Line Interface (cf CLI).User Account and Authentication (UAA) Server.How Cloud Foundry Maintains High Availability.Note: To proxy localhost (and related addresses) with newer Firefox versions (>= 67) the preference _hijacking_localhost (accessible through the about:config page) must be set to true. Ensure ‘SSL Proxy’ is also configured, either by selecting ‘Use this proxy server for all protocols’ or by setting the corresponding values. ‘Port’ field to the right of the ‘HTTP Proxy’ field the ‘Port’ you configured in the Options Local Proxies screen. ‘HTTP Proxy:’ field the ‘Address’ you configured in the Options Local Proxies screen ‘Manual proxy configuration’ radio button Note: To proxy localhost (and related addresses) with newer Chrome versions (>= 72) the command line argument -proxy-bypass-list= must be provided. ‘Customise and control Google Chrome’ button (top right) Instructions for the latest versions of the most commonly used browsers: Chrome (on Windows) You will need to configure your browser to use ZAP as a proxy.īy default ZAP uses an Address of ’localhost’ and a Port of ‘8080’, but these can be changed via the

Line app for pc proxy setting