Trouble with "Authentication Required" pages.

[MrXxx]

When attempting to access a page contained in a restricted access
folder, requiring login, an "Authentication Required" window opens,
but the form most often does not load so users can log in. It has
loaded once, but not with several other attempts.

It doesn't seem to matter which speed is chosen.

Firefox 3.6.12
Mac OS X 10.6.4

I am also running Snitch, and have authenticated all network
connections for Sloppy "Forever" (unless there might be some others I
haven't yet seen the screens for ~ but I've waited up to a full 60
seconds and the window Authentication window is still blank).

Is it just taking a long time to load?

[Richard Dallaway]

Hi - thanks for this report.

I've now seen around four posts relating to authentication-style
problems, so clearly something's not right somewhere.

Do you know if this is authentication handled by the browser (e.g.,
BASIC authentication or similar), or is it authentication handled by
the web application (i.e., it's just a regular web page)?

Is it a publicly visible site I can hit to try to reproduce the
problem?

If you wanted to create screen shots and describe the issue, I'd
certainly investigate. Here's the link for how for where you can
record details: http://code.google.com/p/sloppy/issues/list

Thanks
Richard

[MrXxx]

It's normally a browser dialogue (yes, basic authentication). The
folder itself where the page resides is protected.

When I try to access the page with Sloppy, the application displays a
window. The one time the Sloppy dialogue actually showed properly, I
had already turned off the protection for a while, and tested with
Sloppy that way, so I didn't need it by the time the Sloppy dialogue
did work correctly. That time, I clicked cancel, but the proxy still
attempted connection, and the normal browser dialogue appeared so I
could have gotten in anyway. That makes me wonder if the Sloppy
dialogue is even necessary. (?)

The problem when the alert window doesn't display correctly though, is
that the only way to get out of it is to force quit Sloppy, so the
connection attempt is aborted.

Other than the fact that the folder requires login, it is a public
page. Address is http://www.airweavers.com/chris_richard/Fire

[Richard Dallaway]

I've updated Sloppy to (hopefully) resolve this issue.

If you launch Sloppy, and check the About box it should say "Sloppy/
1.1.127". If not, head over to http://dallaway.com/sloppy/ and launch
it from there.

Please let me know if that works for you.

Richard

On Nov 9, 2:03 am, MrXxx <chrisrichar...@gmail.com> wrote:
> It's normally a browser dialogue (yes, basic authentication). The
> folder itself where the page resides is protected.
>
> When I try to access the page with Sloppy, the application displays a
> window. The one time the Sloppy dialogue actually showed properly, I
> had already turned off the protection for a while, and tested with
> Sloppy that way, so I didn't need it by the time the Sloppy dialogue
> did work correctly. That time, I clicked cancel, but the proxy still
> attempted connection, and the normal browser dialogue appeared so I
> could have gotten in anyway. That makes me wonder if the Sloppy
> dialogue is even necessary. (?)
>
> The problem when the alert window doesn't display correctly though, is
> that the only way to get out of it is to force quit Sloppy, so the
> connection attempt is aborted.
>
> Other than the fact that the folder requires login, it is a public

> page. Address ishttp://www.airweavers.com/chris_richard/Fire

[MrXxx]

That did it Richard.

Just a note though, that users using this feature should know:

Now, instead of opening a Sloppy dialogue first, the site dialogue
pops down first, then a Sloppy dialogue. I'm not sure why that is, but
my guess is that the browser is being directly sent to the site first,
then redirected through Sloppy proxy?

In any event, now I get two logins the first time I log in. The first
is the normal site login, the second that appears is a Sloppy
dialogue. I'm assuming I would have to log into both? That's what I
did anyway, and it worked, but I am assuming if I canceled the Sloppy
login, the browser would either get a forbidden error or open the
direct address (bypass the proxy), but I'm not sure which.

I quit Firefox and tried it again to see what would happen if I
canceled the Sloppy dialogue, but this time I only got the main site's
dialogue, no Sloppy login. I'm guessing this is because there is a
cookie or something still connected on the proxy?

However it works, it does work, but users may want to know that they
will see both logins the first time they connect.

On Nov 9, 5:30 am, Richard Dallaway <dalla...@gmail.com> wrote:
> I've updated Sloppy to (hopefully) resolve this issue.
>
> If you launch Sloppy, and check the About box it should say "Sloppy/

> 1.1.127".  If not, head over tohttp://dallaway.com/sloppy/and launch