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 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.

-Andrew

This tool is great! Add me to the list of those requesting an authorization feature.

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?

Bob

Hi Josh - In our case, we use Windows Integrated Authentication always. Never Basic.

Bob

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.

and another vote. Very surprising they hadn't anticipated security on development sites in advance did they not do any user experience testing.

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].

I also need this feature.

I use .htaccess that my provider allows me to setup.

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:

1. Install and run Firefox
2. Install the Firebug addon for Firefox
3. Install the BrowserLab for Firebug Addon
4. Select Tools -> BrowserLab for Firebug -> Options
5. Select “Allow read access” and press “OK”

Once the setup is complete you just:

1. Navigate to a site that requires authentication and enter your credentials
2. Navigate within the site to the page you want to preview
   
3. Select Tools -> Adobe BrowserLab for Firebug -> Preview Local Source

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/

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