Re: [I] feat: SUSE Linux Enterprise Server 15 support [apisix]
shreemaan-abhishek commented on issue #5: URL: https://github.com/apache/apisix/issues/5#issuecomment-2036306936 > I'm already working on building from source in SLES 15. looking forward to a blog post. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Impact for Redis license change? [apisix]
shreemaan-abhishek commented on issue #8: URL: https://github.com/apache/apisix/issues/8#issuecomment-2036304360 cc: @moonming -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] APISIX to handle all handshake between my client application and the 3rd party service, including getting token, refreshing token, etc. [apisix]
shreemaan-abhishek commented on issue #11106: URL: https://github.com/apache/apisix/issues/11106#issuecomment-2036303021 this is going to be very big 😅 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] docs: add doc for http3 [apisix]
zll600 closed pull request #10990: docs: add doc for http3 URL: https://github.com/apache/apisix/pull/10990 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] fix: update pdb version to k8s 1.25 [apisix-helm-chart]
zll600 closed pull request #713: fix: update pdb version to k8s 1.25 URL: https://github.com/apache/apisix-helm-chart/pull/713 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] feat: add discovery k8s dump data interface [apisix]
shreemaan-abhishek commented on PR #1: URL: https://github.com/apache/apisix/pull/1#issuecomment-2036075843 @hanqingwu should we add docs as well? Also, could you please show how the response body looks like? -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] How to integrate AWS NLB to Apisix Ingress controller in kubernetes? [apisix-ingress-controller]
github-actions[bot] closed issue #2077: How to integrate AWS NLB to Apisix Ingress controller in kubernetes? URL: https://github.com/apache/apisix-ingress-controller/issues/2077 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] bug: ApisixUpstream not created for a kubernetes service using discovery type kubernetes [apisix-ingress-controller]
singhajitk opened a new issue, #2200:
URL: https://github.com/apache/apisix-ingress-controller/issues/2200
### Current Behavior
Hi @shreemaan-abhishek, @H When Upstream creates through Apisix dashboard by
selecting Upstream Type: Service Discovery and it has below spec as yaml
```
type: roundrobin
hash_on: vars
scheme: https
discovery_type: kubernetes
pass_host: node
name: api-testapp
service_name: apisix/api-test:http
```
But it gave error "reason: ResourceSyncAborted" when creating using below
manifest file
```
apiVersion: apisix.apache.org/v2
kind: ApisixUpstream
metadata:
name: api-test-upstream
namespace: apisix
spec:
scheme: https
loadbalancer:
type: roundrobin
discovery:
serviceName: apisix/api-test:http
type: kubernetes
passHost: pass
```
### Expected Behavior
ApisixUpstream should get created and have status as
```
status:
conditions:
- lastTransitionTime: 'TimeStamp'
message: Sync Successfully
observedGeneration: 1
reason: ResourcesSynced
status: 'True'
type: ResourcesAvailable
```
### Error Logs
apisix-ingress-controller throw below error:
2024-04-04T08:16:14+08:00error apisix/apisix_upstream.go:333 failed
to get upstream apisix_api-test-upstream: not found
2024-04-04T08:16:14+08:00warnapisix/apisix_upstream.go:489 sync
ApisixUpstream failed, will retry {"object":
{"Type":1,"Object":{"Key":"apisix/api-test-upstream","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null},
"error": "not found"}
2024-04-04T08:16:49+08:00warnapisix/cluster.go:1164 upstream not
found {"id": "2a212dd9", "url":
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/upstreams/2a212dd9";,
"cluster": "default"}
### Steps to Reproduce
1. Install APISIX, APISIX ingress controller and APISIX dashboard with the
helm chart.
2. Create a ApisixUpstream with below template
```
apiVersion: apisix.apache.org/v2
kind: ApisixUpstream
metadata:
name: api-test-upstream
namespace: apisix
spec:
scheme: https
loadbalancer:
type: roundrobin
discovery:
serviceName: apisix/api-test:http
type: kubernetes
passHost: pass
```
3. Verify the created resource in cluster
### Environment
APISIX version : - 3.8.0
Operating system : Linux apisix-647b4867df-79542 5.4.0-136-generic test:
only check part of schema.
https://github.com/apache/apisix/pull/153~18.04.1-Ubuntu SMP Wed Nov 30
15:47:57 UTC 2022 x86_64 GNU/Linux
OpenResty / Nginx version (run openresty -V or nginx -V):
nginx version: openresty/1.21.4.2
built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
built with OpenSSL 3.2.0 23 Nov 2023
TLS SNI support enabled
APISIX Dashboard version: 3.0.0
APISIX ingress controller version: 1.8.0
--
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: notifications-unsubscr...@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [I] help request: ApisixTls configuration for SSL enabled Upstream [apisix]
singhajitk closed issue #4: help request: ApisixTls configuration for SSL enabled Upstream URL: https://github.com/apache/apisix/issues/4 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] help request: ApisixTls configuration for SSL enabled Upstream [apisix]
singhajitk commented on issue #4: URL: https://github.com/apache/apisix/issues/4#issuecomment-2035821927 > Can you try this ? https://apisix.apache.org/docs/apisix/tutorials/client-to-apisix-mtls/#mtls-bypass-based-on-regular-expression-matching-against-uri Thank you @hanqingwu, I used admin api to create apisixtls resource and it worked with field "skip_mtls_uri_regex". -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: aws-lambda plugin with IAM auth fails with URL-encoded query parameters [apisix]
deiwin commented on issue #11097: URL: https://github.com/apache/apisix/issues/11097#issuecomment-2035736853 Okay, maybe that wasn't a great library to suggest, as it's in JS and whatnot. But would the addition of https://github.com/Kong/lua-resty-aws be acceptable? This could be used for getting the credentials (defaulting to env variables, EKS pod identity, EC2 identity, etc) and the existing code could be kept for the signing logic. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Impact for Redis license change? [apisix]
billmoling opened a new issue, #8: URL: https://github.com/apache/apisix/issues/8 ### Description Dear APISIX Developers, With the recent announcement of Redis adopting dual Source-Available Licensing (RSALv2 and SSPLv1) from version 7.4 onwards, moving away from the BSD 3-Clause License, I'm reaching out to gather your perspectives on this significant change. Given APISIX's utilization of Redis, particularly for features like rate limiting, how do you foresee this licensing shift impacting the APISIX roadmap? Are there any anticipated adjustments or considerations in response to these changes? maybe support other cache system? News here: https://redis.com/blog/redis-adopts-dual-source-available-licensing/ -- 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: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] fix: disable features when plugin is turned off [apisix]
shreemaan-abhishek opened a new pull request, #7: URL: https://github.com/apache/apisix/pull/7 ### Description Fixes # (issue) ### Checklist - [ ] I have explained the need for this PR and the problem it solves - [ ] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [ ] I have updated the documentation to reflect this change - [ ] 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) -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] fix(prometheus): disable features when plugin is turned off [apisix]
shreemaan-abhishek closed pull request #11103: fix(prometheus): disable features when plugin is turned off URL: https://github.com/apache/apisix/pull/11103 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] fix(prometheus): disable features when plugin is turned off [apisix]
shreemaan-abhishek commented on PR #11103: URL: https://github.com/apache/apisix/pull/11103#issuecomment-2035077267 I will close this and create a PR myself. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] feat: add discovery k8s dump data interface [apisix]
shreemaan-abhishek commented on code in PR #1: URL: https://github.com/apache/apisix/pull/1#discussion_r1550083092 ## t/kubernetes/discovery/kubernetes3.t: ## @@ -332,6 +339,8 @@ POST /operators ] --- more_headers Content-type: application/json +--- response_body_like +.*"endpoints".* Review Comment: ``` --- response_body_like .*"endpoints".* ``` this doesn't seem sufficient to show that the feature works fine. The verification should be more descriptive. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] request help: how to translate the nginx weight-based annotation to apisix ingress controller [apisix-ingress-controller]
pottekkat commented on issue #2199: URL: https://github.com/apache/apisix-ingress-controller/issues/2199#issuecomment-2035034982 @ruiruijianggg From the [Nginx Ingress Controller docs](https://kubernetes.github.io/ingress-nginx/examples/canary/#create-ingress-pointing-to-your-canary-deployment) it seems like the weight you set in the `nginx.ingress.kubernetes.io/canary-weight` is the the percentage of traffic you want to route to your canary deployment. In APISIX, the you can configure a more granular traffic split where you can specify the ratio of how traffic is to be split between your baseline deployment and canary deployment. So if you want to directly translate, you can translate the percentage to ratio. `nginx.ingress.kubernetes.io/canary-weight: 50` would mean 50% to canary release. In `ApisixRoute`, this becomes: ```yaml apiVersion: apisix.apache.org/v2 kind: ApisixRoute metadata: name: canary-release spec: http: - name: canary-route match: paths: - /* backends: - serviceName: baseline-deployment servicePort: 8080 weight: 50 - serviceName: canary-deployment servicePort: 8080 weight: 50 ``` The weight can also be 1:1 or 2:2 as it would be treated as ratios as opposed to percentages in the Nginx annotation. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] request help: how to translate the nginx weight-based annotation to apisix ingress controller [apisix-ingress-controller]
ruiruijianggg opened a new issue, #2199: URL: https://github.com/apache/apisix-ingress-controller/issues/2199 ### Issue description I want to know how to translate the weight-based canary annotation in nginx【nginx.ingress.kubernetes.io/canary-weight】. The apisix ingress controller implements the canary function based on the traffix-split plug-in. Now I can only get the weight of the gray upstream from annotation. And the traffic-split plugin-in needs the id and weight of both the baseline upstream and the gray upstream. How the apisix ingress controller implement canary publishing based annotations? ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.8.0 - your Kubernetes cluster version (output of kubectl version): v1.25.3 - if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): -- 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: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] help request: ApisixTls configuration for SSL enabled Upstream [apisix]
hanqingwu commented on issue #4: URL: https://github.com/apache/apisix/issues/4#issuecomment-2034304134 Can you try this ? https://apisix.apache.org/docs/apisix/tutorials/client-to-apisix-mtls/#mtls-bypass-based-on-regular-expression-matching-against-uri -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] feat: add discovery k8s dump data interface [apisix]
hanqingwu commented on PR #1: URL: https://github.com/apache/apisix/pull/1#issuecomment-2034215713 @shreemaan-abhishek ，Thanks , I have found the method build k8s test env in workflows/kubernetes-ci.yml . -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Redirection is recommended to support other domain names [apisix]
github-actions[bot] closed issue #9201: Redirection is recommended to support other domain names URL: https://github.com/apache/apisix/issues/9201 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] help request: resty http got BAD ARGUMENT exception by accident [apisix]
github-actions[bot] commented on issue #9273: URL: https://github.com/apache/apisix/issues/9273#issuecomment-2034139333 This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the d...@apisix.apache.org list. Thank you for your contributions. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Redirection is recommended to support other domain names [apisix]
github-actions[bot] commented on issue #9201: URL: https://github.com/apache/apisix/issues/9201#issuecomment-2034139192 This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] feat: add discovery k8s dump data interface [apisix]
shreemaan-abhishek commented on PR #1: URL: https://github.com/apache/apisix/pull/1#issuecomment-2034095868 is this what you are looking for? https://github.com/shreemaan-abhishek/apisix/blob/5319503293c41cf41a2caa5cb944a12d40686c83/t/kubernetes/discovery/kubernetes.t#L38-L97 -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] chore(dev): upgrade to APISIX 3.9.0 [apisix-helm-chart]
mstefany commented on PR #745: URL: https://github.com/apache/apisix-helm-chart/pull/745#issuecomment-2034000134 Version 3.9.0 does not work, because enable_http2 needs to be on apisix level, not on apisix.ssl.listen level: https://github.com/apache/apisix-helm-chart/blob/6b8acad93b625338ea0e256135e48d6224db93a6/charts/apisix-ingress-controller/templates/apisix-configmap.yaml#L58 ``` + apisix-ingress-controller-8565f87c67-74j96 › apisix apisix-ingress-controller-8565f87c67-74j96 apisix /usr/local/openresty//luajit/bin/luajit ./apisix/cli/apisix.lua init apisix-ingress-controller-8565f87c67-74j96 apisix apisix-ingress-controller-8565f87c67-74j96 apisix WARNING: using fixed Admin API token has security risk. apisix-ingress-controller-8565f87c67-74j96 apisix Please modify "admin_key" in conf/config.yaml . apisix-ingress-controller-8565f87c67-74j96 apisix apisix-ingress-controller-8565f87c67-74j96 apisix apisix-ingress-controller-8565f87c67-74j96 apisix ERROR: port level enable_http2 in ssl.listen is deprecatedfrom 3.9 version, and you should use enable_http2 in apisix level. ``` -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] feat: add discovery k8s dump data interface [apisix]
hanqingwu commented on PR #1: URL: https://github.com/apache/apisix/pull/1#issuecomment-2033867377 I have not find a k8s mock apiserver like one in the test case -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] docs: add doc for http3 [apisix]
kayx23 commented on code in PR #10990:
URL: https://github.com/apache/apisix/pull/10990#discussion_r1549155047
##
docs/en/latest/http3.md:
##
@@ -0,0 +1,128 @@
+---
+title: HTTP/3 protocol
+---
+
+
+
+[HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) is the third major version of
the Hypertext Transfer Protocol (HTTP). Unlike its predecessors which rely on
TCP, HTTP/3 is based on [QUIC (Quick UDP Internet Connections)
protocol](https://en.wikipedia.org/wiki/QUIC). It brings several benefits that
collectively result in reduced latency and improved performance:
+
+ * enabling seamless transition between different network connections, such as
switching from Wi-Fi to mobile data.
+ * eliminating head-of-line blocking, so that a lost packet does not block all
streams.
+ * negotiate TLS versions at the same time as the TLS handshakes, allowing for
faster connections.
+ * providing encryption by default, ensuring that all data transmitted over an
HTTP/3 connection is protected and confidential.
+ * providing zero round-trip time (0-RTT) when communicating with servers that
clients already established connections to.
+
+ APISIX currently supports HTTP/3 connections between downstream clients and
APISIX. HTTP/3 connections with upstream services is not yet supported.
Contributions are welcomed.
+
+ :::caution
+
+ This feature has not been tested at scale and therefore, is not recommended
for production use.
+
+ :::
+
+## Usage example
+
+1. To allow for HTTP/3 connections on 9443 port, add the following
configurations to the `config.yaml` file:
+
+```yaml
+apisix:
+ ssl:
+listen:
+ - port: 9443
+enable_http3: true # enable HTTP/3
+ssl_protocols: TLSv1.3 # enable TLSv1.3
+```
+
+**note** `enable_http3` requires `TLSv1.3`
+
+2. Create an SSL object for test.com.
+
+```shell
+curl http://127.0.0.1:9180/apisix/admin/ssls/1 \
+-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
+{
+ "cert" : "'"$(cat t/certs/apisix.crt)"'",
+ "key": "'"$(cat t/certs/apisix.key)"'",
+ "snis": ["test.com"]
+}'
+```
+
+3. Create route
+
+```shell
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
+-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
+{
+"uri": "/get",
+"hosts": ["test.com"],
+"methods": ["GET"],
+"upstream": {
+"type": "roundrobin",
+"nodes": {
+"httpbin.org": 1
+}
+}
+}'
+```
+
+4. Access verification
+
+Access test.com using HTTP/3:
+
+- curl version 7.88.0+, requires
[http-only](https://github.com/curl/curl/blob/master/docs/cmdline-opts/http3-only.md)
option.
Review Comment:
`8.4.0` also doesn't seem to support this option
--
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: notifications-unsubscr...@apisix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] docs: add doc for http3 [apisix]
kayx23 commented on code in PR #10990:
URL: https://github.com/apache/apisix/pull/10990#discussion_r1549143951
##
docs/en/latest/http3.md:
##
@@ -0,0 +1,128 @@
+---
+title: HTTP/3 protocol
+---
+
+
+
+[HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) is the third major version of
the Hypertext Transfer Protocol (HTTP). Unlike its predecessors which rely on
TCP, HTTP/3 is based on [QUIC (Quick UDP Internet Connections)
protocol](https://en.wikipedia.org/wiki/QUIC). It brings several benefits that
collectively result in reduced latency and improved performance:
+
+ * enabling seamless transition between different network connections, such as
switching from Wi-Fi to mobile data.
+ * eliminating head-of-line blocking, so that a lost packet does not block all
streams.
+ * negotiate TLS versions at the same time as the TLS handshakes, allowing for
faster connections.
+ * providing encryption by default, ensuring that all data transmitted over an
HTTP/3 connection is protected and confidential.
+ * providing zero round-trip time (0-RTT) when communicating with servers that
clients already established connections to.
+
+ APISIX currently supports HTTP/3 connections between downstream clients and
APISIX. HTTP/3 connections with upstream services is not yet supported.
Contributions are welcomed.
+
+ :::caution
+
+ This feature has not been tested at scale and therefore, is not recommended
for production use.
+
+ :::
+
+## Usage example
+
+1. To allow for HTTP/3 connections on 9443 port, add the following
configurations to the `config.yaml` file:
+
+```yaml
+apisix:
+ ssl:
+listen:
+ - port: 9443
+enable_http3: true # enable HTTP/3
+ssl_protocols: TLSv1.3 # enable TLSv1.3
+```
+
+**note** `enable_http3` requires `TLSv1.3`
+
+2. Create an SSL object for test.com.
+
+```shell
+curl http://127.0.0.1:9180/apisix/admin/ssls/1 \
+-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
+{
+ "cert" : "'"$(cat t/certs/apisix.crt)"'",
+ "key": "'"$(cat t/certs/apisix.key)"'",
+ "snis": ["test.com"]
+}'
+```
+
+3. Create route
+
+```shell
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
+-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
+{
+"uri": "/get",
+"hosts": ["test.com"],
+"methods": ["GET"],
+"upstream": {
+"type": "roundrobin",
+"nodes": {
+"httpbin.org": 1
+}
+}
+}'
+```
+
+4. Access verification
+
+Access test.com using HTTP/3:
+
+- curl version 7.88.0+, requires
[http-only](https://github.com/curl/curl/blob/master/docs/cmdline-opts/http3-only.md)
option.
+
+```shell
+curl -k -vvv -H "Host: test.com" -H "content-length: 0" --http3-only --resolve
"test.com:9443:127.0.0.1" https://test.com:9443/get
Review Comment:
this isn't working for some reasons:
my curl version:
```
curl 8.7.1 (x86_64-apple-darwin) libcurl/8.7.1 OpenSSL/3.2.1 zlib/1.3.1
brotli/1.1.0 zstd/1.5.6 c-ares/1.27.0 libidn2/2.3.7 libpsl/0.21.5
libssh2/1.11.0 nghttp2/1.60.0 nghttp3/1.2.0
Release-Date: 2024-03-27
```
--
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: notifications-unsubscr...@apisix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [I] [Site]: Update Blog summary pages [apisix-website]
Yilialinn commented on issue #1751: URL: https://github.com/apache/apisix-website/issues/1751#issuecomment-2033794447 > ### Current State > **Description of the current state/issue**: > > The "Featured" and "Editors' Picks" sections on both summary pages only cover from late 2022 to Jan - June/Jul of 2023. > > Should take a look at the stats of Jul/Aug - Dec 2023 contents and decide what to update. > > **Link to the page**: > > * EN-US https://apisix.apache.org/blog/ > * ZH-CN https://apisix.apache.org/zh/blog/ > > **Screenshots (if relevant)**: EN-US  > > ZH-CN  > > ### Desired State > **Description of the change you are proposing**: > > Some or all contents are updated based on most viewed or other sort of content strategy. The current ones seems to be out of date. > > ### Would you like to fix this issue? > No. Please assign another contributor I will update the editors' picks every month -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Site]: Update Blog summary pages [apisix-website]
Yilialinn commented on issue #1751: URL: https://github.com/apache/apisix-website/issues/1751#issuecomment-2033793099 > Hi @Yilialinn Can you help resolve this issue? Sorry for my late reply. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
