Dreamweaver proxy issues

[fishwicksl89690049]

Application: DreamWeaver 18 (build 10136)

OS: Mac OSX 10.11.6

In our network environment we have an authenticated proxy server for all internet facing traffic, which doesn't pose a problem with any AdobeCC apps with the exception of Dreamweaver. Shortly after launching the DW application we noticed persistent dialog boxes requesting proxy authentication. Upon checking our proxy logs we see that it's trying to go to a "local" site (specifically: http://127.0.0.1:58896/socket.io/socket.io.js) so instead of rendering any sites locally it is trying to go via our proxy.

When the system proxy is disabled this is not a problem, so I tried adding 127.0.0.1 as a system proxy exception however the problem remained.

It appears then that DW for Mac does not honor the proxy exceptions defined in the system configuration.

Does anyone know of a workaround for this? Perhaps some location within the DW app that network proxy settings can be changed?

Thanks

Joel

[Preran]

Hi Joel,

Am checking with the team. Will get back to you as soon as I have a response.

Thanks,

Preran

[Niharika Jha]

Hi,

Do you have any files within the site currently open where they are referring to socket.io.js?

Regards,

Niharika Gupta

Adobe Dreamweaver

[fishwicksl89690049]

Hi Niharika

I am able to replicate the issue with any document open, including File - New - and creating a new blank document.

I'm not 100% sure, but I suspect it could be something related to the preview of the site within DW, from what I can see it looks like it hosts the website files on a random local port for preview.

[fishwicksl89690049]

Hi Niharika

Have you managed to discover anything on this issue as yet?

In addition to the persistent authentication dialogs in the application, it is also causing our proxy log files to grow large due to the flooding of errors.

Thanks

[Preran]

I have written to Niharika seeking an update to her response. If you are in a rush, feel free to get in touch with the tech support team directly using this link Contact Customer Care

[Preran · Accepted solution]

A quick update. The team has been able to reproduce this issue, and they have logged a bug for investigation for a fix in a future update.

Thanks,

Preran

[fishwicksl89690049]

Fantastic news, thanks for the update Preran.