<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gorouter on mcclain.sh</title><link>http://mcclain.sh/tags/gorouter/</link><description>Recent content in Gorouter on mcclain.sh</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 May 2014 00:00:00 +0000</lastBuildDate><atom:link href="http://mcclain.sh/tags/gorouter/index.xml" rel="self" type="application/rss+xml"/><item><title>Hacking on Cloud Foundry's Gorouter</title><link>http://mcclain.sh/posts/hacking-on-cloud-foundrys-gorouter/</link><pubDate>Mon, 12 May 2014 00:00:00 +0000</pubDate><guid>http://mcclain.sh/posts/hacking-on-cloud-foundrys-gorouter/</guid><description>&lt;p&gt;Late last week, a couple colleagues and myself discovered a small bug in Cloud Foundry&amp;rsquo;s &lt;a href="https://github.com/cloudfoundry/gorouter" target="_blank" rel="noopener noreffer "&gt;gorouter&lt;/a&gt; in which a websocket upgrade was not completed if a comma-separated list of values in the Connection header was provided. A &lt;a href="https://github.com/cloudfoundry/gorouter/pull/39" target="_blank" rel="noopener noreffer "&gt;pull request&lt;/a&gt; was pieced together, submitted and is currently being looked at by Pivotal. However, I figured, why let the learning stop there?&lt;/p&gt;
&lt;p&gt;There were several things that I was unfamiliar with:&lt;/p&gt;</description></item></channel></rss>