Fix the weridness in the DELL older IDRAC like version 6 so you can open the JAVA link it provides in chrome
Total ratings
4.62
(Rating count:
13)
Review summary
Pros
- Still working effectively with newer Java versions.
- Fixes issues with .jnlp file downloads for IDRAC.
- Saves time and effort accessing the DRAC.
- Positive user experience with seamless functionality.
- Users express gratitude towards the developer (Craig).
Cons
- Interferes with other download-related extensions.
- No instructions provided for setup or usage.
- Default behavior can lead to conflicts with file naming.
- May require additional configurations in Java settings.
Most mentioned
- Works well for its stated purpose.
- Interferes with extensions like DownThemAll.
- Users appreciate the developer's efforts.
- The extension is crucial for accessing DRAC.
Upgrade to see all 19 reviews
Recent reviews
Recent rating average:
4.00
All time rating average:
4.62
Upgrade to see all 19 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
Date | Author | Rating | Lang | Comment |
---|---|---|---|---|
2024-04-18 | Ákos Szabó | en | 2024, and still working! | |
2023-07-03 | Wilson Sour | Hi great work, just want to let you know that it is still working now in July 2023 with Java 8 update 251 with chrome extension. see below on how to fix it. https://www.youtube.com/watch?v=Rzvr0uLPhlk&t=198s | ||
2023-07-03 | Wilson Sour | en | Hi great work, just want to let you know that it is still working now in July 2023 with Java 8 update 251 with chrome extension. see below on how to fix it. https://www.youtube.com/watch?v=Rzvr0uLPhlk&t=198s | |
2022-01-23 | Dieter D | Still works like a charm, thanks a lot Craig! | ||
2022-01-23 | Dieter D | en | Still works like a charm, thanks a lot Craig! | |
2021-06-16 | R. Daneel Olivaw | Works well for its stated purpose, but at some point I noticed it intermittently interfering with other download-related extensions. Most specifically, at present it seems to interfere with extensions that rename/move files during/after download, such as DownThemAll which grabs link details for extended file naming options. It also completely prevents DTA (and others) from downloading to subfolders, which is likely the same root cause. While extensions are limited to using the profile's Downloads folder per Chrome security policy, there are no restrictions within that folder. I have successfully tested all functions mentioned here without this extension installed, so it seems this extension is the only cause of these problems and there are no secondary/compounding factors. To fix it: The extension either needs a more specific automatic filter/mechanism or, if the circumstances/API doesn't allow for an automatic/programmatic fix, then possibly just a manual whitelist, like a short list with buttons to add specific scopes, like "run on this domain" etc. and a default exit/ignore if the current site/IP/range/etc isn't on there. Looking at the code, it uses a simple regex filter of "^viewer\.jnlp" to ID files, which should be fine as most file names wouldn't contain that string, so I can only guess that the issue is that the extension running on every single download is causing conflicts, meaning it should be limited in some other way, like my suggested whitelist. For reference, the red error message seen on the Chrome extensions page (main list or single extension page) after a conflict: """ This extension failed to name the download "" because another extension (Fix IDRAC .jnlp file) determined a different filename "". """ | ||
2021-06-16 | R. Daneel Olivaw | en | Works well for its stated purpose, but at some point I noticed it intermittently interfering with other download-related extensions. Most specifically, at present it seems to interfere with extensions that rename/move files during/after download, such as DownThemAll which grabs link details for extended file naming options. It also completely prevents DTA (and others) from downloading to subfolders, which is likely the same root cause. While extensions are limited to using the profile's Downloads folder per Chrome security policy, there are no restrictions within that folder. I have successfully tested all functions mentioned here without this extension installed, so it seems this extension is the only cause of these problems and there are no secondary/compounding factors. To fix it: The extension either needs a more specific automatic filter/mechanism or, if the circumstances/API doesn't allow for an automatic/programmatic fix, then possibly just a manual whitelist, like a short list with buttons to add specific scopes, like "run on this domain" etc. and a default exit/ignore if the current site/IP/range/etc isn't on there. Looking at the code, it uses a simple regex filter of "^viewer\.jnlp" to ID files, which should be fine as most file names wouldn't contain that string, so I can only guess that the issue is that the extension running on every single download is causing conflicts, meaning it should be limited in some other way, like my suggested whitelist. For reference, the red error message seen on the Chrome extensions page (main list or single extension page) after a conflict: """ This extension failed to name the download "" because another extension (Fix IDRAC .jnlp file) determined a different filename "". """ | |
2021-02-14 | Vincent Wolsky | no instructions, added it to chrome, clicked launch virtual console on idrac page and it downloads that file and nothing happens. | ||
2021-02-14 | Vincent Wolsky | en | no instructions, added it to chrome, clicked launch virtual console on idrac page and it downloads that file and nothing happens. | |
2021-01-15 | Phillip De Rossi | Awesome mate, thank you! works great. :-D |
Upgrade to see all 19 reviews