[quickthrower2]

Ugly yes, over engineering? no it's what you would have done in PHP in the 90's. Doing the URL thing would need more work (hello .htaccess). Anyway...

Good points: It is semantically correct and self documenting. There is no resource called 300 nested under a resource called 200 so lets not pretend there is. The query string seems perfect for the job of providing size parameters. You can then extend this interface to take other factors you want to affect the image, and keep it backwards compatible. Function over form.

[jeremy_wiebe]

Add to this the fact that you don’t have to memorize which order the “parameters” go.

Is it `/width/height` or `/height/width`?

To me this is very similar to languages that use names parameters vs positional.