Query Parameters in REST

Question

I'm writing a RESTful webservice for Google AppEngine. The webservice provides a Java serialized object representation of a product based on a barcode and format. I was wondering what design methodology (if any) is preferred by RESTful design among the following options:

Option - 1:

 /product?barcode=1234&format=ean_13

Option - 2:

/product/1234?format=ean_13

Option - 3:

/product/ean_13/1234

I found quite a few references on REST on SO but nothing that addresses the use of query parameters to identify a representation.

My own understanding is that it shouldn't make a difference since the server is stateless in all three situations but I'm not sure.

Darrel Miller · Accepted Answer · 2012-03-16 13:42:16Z

3

It doesn't make a difference to REST those are just three different identifiers.

From a practical HTTP perspective, there are many deployed intermediary caches that will not cache representations that have query parameters. So if want to cache these representations in public caches then maybe option 3 is better.

answered Mar 16, 2012 at 13:42

Darrel Miller

143k32 gold badges202 silver badges246 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Query Parameters in REST

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related