cAPI on port other than 80

More
1 month 12 hours ago #285 by carvalhorj
cAPI on port other than 80 was created by carvalhorj
Hello all, I am in need of help. Situation is the following

I have a joomla prodution installation that runs on an apache port other than 80. It runs on 80 and some other specific port.

cAPI responds as expected but only on port 80, if I make a request on the other port it times out, thou all the other joomla instalation and components run ok.

Is this a bug or a feature?

how can i work around it other than using port 80?

Thanks

Ricardo

Please Log in or Create an account to join the conversation.

More
1 month 11 hours ago #286 by steve.tsiopanos
Replied by steve.tsiopanos on topic cAPI on port other than 80
Hello Ricardo,

Do you have a live example which we can test confirm that your API access does not work on ports other than port 80 / 443.

Were you testing through the Swagger UI? If so I suspect the issue may be that cAPI currently does force other port 80 or 443 access within the Swagger UI view. This is something I can keep in mind for cAPI v2 as the entire built-in Swagger UI is being upgraded to the latest version.

Please Log in or Create an account to join the conversation.

More
1 month 10 hours ago #287 by carvalhorj
Replied by carvalhorj on topic cAPI on port other than 80
Totally right you are:

the address i am using is the following (domain removed because of being a public forum)
XXXXXXXXXX.com.br:7530/administrator/index.php?option=com_services&view=swaggerui

and the answer is

Can't read swagger JSON from XXXXXXXXXX.com.br:7530/api/v1/slim/swagger

Any way around this?

Please Log in or Create an account to join the conversation.

Newsletter

Cron Job Starts