After mojo update /latest/configuration API call no longer works and gives page not found

RESOLVED FIXED

Status

()

enhancement
RESOLVED FIXED
7 months ago
7 months ago

People

(Reporter: dkl, Assigned: dkl)

Tracking

Staging

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

45 bytes, text/x-github-pull-request
Details | Review
(Assignee)

Description

7 months ago
In the old Apache world of htaccess, /latest/configuration would rewwrite to /bzapi/configuration

RewriteRule ^(?:latest|1\.2|1\.3)/(.*)$ extensions/BzAPI/bin/rest.cgi/$1 [NE]
RewriteRule ^bzapi/(.*)$ extensions/BzAPI/bin/rest.cgi/$1 [NE]

With the mojo update that /latest prefix no longer works.

$r->any('/extensions/BzAPI/bin/rest.cgi/*PATH_INFO')->to('CGI#bzapi_cgi');
$r->any('/bzapi/*PATH_INFO')->to('CGI#bzapi_cgi');

Need to add:

$r->any('/latest/*PATH_INFO')->to('CGI#bzapi_cgi');

and this should work again.
How annoying. It turned out I checked for /1.2/ and /1.3/ but not /latest/
(Nobody uses /1.2/ or /1.3/)

I think this helps my argument for all routes being in the same file though.
(Assignee)

Comment 2

7 months ago
Posted file GitHub Pull Request
(Assignee)

Comment 3

7 months ago
Merged to master.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.