[Bug] PerformHttpRequest does not normalize empty URL path to /

[JesterIruka]

Summary

1. Use PerformHttpRequest to access any domain without a path, e.g. https://any-api.com.
2. Since the current PerformHttpRequest does not default the path to /, the request fails or behaves incorrectly.
3. The developer is forced to explicitly append the trailing slash (https://any-api.com/) for the request to work as expected.

Expected behavior: When no path is provided, PerformHttpRequest should default the request path to /, consistent with standard HTTP client behavior (browsers, curl, most HTTP libraries).

Actual behavior: The path is left empty instead of being normalized to /, causing the request to fail unless the developer manually adds the trailing slash.

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b92 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Windows 11 Build 26200

CPU

AMD Ryzen 7 5700G

RAM

32 GB DDR4

Using txAdmin?

Yes

Hosting provider

Self-hosted

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Use PerformHttpRequest to access any domain without a path, e.g. https://any-api.com.
2. Since the current PerformHttpRequest does not default the path to /, the request fails or behaves incorrectly.
3. The developer is forced to explicitly append the trailing slash (https://any-api.com/) for the request to work as expected.

Expected Behavior

When no path is provided, PerformHttpRequest should default the request path to /, consistent with standard HTTP client behavior (browsers, curl, most HTTP libraries).

Actual Behavior

The path is left empty instead of being normalized to /, causing the request to fail unless the developer manually adds the trailing slash.

Evidence

No response

Additional Context

No response

[FabianTerhorst]

Thanks, we are looking into this.

[Gogsi]

A fix for this bug has been implemented and is available in the latest patch. Please try again and let us know if the issue persists. Thanks for your help!

[JesterIruka]

A fix for this bug has been implemented and is available in the latest patch. Please try again and let us know if the issue persists. Thanks for your help!

Thank you, it's fixed now.