gitlab-org--gitlab-foss/spec/routing
Robert Speicher 5c6cbfa6cb Merge branch 'atom-routes' into 'master'
Allow browsing branches that end with '.atom'

## What does this MR do?

1. Simplify the regex capture in the routing for the CommitsController
   to not exclude the '.atom' suffix. That's a perfectly valid git
   branch name, so we shouldn't blow up if we get it.
2. Because Rails now can't automatically detect the request format, add
   some code to do so in `ExtractPath` when there is no path. This means
   that, given branches 'foo' and 'foo.atom', the Atom feed for the
   former is unroutable. To fix this: don't do that! Give the branches
   different names!

## Why was this MR needed?

Creating a branch or tag name ending in '.atom' would cause some 500s on that repo.

## What are the relevant issue numbers?

Closes #21955. Related to !5994.

See merge request !6750
2016-10-11 14:04:31 +00:00
..
admin_routing_spec.rb Clean up unused routes 2016-07-26 12:06:42 +02:00
notifications_routing_spec.rb Updated rspec to rspec 3.x syntax 2015-02-12 19:17:35 +01:00
project_routing_spec.rb Allow browsing branches that end with '.atom' 2016-10-11 13:31:12 +01:00
routing_spec.rb Catch any undefined API routing and return 400 Bad Request 2016-10-10 16:32:32 +03:00