apache / apache/incubator-seata

nacos-config.sh推送seata配置到nacos1.3.0上发生错误

Open
#3,936 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
26k
Forks
8.8k
Avg merge
1d 8h
Merged PRs (30d)
4

Description

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.

### Ⅰ. Issue Description
./nacos-config.sh -h 192.168.0.104 -p 8804 -g SEATA_GROUP -t 3b964d9d-70c2-4c53-baf4-b51566f828ae -u nacos -w nacos
set nacosAddr=192.168.0.104:8804
set group=SEATA_GROUP
Please check the cluster status.
nacos1.3.0服务端日志:
2021-08-07 13:58:20,411 ERROR Servlet.service() for servlet [dispatcherServlet] in context with path [/nacos] threw exception
org.springframework.security.web.firewall.RequestRejectedException: The request was rejected because the URL was not normalized.

### Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

```
Just paste your stack trace here!
```

### Ⅲ. Describe what you expected to happen

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. xxx
2. xxx
3. xxx

### Ⅴ. Anything else we need to know?

### Ⅵ. Environment:

- JDK version :1.8
- OS :centos7
- Others:

Contributor guide

Open the contributing guide

Research direction

Start by running the shown nacos-config.sh command against a Nacos 1.3.0 server and inspect the resulting server log for the RequestRejectedException. Trace the script's request construction and compare it with the Nacos endpoint expectations; done means the Seata configuration is accepted without the URL normalization error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, shell
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.