Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Server Port Filtering in SteamUser #488

Closed
koftrciali opened this issue Aug 11, 2024 · 3 comments
Closed

Feature Request: Server Port Filtering in SteamUser #488

koftrciali opened this issue Aug 11, 2024 · 3 comments

Comments

@koftrciali
Copy link

Problem Statement

Some proxy providers, such as Thunderproxies, restrict access to all ports except 443 and 80. This limitation makes it challenging to establish connections through other ports.

Proposed Solution

Introduce a serverFilter function as an option when creating a SteamUser instance. This function would allow users to filter the server list based on specific criteria, such as port availability.

const client = new SteamUser({
    serverFilter: (serverList) => {
        return serverList.filter(server => server.port === 443 || server.port === 80);
    }
});

Alternatives Considered

None at this time.

Additional Context

Implementing this feature would simplify connecting to services that restrict port usage, ensuring compatibility with a broader range of proxy providers.

@DoctorMcKay
Copy link
Owner

Sounds like webCompatibilityMode does what you want?

@Sadzurami
Copy link
Contributor

Sadzurami commented Sep 1, 2024

Sounds like webCompatibilityMode does what you want?

looks this feature not works as expected
after retrieving CMServers from api, servers list not filters by 443 port
so, even if webCompatibilityMode is enabled, we still can get websocket with 27*** port

@DoctorMcKay
Copy link
Owner

Sounds like webCompatibilityMode does what you want?

looks this feature not works as expected after retrieving CMServers from api, servers list not filters by 443 port so, even if webCompatibilityMode is enabled, we still can get websocket with 27*** port

Fixed in 5.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants