anchor.diff:  usage: 512M x 1 instances
   urls: jc0830-spring.<%=vars.app_domain%>
   
  -     state     since                    cpu    memory           disk   
  -#0   running   2014-08-28 06:31:37 PM   0.0%   277.8M of 512M   137.9M of 1G 
  +     state     since                    cpu    memory           disk
  +#0   running   2014-08-28 06:31:37 PM   0.0%   277.8M of 512M   137.9M of 1G
   
   </pre>
   
  -### <a id='sample-step4'></a>Step 4: Test the Sample App ###
  +### Step 4: Test the Sample App ###
   
   You’ve deployed your first app to <%=vars.product_short%>! Now let’s access your app online using its URL.
   In the terminal output, the `urls` field of the `App started` block contains the app URL. This is the `HOST_NAME` you specified with the `-n` flag plus the domain `<%=vars.app_domain%>`. The image shows the resulting webpage for the `spring-music` app.
  
positive.code: 	usage: 512M x 1 instances
  	urls: jc0830-spring.<%=vars.app_domain%>
  
  	     state     since                    cpu    memory           disk   
  	#0   running   2014-08-28 06:31:37 PM   0.0%   277.8M of 512M   137.9M of 1G
      </pre>
  
  
negative.code: 
  Run `cf help` to view a complete list of commands, grouped by task categories, and run `cf help [COMMAND]` for detailed information about a specific command. For more information about using the `cf` CLI, refer to the cf Command Line Interface (CLI) topics, especially the <%=vars.cli_v6%> topic.
  
  <p class="note"><strong>Note</strong>: You cannot perform certain tasks in the <%=vars.dev_console_2%> because these are commands that only a <%=vars.product_short%> administrator can run. If you are not a <%=vars.product_short%> administrator, the following message displays for these types of commands:
  
  <code>error code: 10003, message: You are not authorized to perform the requested action</code>
  
  <%=vars.dev_console_note%>
  </p>
  
  ## <a id='troubleshoot'></a>Troubleshooting ##
  If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
  
  ### App Deploy Fails ###
  Even when the deploy fails, the app might exist on <%=vars.product_short%>. Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy.
  
  ### App Requires a Content-Type ###
  
  If you specify a `Content-Encoding` header of `gzip` but do not specify a `Content-Type` within your application, <%=vars.product_short%> might send a `Content-Type` of `application/x-gzip` to the browser. This scenario might cause the deploy to fail if it conflicts with the actual encoded content of your app. To avoid this issue, be sure to explicitly set `Content-Type` within your app.
  
  ### App Requires a Unique URL ###
  <%=vars.product_short%> requires that each app that you deploy have a unique URL. Otherwise, the new app URL collides with an existing app URL and <%=vars.product_short%> cannot successfully deploy the app. You can fix this issue by running `cf push` with either of the following flags to create a unique URL:
  
  * `-n` to assign a different HOST name for the app.
  * `--random-route` to create a URL that includes the app name and random words. Using this option might create a long URL, depending on the number of words that the app name includes.
  
  
  
  
  
  
  