Slashdot Mirror
White List URL Browser Selector?
malcomvetter asks: "OK, so I'm stuck working in a Microsoft environment. My preference is Firefox for the external 'untrusted' web content out there and our internal 'trusted' web apps require IE, but rather than pick one browser over the other as 'default' I came up with this idea: I want a tool that gets installed as my default browser in Windows, and all URL strings that Windows passes to it can then be simply regex'ed for domain and then routed (re-passed) appropriately. Hence, having the ability to allow admins to maintain a white-list of 'trusted' IE sites (or [insert browser here] sites) and those URLs are passed to IE, all others defaulting to (in my preference) Firefox. And when I thought about it, I was surprised that I hadn't heard of an existing tool to do that. I have used the Firfox extension for 'open in IE', but I'd like a tool that I can configure and forget about. Has anyone seen such an app? Would it be an extremely hard thing to build?"
As a developer who has been forced to use IE in applications in the past, I can say that the Microsoft "Web Browser Control" is basically the IE rendering engine encapsulated in an OCX. Its extremely simple to include this rendering engine in any windows application. I'd imagine it would be trivial to write a firefox extension* that parses the URL and loads an IE control in a new "empty" frame if the URL is on the white list, then passes the URL to the control to be handled.
We might be able to use one of the tabs modification extensions that already exists as a starting point for usurping default firefox tab behavior, and I'd be interested in helping with a project of this nature.
*I have no experience writing firefox plugins, but the variety that are available show that the architecture is fairly extensible.
A much simpler, but much less integrated approach would be to use a "URL Launcher." Basically, a program that determines if the domain from the URL entered is "IE-only" or not and fires the appropriate browser accordingly. This would be a 5-10 minute project for a good developer, but would be effective.
Josh.
How many roads must a man walk down? 42.
It's still in beta at the moment, but I expect a final version to be out in the not too distant future.
Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
Get the source for the View in IE extension for Firefox/Mozilla. Add to that a list and then when you go to a page on that list it automatically launches it in IE. That would certainly not be hard to build.
For some reason at time of posting, the whole mozdev.org site seems to be down, but otherwise I would have gotten the link to the View in IE extension.
I am seeing alot of people saying that nothing exists and why don't you use browser/tool/etc X, instead of offering useful advice.
No, this tool would not be too hard to write. I have written a protocol handler for windows (years ago). All it takes is a registry entry to point windows to the program, and a program that processes it's command line arguments through a list of greps with actions (hard coded or stored in a config file if you like). The only difficult part is that once in the browser, you can't easily intercept the selected links and check every one.
I think a rudimentry attempt at such a program could be done in 30-40 lines of C code, or with a perl script closer to 10 lines or less. All you have to do is find out what the registry entry for the protocol handler is, and change it. I found it by digging through the registry with regedit, but I suspect that the MSDN knowlege base probably has an article on it.
There is no need to browbeat someone over such a request because it doesn't make sense to us. The true measure of a utility such as that is that someone wants to use it, and someone (probably the same person) is willing to write it -- if it doesn't already exist.
This is what we call the pragmatic approach, eh?
More Caffeine. NOW