chromeipass: "Auto fill HTTP Auth dialogs and send them" option doesn't seem to work

[CoooolRaoul]

The option "settings" -> "general" -> "Auto fill HTTP Auth dialogs and send them" seem to have absolutely no effect for me. Is there somewhere an explanation how it's supposed to work to help to find how what I'm not doing correctly?

[pfn]

They automatically get sent to server without a dialog popping up

On Tue, Dec 27, 2016, 11:44 PM CoooolRaoul notifications@github.com wrote:

The option "settings" -> "general" -> "Auto fill HTTP Auth dialogs and send them" seem to have absolutely no effect for me. Is there somewhere an explanation how it's supposed to work to help to find how what I'm not doing correctly?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pfn/passifox/issues/581, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfQxUJsdibobUqJuGm7IjwVXFryBUUIks5rMhNugaJpZM4LWvGZ .

[CoooolRaoul]

Then it doesn't works (for me at least): I'm still getting the pop-ups (maybe because the url doesn't match the entry, I'm going to investigate further)

[pfn]

If it doesn't work then the credentials are are wrong or the entry does not match. You will get a pop-up notification from keepass when credentials are sent

On Wed, Dec 28, 2016, 9:06 PM CoooolRaoul notifications@github.com wrote:

Then it doesn't works (for me at least): I'm still getting the pop-ups (maybe because the url doesn't match the entry, I'm going to investigate further)

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/pfn/passifox/issues/581#issuecomment-269582483, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfQxY8aXxFWE21G4SnEHBEN1z_IOIK3ks5rMz-3gaJpZM4LWvGZ .

[CoooolRaoul]

It could be useful to have a kind of "debug mode" option to enable receiving nformational message in the situation where authentication request is detected and that no matching entry is returned by KeePassHTTP. This could be very helpful to analyze what's going on under the hoods in those cases (even better if KeePassHTTP itself could integrate a verbose mode of each request it is processing, maybe it's already exists ?)

[CoooolRaoul]

It worked after fixing the "url" field in the keypass database entry Anyway (unless already been asked) maybe you should think about implementing a "debug" or "trace" option, could be really useful I guess.

[bilogic]

@CoooolRaoul how did you fix the "url" field? thank you

[CoooolRaoul]

@CoooolRaoul how did you fix the "url" field? thank you

Unfortunately, it's been two years and and don't remember what I did exactly. You may try to reduce the URL field of the Keepass entry supposed to match to its shortest prefix ("http://.com", removing whatever is after this)

[bilogic]

I got it too, just make URL the shortest prefix in Keepass e.g. http://example.com for logging in to http://example.com/login. I was confused as my Keepass is configured to pop up balloon tips whenever it is queried, however HTTP auth does not trigger any pop ups.