URL Masking for ThingWorx REST Service

Forum|Forum|10 years ago
September 21, 2015
2 replies
9155 views

As per my understanding, ThingWorx services can be exposed as REST, but URI would be /Thing/ThingName/Services/ServiceName.

Exposing services in this way could expose business data/entities as well.

My question is that, can we MASK thingworx service URL in a custom or a REST way i.e. /resources ?

Connectivity

P

paic

1-Visitor

I actually tried this one time with a URL Rewrite called 'Tuckey' but I couldn't make it work, so it may not be possible. But that is what I would recommend. 'Theoretically' it could work, but when I tried it, I couldn't make it work, although I didn't go very deep.

E

esirohi

Author

1-Visitor

Thanks for replying.

As you mentioned that you tried URL Rewriting, what error/issues you encountered? I will also try out at my end.

I think, the changes can be made in domain setup (probably CNAME or URL Forwarding/Redirection) which can redirect a domain to another URL.

P

paic

1-Visitor

It's been a rather long time so I don't remember.

C

CK_14383687

7-Bedrock

This simple nginx configuration works for me:

worker_processes  1;

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

    sendfile        on;
    keepalive_timeout  65;

    server {
        listen       80;
        server_name  localhost;

          location / {
               proxy_pass       http://localhost:8080;
               proxy_set_header Host      $host;
               proxy_set_header X-Real-IP $remote_addr;
          }

          location /service {
               proxy_pass http://localhost:8080/Thingworx/Things/Neuron/ServiceDefinitions/GetConfigurationTables;
               proxy_set_header Host $host;
               proxy_set_header X-Real-IP $remote_addr;
          }
          
     }
}