Home/ Questions/Q 6542853
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T11:16:36+00:00

I’m creating a RESTful web service that allows me to import documents by name.

  • 0

I’m creating a RESTful web service that allows me to import documents by name. I would import a document using a path like this:

/documents/frequently-asked-questions

If the document doesn’t already exist, it would create a new one; otherwise, it would simply overwrite the existing document.

The question I have is whether this is a wrongheaded endpoint for a RESTful service. Normally I’d use POSTs for creates and PUTs for updates. Here it’s not known in advance whether the document already exists. If this is reasonable, then what’s the best HTTP method? If it’s not correct, then what’s a better approach?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The HTTP 1.1 specification says for POST:

    9.5 POST

    The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.

    And for PUT:

    9.6 PUT

    The PUT method requests that the enclosed entity be stored under the supplied Request-URI.

    Given that, and the fact that PUT is idempotent and POST is not, PUT seems the logical choice here for both your create and update.

    Source:
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.2

    • 0