This is an automated email from the ASF dual-hosted git repository.
qiuxiafan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-client-js.git
The following commit(s) were added to refs/heads/master by this push:
new 2bb9cd0 docs: Fix doc link (#141)
2bb9cd0 is described below
commit 2bb9cd050fc227fef14992aa780bb32e4623b75a
Author: wuwen <[email protected]>
AuthorDate: Tue Sep 24 15:11:01 2024 +0800
docs: Fix doc link (#141)
---
README.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index 8dd3bec..4366943 100644
--- a/README.md
+++ b/README.md
@@ -197,9 +197,9 @@ The SkyWalking client-js agent would be deployed and
running outside of your dat
There are various kinds of telemetry relative data would be reported to
backend separately or through your original HTTP requests.
In order to implement **distributed tracing from the browser**, an HTTP header
with the name `sw8` will be added to HTTP requests
-according to [Cross Process Propagation Headers Protocol
v3](https://skywalking.apache.org/docs/main/next/en/protocols/skywalking-cross-process-propagation-headers-protocol-v3/).
-`client-js` will also report spans and browser telemetry data through [Trace
Data Protocol
v3](https://skywalking.apache.org/docs/main/next/en/protocols/trace-data-protocol-v3/)
and
-[Browser
Protocol](https://skywalking.apache.org/docs/main/next/en/protocols/browser-protocol/).
+according to [Cross Process Propagation Headers Protocol
v3](https://skywalking.apache.org/docs/main/latest/en/api/x-process-propagation-headers-v3/).
+`client-js` will also report spans and browser telemetry data through [Trace
Data Protocol
v3](https://skywalking.apache.org/docs/main/latest/en/api/trace-data-protocol-v3/)
and
+[Browser
Protocol](https://skywalking.apache.org/docs/main/latest/en/api/browser-protocol/).
Because all of this data is reported from an unsecured environment, users
should make sure to:
1. Not expose OAP server to the internet directly.
