ChatGPTNextWeb / ChatGPTNextWeb/NextChat
[Bug] Self-Deploied WEBDAV service can't be used to backup
- Dominant language
- TypeScript
- Stars
- 88.8k
- Forks
- 59.1k
- PR merge metrics
- No merged PRs in 30d
Description
### π¦ Deployment Method
Docker
### π Version
v2.12.4
### π» Operating System
Ubuntu
### π System Version
22.04
### π Browser
Chrome
### π Browser Version
Google Chrome 126.0.6478.126
### π Bug Description
I have deploied my webdav service, and can access it with curl
`β ~ curl -u USERNAME:PASSWD http://MY_HOSTNAME:3971/`
got html output:
```
Index of /
Index of /
```
but In my nextchat's config, I click "ζ£ζ₯ε―η¨ζ§β (check availableοΌ
it sends http req
https://MY_CHAT_HOST/api/webdav/chatgpt-next-web?endpoint=http://MY_ADV_HOST:3971
got 400 bad request
when I click sync
it sends http req
https://MY_CHAT_HOST/api/webdav/chatgpt-next-web/backup.json?endpoint=http://MY_ADV_HOST:3971
got resp
404
I have already insert my endpoint to white list using docker-compose
```
chatgpt:
image: yidadaa/chatgpt-next-web:using
container_name: chatgpt
environment:
- WHITE_WEBDEV_ENDPOINTS=http://MY_HOST:3971
restart: always
```
### π· Recurrence Steps
_No response_
### π¦ Expected Behavior
_No response_
### π Additional Information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the /api/webdav/chatgpt-next-web and /api/webdav/chatgpt-next-web/backup.json handlers, then compare their endpoint handling with the WHITE_WEBDEV_ENDPOINTS Docker configuration and the reported curl response. Done means the availability check and backup request work against the listed self-hosted WebDAV endpoint without returning 400 or 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nextjs, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100