<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>CloudFoundry on Bill Glover</title>
		<link>https://old.bill.dev/tags/cloudfoundry/</link>
		<description>Recent content in CloudFoundry on Bill Glover</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
			<managingEditor>hello@bill.dev (Bill)</managingEditor>
		
		
			<webMaster>hello@bill.dev (Bill)</webMaster>
		
		
		
			<lastBuildDate>Sun, 28 Sep 2025 22:27:35 +0100</lastBuildDate>
		
			<atom:link href="https://old.bill.dev/tags/cloudfoundry/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Investigating HTTP 502 responses on Cloud Foundry</title>
				<link>https://old.bill.dev/2024/08/16/investigating-http-502-responses-on-cloud-foundry/</link>
				<pubDate>Fri, 16 Aug 2024 16:27:03 +0100</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2024/08/16/investigating-http-502-responses-on-cloud-foundry/</guid>
				<description>&lt;p&gt;As a platform engineer working with multiple platform teams running applications on the Tanzu Platform for Cloud Foundry, I have been addressing intermittent issues that have been overlooked as quirks of the platform. These issues are what I like to call developer paper cuts. They are points of friction where something does not function as expected but occurs infrequently, leading to a lack of prioritization for investigation.&#xA;One of these developer paper cuts is the occurrence of the HTTP 502 response code from services operating on the platform. In this post, I will detail our investigation into this issue, highlight some known causes of the 502 response code, and provide tips for debugging similar issues.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
