Correct requests to api.perma.cc that don't specify a route

[sabzo]

No description provided.

[codecov]

Codecov Report

Merging #3174 (d295c2e) into develop (20a824d) will increase coverage by 0.00%.
The diff coverage is 66.66%.

@@           Coverage Diff            @@
##           develop    #3174   +/-   ##
========================================
  Coverage    84.22%   84.22%           
========================================
  Files           52       52           
  Lines         5591     5592    +1     
========================================
+ Hits          4709     4710    +1     
  Misses         882      882           

Impacted Files	Coverage Δ
perma_web/api/urls.py	78.94% <ø> (+3.94%)	⬆️
perma_web/api/views.py	85.46% <66.66%> (-0.29%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[sabzo]

This ticket is ready to review :)

[sabzo]

Are there unit tests to write for this feature?

[bensteinberg]

These redirects are already working correctly, I think, or at least they do for me. What symptom or issue are you seeing that this PR addresses?

[sabzo]

This PR tries to address the scenario where If a developer accidentally curl -X POST https://api.perma.cc/ (instead of POSTing to one of the actual API endpoints), our app tries to send them an HTML error page, but the error page itself throws a 500 error, because it only works for perma.cc routes, not api.perma.cc routes.

[bensteinberg]

LGTM. Thanks!