[11.x] Fixes trust proxy REMOTE_ADDR not working in Swoole

[chuoke]

When using REMOTE_ADDR set the trust proxy in Swoole, like this:

      $middleware->trustProxies(
            at: [
                'REMOTE_ADDR',
            ],
            headers: Request::HEADER_X_FORWARDED_FOR
        );

Is nothing set to request->trustedProxies because $_SERVER['REMOTE_ADDR'] does not exist in Swoole. But Laravel internally converts the server information in Swoole into the request->server attribute, which includes REMOTE_ADDR, and then request()->server->get('REMOTE_ADDR') can get the corresponding value normally.

This leads to some logical ambiguity and increases the cognitive burden and learning cost.

So we need to unify the logic to avoid inconsistency. I can't change this in the Request class because of the method attribute restrictions, so the solution I've come up with so far is this, it works for me, and I hope there's another better way to solve it.

[taylorotwell]

Can you add a test then mark as ready for review?

[chuoke]

hi @taylorotwell I added one test case. the checks were unsuccessful, but not caused by this change, it seems some other network is wrong. Can you recheck this?