Url encoded problem
See original GitHub issueDescribe the bug When I try to publish i get this :
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://domain/@scope%2fpackage - no such package available
npm ERR! 404
npm ERR! 404 '@scope/package@0.1.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
In logs I’ve this :
http <-- 404, user: user(*.*.*.* via *.*.*.*), req: 'PUT /@scope%2fpackage', error: no such package available
http <-- 404, user: user(*.*.*.* via *.*.*.*), req: 'PUT /@scope%2fpackage', error: no such package available
Expected behavior It should push correctly package
Docker || Kubernetes (please complete the following information):
- Docker verdaccio tag: 4.5.1
- Docker Version: 19.03.8
- Traefik Version: v2.2.0
Environment informations It runs behind traefik reverse proxy
Configuration File (cat ~/.config/verdaccio/config.yaml)
storage: ./storage
auth:
htpasswd:
file: ./htpasswd
uplinks:
npmjs:
url: https://registry.npmjs.org/
packages:
'@*/*':
access: $all
publish: $authenticated
proxy: npmjs
'**':
proxy: npmjs
logs:
- {type: stdout, format: pretty, level: http}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Possible URL encoding issues - Stack Overflow
I don't know how to do that in Ruby, but this question looks like a good start. The browser probably escapes URLs automatically, ......
Read more >Resolving the The URL-encoded form data is not valid Error
Answer · 1. Go to the folder where the application (Secret Server or Password Reset Server) is installed. · 2. Open the web-appsettings.config ......
Read more >URL Encoding | Google Maps Platform
The URI generic syntax uses URL encoding to deal with this problem, ... All characters to be URL-encoded are encoded using a '%'...
Read more >2.2. URL Character Encoding Issues - Freesoft
All unsafe characters must always be encoded within a URL. For example, the character "#" must be encoded within URLs even in systems...
Read more >URL Encoding does not work anymore #9554 - GitHub
Hi! I'm having a similar issue with encoding '%' in my get parameters now. If I replace '%' with '%25' manually in the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
if you are using an apache reverse proxy / virtual host, you need to configure it with
AllowEncodedSlashes On
and potentiallyProxyPreserveHost On
it does say that; and that’s what i used, and it didn’t work with scoped packages (not fun when you depend on babel or types and more). kept tweaking things all over the place and … it works?