Skip to content

Two HTTPS proxies with different usernames and passwords but identical hostnames and ports are in conflict with each other #254

@proxy19C

Description

@proxy19C

I have an HTTPS Proxy servers that acts as a relay and it changes destination based on logged in users. My goal is to be able to change authenticated user by having two entries in FoxyProxy. However, it seems like that there's a conflict.

Image

If you end up having a configuration like this on my screenshot (credentials obviously redacted for privacy), the extension seems to not allow me to change between the two properly.

Image

Despite me clicking on "https to spain" my requests are still going through "https to switzerland", and if I click on "https to switzerland" the UI shows that it was successfully selected, however once I reload the page and check the selected proxy it goes back to "https to spain".

It seems like changing hostname to something that would contain a new symbol, for exampel a "#" is a workaround the issue, so I have to add "#" to the end of the hostname of the proxy that I don't want to be selected. Once I change the hostname URL to proxy.example.org# of "https to switzerland" and save the settings, the UI acts normally and the extension itself works fine. However, obviously, a URL containing a "#" is invalid and if I try to use "https to switzerland" it won't work as the domain is incorrect, but at least now clicking the switzerland proxy option works correctly and it is actually being selected.

My assumption is that for some reason those entries don't have some unique IDs attached to them and/or for some reason selecting a proxy in the list is based on the hostnames? Otherwise I don't really know why adding a minimal change to the hostname sort of fixes the issue.

I'm unfortunately completely unfamiliar with the project nor do I really have much time to fix this, but hopefully someone picks up on the issue and figures it out. It would be extremely appreciated! I'll be happy to provide more details if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions