title: Spray: Bringing RequestContext in scope results in timeout
body: <p>Hi scala and spray people!</p>
  
  <p>I have a small annoying issue with extracting the HTTP 'Accept' header from the <code>RequestContext</code> and matching on it. On a normal route like so:</p>
  
  <pre><code>get {
    respondWithMediaType(`text/plain`) {
      complete ( "Hello World!" )
    }
  }
  </code></pre>
  
  <p>It works like a charm. But whenever I bring the context into scope like so (as suggested in <a href="http://spray.io/documentation/1.1-SNAPSHOT/spray-routing/advanced-topics/understanding-dsl-structure/" rel="nofollow">the documentation for directives</a>):</p>
  
  <pre><code>get { context =&gt; {
    respondWithMediaType(`text/plain`) {
      complete ( "Hello World!" )
    }
  } }
  </code></pre>
  
  <p>The result becomes the following error message:</p>
  
  <pre><code>The server was not able to produce a timely response to your request.
  </code></pre>
  
  <p>I am fairly new to Spray, but it looks really odd to me that bringing an (otherwise implicit) object into scope can have such a weird sideeffect. Does any of you have a clue on what is going on?</p>