ShaunMaher opened a new pull request, #11782:
URL: https://github.com/apache/apisix/pull/11782

   ### Description
   
   Fixes #11781 
   
   In the event that `ngx.var.server_port` is a blank string (e.g. client 
request arrived via unix socket instead of TCP port), `httpc:connect` is given 
the listening port from the APISIX config, preventing an error.
   
   I have tried to cover the possible ways that node_port can be defined in the 
config.
   
   `function tab_is_array(t)` borrowed from: 
https://github.com/apache/apisix/blob/a0b1a4554dc9ce23e877cc1fc58507c795203878/apisix/cli/file.lua#L47
   
   Sorry if my Lua code isn't up to your standards, I'm new to Lua and still 
finding my feet.
   
   ### Checklist
   
   - [X] I have explained the need for this PR and the problem it solves
   - [X] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change: I'll need help with 
this
   - [ ] I have updated the documentation to reflect this change: I don't think 
any changes are necessary.
   - [ ] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to