Written by

Question Stefan Blank · May 18, 2018

REST service works only via VPN

Hi,
I created a REST service that works well if called via VPN,  for example the url http://192.168.10.60:57772/fm/status returns a JSON string as expected.
If I replace the ip 192.168.10.60 with the ip used for our public website nothing happens. If I remove the port :57772 the browser returns a 404 error page.
Do I have to use a different port or is this caused by the settings of our web server? (We are using Apache Web Server: Apache Cache_Server_Pages-Apache_Module/2016.1.0.656.0-1601.1554d)  


Thanks in advance!

Comments

Robert Cemper · May 18, 2018

If you remove  port 57772, then HTTP uses default port  80
At that server  your "page" is unknown and you get back 404

I suggest checking the firewalls on your way starting with the server of your public website. to let 57772 in

my 2ct.

0
Robert Cemper  May 18, 2018 to Robert Cemper

my assumption; you have installed CSP Gateway on your public website 

0
Stefan Blank  May 24, 2018 to Robert Cemper

Hi Robert,
many thanks for your answer. The url without port 57772 and with port 80 result in a 404 error page. But I must correct myself: we are using IIS not Apache (the Apache module version is only shown in the Cachè-CSP-Gateway-Management page).
I have read here in another post (https://community.intersystems.com/post/fixedcall-rest-service-csp-gate…) that IIS needs an additional file type mapping (*) for REST services. In our system under "Default Web Site" there are for CSPms configured the types csp and cls only. Before I add a wildcard * mapping: are there any considerations about security or system behavior or even system breakdown? (I'm not experienced in IIS configuration...)

Thanks,

Stefan

0
Robert Cemper  May 24, 2018 to Stefan Blank

Sorry, IIS is also not my world.

0