stubbornTanzhe commented on issue #7972: URL: https://github.com/apache/apisix/issues/7972#issuecomment-1255833785
> > I change that,but seems that it's only listen 127.0.0.1 and tcpv4 > > `127.0.0.1` in ipv6 is `::ffff:7f00:1`, my config: > > ``` > apisix: > admin_key: > - name: admin > key: edd1c9f034335f136f87ad84b625c8f1 # using fixed API token has security risk, please update it when you deploy to production environment > role: admin > > allow_admin: > - ::ffff:7f00:1 > ``` > > ### test > #### add route > ``` > curl -X PUT 'http://127.0.0.1:9080/apisix/admin/routes/1' \ > -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' \ > -d '{ > "uri": "/*", > "upstream": { > "nodes": { > "httpbin.org:80": 1 > }, > "type": "roundrobin" > } > }' > ``` > > #### hot route > ``` > curl http://127.0.0.1:9080/get > { > "args": {}, > "headers": { > "Accept": "*/*", > "Host": "127.0.0.1", > "User-Agent": "curl/7.84.0", > "X-Amzn-Trace-Id": "xxx", > "X-Forwarded-Host": "127.0.0.1" > }, > ...... > } > ``` > > success on APISIX v2.13 maybe i am not describe it clear~ i mean when in ipv6 env, the apisix pod's ip is ipv6 address, but admin address is ipv4 the admin CURD api is ok when curl to 127.0.0.1, but it seems that it use ipv4 tcp stream in the tcp layer~ -- 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]
