API over the Internet: use port 80 or custom (e.g. 8080)?

Question

API over the Internet: use port 80 or custom (e.g. 8080)?

We have a web service that will not be available to users. That is, only by:

Javascript from browser
Mobile apps (iPhone and Android)
Other servers

The question is: is it ok to use some kind of user port for this (e.g. 8080), or should we use only 80 ports (so the URL will not contain the port number).

What are the pros and cons? Are there any reasons why the option with custom ports is unacceptable?

+3

java http

Eugene retunsky Apr 19 '12 at 17:15

source share

3 answers

, , , .

+1

user1309663 19 . '12 17:42

One thing you could do is set up your own firewall or router to route traffic addressed to a specific URL to a custom port configured on your application server, so that only requests specific to the service being launched get into it.

+1

Matt moran Apr 20 '12 at 7:14

source share

Perception · Accepted Answer · 2012-04-19T17:38:18+0000

, , " ", 8080. , - 8080. , - , 80 .

, . 8080 , - .

API over the Internet: use port 80 or custom (e.g. 8080)?

More articles: