Home/ Questions/Q 7196765
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T20:50:25+00:00

Example 1: http://www.example.com/image/logo.png http://www.example.com/images/logo.png Example 2: http://www.example.com/user/johndoe http://www.example.com/users/johndoe Especially if you use the Url

  • 0

Example 1:

http://www.example.com/image/logo.png
http://www.example.com/images/logo.png

Example 2:

http://www.example.com/user/johndoe
http://www.example.com/users/johndoe

Especially if you use the Url as REST API. (Example 2)

Which one is recommended and why?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For REST, i mainly use the plural form to indicate a path to the resource. But you also have to take the Cacheablility, Frequency of Change and the Mutability of the Resource. In my case, collections of the resource is mainly the case, so i had used the plural form.

    The reason for this is that for example:

    http://www.example.com/users/johndoe

    will serve the URI to GET the user johndoe which belongs to your collection of users.

    http://www.example.com/users

    will be used as the URI to GET all users and can be easily be used on query url like:

    http://www.example.com/users?limit=5

    creating a new user will still use the same URL then using POST & passing the parameters:

    http://www.example.com/users

    for refs you may want to check the Oreilly book RESTful Web Services Cookbook

    • 0