FrameMaker using port 80 for non-http traffic?

Forum|Forum|8 years ago
August 29, 2017
1 reply
288 views

We have a proxy that intercepts all port 80 traffic, and if non-http traffic is sent over port 80 the proxy rejects the traffic.

Does FrameMaker use port 80 for non-http traffic, and if so, how can we change that?#

Thanks.

This topic has been closed for replies.

Jeff_Coatsworth

Community Expert

The Adobe licensing model probably uses some "phone-home" mechanism, but there are plenty of installations (governments, military contractors, banks, etc.) where internet connections are non-existent. What issue are you running into that would cause you to care about this?

S

stevem34492868Author

Participant

Reported issue is that FrameMaker does not connect on "websockets port 80" when the proxy is intercepting... note the proxy intercepts all port 80 traffic and only port 80.

If traffic is sent on port 80 without appropriate HTTP headers, it will be blocked/rejected by the proxy server.

When the proxy is physically powered off, then websockets port 80 connects successfully.

Therefore, I can only assume at this point that FrameMaker is using standard http port 80 for non-http traffic.... can you confirm this ?

Jeff_Coatsworth

Community Expert

You're getting a message in FM that it can't connect? Never heard that one before. You'll need to contact Adobe Support - this is just a user to user forum here.

Remix with Firefly Community Gallery

Thousands of free creations to fall in love with and remix in Firefly.

Explore now

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded