AdguardTeam / AdguardTeam/CoreLibs

Cannot access `search.shopping.naver.com` due to WAF is triggered

Aperta
#2,093 0 commenti 0 reazioni 1 assegnatario Assegnata a @ngorskikh Vedi su GitHub
Bug Priority: P4 Status: In Progress
Lingua principale
Nessun dato sulla lingua
Stelle
52
Fork
10
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Please answer the following questions for yourself before submitting an issue

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard version

2.19.0.2258

### Browser version

Google Chrome 150.0.7871.187 arm64

### OS version

macOS 26.5.2

### Issue Details

Steps to reproduce:
1. Disable all filters lists, config of stealth mode, conf of DNS protection and userscripts
2. Visit https://shopping.naver.com/ns/home
3. Querying '안경' at `input[class^="_searchInput_search_text_"]`

### Expected Behavior

_No response_

### Actual Behavior

WAF is triggered

### Screenshots

Screenshot 1

### Additional Information

_No response_

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.