Description of problem: Currently the catalog responds to URLs that are id={value} or searchField[1..n]={value[1..n]} and other computer query formated URLs this while functional isn't particularly friendly. The catalog should also support a few human friendly variations of URL: hardware.redhat.com/[rhelX|RHELX] hardware.redhat.com/[rhemrg|RHEMRG|mrg|MRG] hardware.redhat.com/[vendor|variations] hardware.redhat.com/[vendor|variations]/[make|variations] Variations should be a best guess match. Supporting combinations of RH and vendor information (eg. hardware.redhat.com/rhel6/dell) is not required at this time but should be expected as a follow-on feature. Also supporting determining make and model (eg. hardware.redhat.com/poweredge or hardware.redhat.com/dl585) are not required at this time but again will be a follow-on feature. Expected results: hardware.redhat.com/rhel6 should respond the same as: https://hardware.redhat.com/list.cgi?version=6 hardware.redhat.com/{vendor} should respond the same as: vendor=vendor+version=6,5 sorted by version then make/model.
Created attachment 527837 [details] patch for friendly url
Created attachment 527839 [details] .htaccess file used to rewrite url use apache's urlrewrite module to rewrite url
Created attachment 528687 [details] new htaccess file support ending slash, and vendor's name includes digits
Will this last update break the current cert id support? That is... hardware.redhat.com/12345 goes to hardware.redhat.com/show.cgi?id=12345
(In reply to comment #9) > Will this last update break the current cert id support? That is... > > hardware.redhat.com/12345 goes to hardware.redhat.com/show.cgi?id=12345 no, it won't hurt our exist cert id support, because Apache urlrewrite module will first process urlrewrite rules in VirtualHost context, that is rewrite our hardware.redhat.com/123 to hardware.redhat.com/show.cgi?id=12345, and there is a flag L, this means it is the last rule if the rule's condition has been met, and will not process .htaccess in per directory level.
Are changes needed in the apache configs to support htaccess?
Closing as this work with 3a.