Summary:	ASTERISK-26298: ari: Swagger resources.json does not acknowledge http prefix as configured in http.conf
Reporter:	Dan Jenkins (danjenkins)	Labels:
Date Opened:	2016-08-16 04:38:55	Date Closed:
Priority:	Major	Regression?	No
Status:	Open/New	Components:	Resources/res_ari
Versions:	13.10.0	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:	( 0) patch
Description:	When giving a http prefix in http.conf, this prefixes all http routes successfully. I can go to /a-http-prefix-added-to-conf/ari/api-docs/resources.json And that gives me back the correct json file - great news. We can see in the asterisk console the correct info too Enabled URI's: /a-http-prefix-added-to-conf/httpstatus => Asterisk HTTP General Status /a-http-prefix-added-to-conf/phoneprov/... => Asterisk HTTP Phone Provisioning Tool /a-http-prefix-added-to-conf/static/... => Asterisk HTTP Static Delivery /a-http-prefix-added-to-conf/ari/... => Asterisk RESTful API /a-http-prefix-added-to-conf/ws => Asterisk HTTP WebSocket However, resources.json gives back an incorrect base bath. "basePath":"http://<address>:8000/ari" - it should be "basePath":"http://<address>:8000/a-http-prefix-added-to-conf/ari"
Comments:	By: Asterisk Team (asteriskteam) 2016-08-16 04:38:55.691-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Torrey Searle (tsearle) 2016-08-17 08:09:30.478-0500 here is a patch that fixes the issue