title: REST convention for resources with slashes
body: <p>Is there any REST convention for handleling resources with slashes?</p>
  
  <p>For instance, let's say a normal REST resource works like this:</p>
  
  <ul>
  <li><code>/ice cream/chocolate</code> - returns the
  ingredients of chocolate ice cream</li>
  <li><code>/ice cream/rocky road</code> - returns the
  ingredients of rocky road ice cream</li>
  <li><code>/ice cream/strawberry/banana</code> -
  returns the stawberry banana
  ingredients</li>
  </ul>
  
  <p>Only <code>/ice cream/strawbery/banana</code> doesn't quite work because that looks like a resource for strawberry with a subcomponent of banana.... not quite what we're going for.</p>
  
  <p>When you try to escape the <code>'/'</code> with <code>'%2F'</code> many web servers (including glassfish and apache) block this by default as a possible security violation.  There are server overrides, but then I'd need to get a different team involved... I'd rather just handle it myself.</p>
  
  <p>So what is one with a RESTful mind to do?  I can't very well prevent someone from naming their ice cream 'strawberry/banana'.  </p>
  
  <p>I was thinking of using some custom escape sequence like <code>stawberry*slash*banana</code> and then force any display component to do the conversion on their end, but I thought others must have faced similar issues, so why not ask for the best practice (or at least for some ideas that make sense)?</p>