All our dev sites are password protected, so all I get is error 401, not authorized.
Any plans on adding the ability to provide login details so that protected servers can be checked to?
Thanks for your interest in BrowserLab.
The FAQ states that BrowserLab does not currently support HTTP authentication under the Known Issues section. I'm unable to comment on any unannounced features or enhancements, however I'm happy to pass along your request to the product team.
Please pass along this extra vote for supporting HTTP authentication. When I'm developing a website for a client, I always keep the development site password protected -- actually, I keep all client files password protected.
Granted, I can remove the authentication requirement for when I want to test pages, but that kind of defeats the purpose of using the authentication in the first place.
Add me to the list of folks requesting support for http authorization. BrowserLab is a fantastic service, but I'm going to require access to password protected servers in order for it to be really useful.
Add me to the list of people who would not find this service very useful without Authentication support.
Most of the sites I develop are "Extranet" sites which require logging in to access. I became very excited upon trying out this service, only to realize that it would be useless for 80-90% of the sites I develop.
Thanks, but it is not clear to me that "BrowserSeal" is better. It seems as if it is limited to rendering web pages only on browsers that run on the current OS platform - it's not cross platform, which for my purposes severely limits its value. Correct me if I am mistaken. We are always finding rendering differences and nuances between, for example, Safari on the Mac and Safari on the PC. How would BrowserSeal help us evaluate those differences?
You are correct in that BrowserSeal is an application running on Windows and it only supports browsers running on this OS. The rendering differences between Mac and Windows versions of Safari are very, very rare and subtle. So yes, this approach has some disadvantages, but the advantages are huge - having all these browsers at hand allows you to actually debug the issue.
Not to mention that BrowserSeal is faster and can work with local and password protected sites.
I find myself using another service that supports authentication [Solicitation Removed] more
and more often, except when I'm on Mac - in that case BrowserLab is still the best service, [Solicitation Removed].
Yes, please add a way to view authentication autorization required pages. I am able to make a pdf from any of my website's password required pages in Acrobat 9 Pro. It puts up a user/password window before building the pdf. I don't see why that couldn't be the case in browserlab as well.
With the recent release of Adobe BrowserLab for Firebug Addon for Firefox it is now possible to preview pages on sites that require authentication.
You first setup Firefox with Firebug and BrowserLab for Firebug Addon:
Once the setup is complete you just:
When Preview Local Source is selected BrowserLab will tunnel files through Firefox rather than getting them directly from the web. This means that any page that you can navigate to in Firefox can be previewed by BrowserLab in any of the browsers it supports.
You can get the BrowserLab for Firebug addon here: https://addons.mozilla.org/en-US/firefox/addon/231196/
Yeah, that Firebug add-on doesn't really work, you might want to look at it's awesome 2-star rating and all the comment complaints.
Bump this thread, and add me to the list of people who want to see an authentication feature added.
Seems ridiculous that it's not included already.... Many of the sites us developers want to preview are Dev or Staging sites, which are almost always behind a login...
We have read through those comment complaints and most of the low star votes are due to people saying it doesn't work on Debian or Ubuntu which we don't support. Most people using Mac or Windows have no problems with the add-on. If you're having issues with it, please start a new thread here on the forums, provide details on the issues you're having, and I'll be happy to help you out.
Anyone have an idea as to when or if this will be resolved? I too have a test site that's password protected with basic authentication and would love to test it in BrowserLab.
As for the Firefox extention, I don't want to install Firefox just for the purpose of using an addon to an addon so I can get the funtionality. Besides, is not having to install a bunch of browsers the reason why we're using BrowserLab in the first place?
Tools doesn't show Browserlab for Firebug upon install and restart? I've been able to give "Allow read access" but I can't seem to find how to actually launch the Browserlab from Firebug.
See here: http://cl.ly/image/3d401l1t3O31
and I don't see it when I open Firebug either??
What am I missing?
Using FF 17.0.1 on Mac 10.6.8
Europe, Middle East and Africa