Brackets seems not able to display extension lists via extension manager when under authenticated proxy environment

[core-ai-bot]

Issue by yohanChang
Monday Nov 14, 2016 at 10:48 GMT
Originally opened as adobe/brackets#12910

---

Prerequisites

• Can you reproduce the problem with Debug -> Reload Without Extensions?
• Did you perform a cursory search to see if your bug or enhancement is already reported?
• Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here

Description

It seems like there are some proxy issues left on Brackets.
Certainly, as long as we follow the guide from Troubleshooting document (https://github.com/adobe/brackets/wiki/Troubleshooting#-having-trouble-installing-extensions),
there was no problem to install extension under proxy setting no matter whether it is authenticated one or not.
But the problem actually aroused before any installation. When we just opened the extension manager, we couldn't see any extension lists inside extension manager.
Instead we saw a message, "unable to access the extension registry. Please try again later."
Could you please help me out finding a way to display lists on extension manager when the proxy setting is authenticated one (which is an usual condition on corporate proxy)?
Thank you for your support.

Steps to Reproduce

1. Change your network settings into proxy setting
   (I am not completely sure authentication matters, but we do have authenticated setting)
2. Open Brackets
3. Set your proxy setting prepared on brackets.json
4. Open Extension Manager by clicking the icon under Live Preview icon
5. Check whether lists are visible or not

Expected behavior: [What you expected to happen]
Display all the extension lists

Actual behavior: [What actually happened]
a message, "unable to access the extension registry. Please try again later."

Versions

OS : Windows 7 Professional K Service Pack 1
Brackets version number : Release 1.7 build 1.7.0-16898 (alf_localization_release_1.7 b0a363b71) build timestamp: Thu Sep 29 2016 15:34:31 GMT+0900

[core-ai-bot]

Comment by ficristo
Thursday Nov 17, 2016 at 19:13 GMT

---

Are you able to access this json?
https://s3.amazonaws.com/extend.brackets/registry.json

[core-ai-bot]

Comment by ficristo
Sunday Nov 20, 2016 at 08:21 GMT

---

There is some discussion of a relative problem here adobe/brackets#12898

[core-ai-bot]

Comment by yohanChang
Tuesday Nov 29, 2016 at 03:57 GMT

---

Thank you for the reply, and I want to apologize for the late response.
Yes, I am able to access the json file you mentioned with proxy environment with the authentication.

In my opinion, what causes the error was the ajax call without proxy authentication.
In function named downloadReigstry() on brackets/src/extensibility/ExtensionManager.js,
ajax call was invoked with the json file you mentioned above.
The ajax function was utilized without proxy information and I think this is where the error was occurred.

On the other hands, when installing extension, proxy environment is concerned and utilized if there's one.

If you don't mind, could you please take a look at the function downloadRegistry() (brackets/src/extensibility/ExtensionManager.js)?

Thank you.

[core-ai-bot]

Comment by ficristo
Saturday Dec 03, 2016 at 16:03 GMT

---

If you can run from source could you try this PR adobe/brackets#12933 ?

[core-ai-bot]

Comment by yohanChang
Monday Dec 05, 2016 at 04:25 GMT

---

Thank you for the reply.
Yes, I can run Brackets from the source, so I can try that PR #12933 .

However, by checking the commits on that PR, I am not really confident that this issue will be fixed since there was no specific changes like handling proxy part on downloadRegistry() in ExtensionManager.js.
Still, I will check that PR until the end of this week and report the outcome on this post.

Thank you.