GET /published/ route is inconsistent when specifying invalid parameters

[dcermak]

Issue Description

The GET /published/ route is relatively inconsistent when one specifies invalid parameters.

For example osc api /published/Virtualization:vagrant/ succeeds and osc api /published/Virtualization:vagrant:invalid/ is rejected with a 404. But, once you get into subdirectories, this no longer applies as osc api /published/Virtualization:vagrant/openSUSE_Tumbleweed results in a list of directories, but osc api /published/Virtualization:vagrant/this_does_not_exist just gives me an empty directory.

Expected Result

Specifying invalid parameters should either result in a 404 for all parameters or none of them.

Further Information

• tested against build.opensuse.org

[dcermak]

I've realized that it gets even more inconsistent once you start adding more path entries:

$ osc api /published/Virtualization:vagrant/this_does_not_exist
<directory>
</directory>
$ osc api /published/Virtualization:vagrant/this_does_not_exist/foo
<directory>
</directory>
$ osc api /published/Virtualization:vagrant/this_does_not_exist/foo/bar
Server returned an error: HTTP Error 404: no such file
no such file
$ osc api /published/Virtualization:vagrant/this_does_not_exist/foo/bar/baz
Server returned an error: HTTP Error 404: Not Found

I would suggest to start throwing 404s immediately, as the current behavior makes wrapping the API rather awkward.

[dcermak]

@danidoni afaik these routes go directly to the backend, so I guess that this is something for @mlschroe?

[danidoni]

@danidoni afaik these routes go directly to the backend, so I guess that this is something for @mlschroe?

Ouch, true. Changing