GET on Atom feed (artifactname.ext;entry) produces a 405 Method Not Allow error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Atom
  • Labels:
    None
  • User impact:
    High
  • Similar Issues:
    None

Description

Atom feed for at artifact doesn't work. The ;entry addition causes the error (nothing in the log). The ;history path param works fine.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment -

After giving it another thought, I've raised the priority to critical - I cannot fetch artifact's metadata, and it will be needed for proper local cache handling.

Show
Andrew Perepelytsya added a comment - After giving it another thought, I've raised the priority to critical - I cannot fetch artifact's metadata, and it will be needed for proper local cache handling.
Hide
Permalink
Andrew Perepelytsya added a comment -

In fact, there was an error in Dan't commit log. One should append ;atom, not ;entry:

http://localhost:8080/api/registry/Default%20Workspace/hello-config.xml;atom

Question is then - should we instead return HTTP 501 Not Implemented for unknown representations instead of 405? (will rename an issue then)

Show
Andrew Perepelytsya added a comment - In fact, there was an error in Dan't commit log. One should append ;atom, not ;entry: http://localhost:8080/api/registry/Default%20Workspace/hello-config.xml;atom Question is then - should we instead return HTTP 501 Not Implemented for unknown representations instead of 405? (will rename an issue then)
Hide
Permalink
Dan Diephouse added a comment -

Closing since it was a usage issue.

Show
Dan Diephouse added a comment - Closing since it was a usage issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: