Illegal character in scheme name at index 0

最新推荐文章于 2023-12-25 08:00:00 发布
最新推荐文章于 2023-12-25 08:00:00 发布
阅读量7.9k 收藏 1
点赞数 1
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_37939020/article/details/65632658
版权




调用微信接口生成二维码时,一直报错,找了很久,原来是调用微信接口时url中多复制了一个空格,将空格删除就添加成功了




qrcode{"exprtime":1,"qrname":"12345","qrtype":"b"}

*************b
2017-03-24 16:13:55.288 ERROR 7876 --- [nio-8080-exec-7] o.s.boot.context.web.ErrorPageFilter     : Forwarding to error page from request [/insertone] due to exception [Illegal character in scheme name at index 0:  https://api.weixin.qq.com/cgi-bin/qrcode/create?access_token=wNC9JYMhHPYJ-x1hX2tM84hbj8OLHDLbmTW8cUgJr2nC7B7C0emt22DzZtFSBk5KIFHak-bmHJDi4OB1RfWNgf0tsbR3fUDOFhgMyngXtn9cg91M0oyk2YJJjchKjviQMJAiAAAEBS]


java.lang.IllegalArgumentException: Illegal character in scheme name at index 0:  https://api.weixin.qq.com/cgi-bin/qrcode/create?access_token=wNC9JYMhHPYJ-x1hX2tM84hbj8OLHDLbmTW8cUgJr2nC7B7C0emt22DzZtFSBk5KIFHak-bmHJDi4OB1RfWNgf0tsbR3fUDOFhgMyngXtn9cg91M0oyk2YJJjchKjviQMJAiAAAEBS
at java.net.URI.create(URI.java:852) ~[na:1.8.0_73]
at org.apache.http.client.methods.HttpPost.<init>(HttpPost.java:76) ~[httpclient-4.5.2.jar:4.5.2]
at com.hzit.qrcode.myuntil.NetUtil.post(NetUtil.java:84) ~[classes/:0.0.1-SNAPSHOT]
at com.hzit.qrcode.myuntil.QRcodeUtil.getTicket(QRcodeUtil.java:22) ~[classes/:0.0.1-SNAPSHOT]
at com.hzit.qrcode.service.QrcodeServiceImpl.getTicket(QrcodeServiceImpl.java:33) ~[classes/:0.0.1-SNAPSHOT]
at com.hzit.qrcode.service.QrcodeServiceImpl.getQrcodeurl(QrcodeServiceImpl.java:46) ~[classes/:0.0.1-SNAPSHOT]
at com.hzit.qrcode.service.QrcodeServiceImpl.doInsertOne(QrcodeServiceImpl.java:59) ~[classes/:0.0.1-SNAPSHOT]
at com.hzit.qrcode.web.QRcodeAction.insertqrcode(QRcodeAction.java:51) ~[classes/:0.0.1-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_73]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_73]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_73]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_73]
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221) ~[spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136) ~[spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:832) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:743) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:961) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:895) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:967) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:869) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) ~[servlet-api.jar:na]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:843) ~[spring-webmvc-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) ~[servlet-api.jar:na]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) ~[tomcat-websocket.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at com.alibaba.druid.support.http.WebStatFilter.doFilter(WebStatFilter.java:123) ~[druid-1.0.14.jar:1.0.14]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) ~[spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:89) ~[spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:77) ~[spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.springframework.boot.context.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:120) [spring-boot-1.3.8.RELEASE.jar:1.3.8.RELEASE]
at org.springframework.boot.context.web.ErrorPageFilter.access$000(ErrorPageFilter.java:61) [spring-boot-1.3.8.RELEASE.jar:1.3.8.RELEASE]
at org.springframework.boot.context.web.ErrorPageFilter$1.doFilterInternal(ErrorPageFilter.java:95) [spring-boot-1.3.8.RELEASE.jar:1.3.8.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.boot.context.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:113) [spring-boot-1.3.8.RELEASE.jar:1.3.8.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:121) [spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.8.RELEASE.jar:4.2.8.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) [catalina.jar:8.0.33]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) [catalina.jar:8.0.33]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212) [catalina.jar:8.0.33]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) [catalina.jar:8.0.33]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) [catalina.jar:8.0.33]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) [catalina.jar:8.0.33]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) [catalina.jar:8.0.33]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) [catalina.jar:8.0.33]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) [catalina.jar:8.0.33]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522) [catalina.jar:8.0.33]
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095) [tomcat-coyote.jar:8.0.33]
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672) [tomcat-coyote.jar:8.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1502) [tomcat-coyote.jar:8.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1458) [tomcat-coyote.jar:8.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_73]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_73]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:8.0.33]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_73]
Caused by: java.net.URISyntaxException: Illegal character in scheme name at index 0:  https://api.weixin.qq.com/cgi-bin/qrcode/create?access_token=wNC9JYMhHPYJ-x1hX2tM84hbj8OLHDLbmTW8cUgJr2nC7B7C0emt22DzZtFSBk5KIFHak-bmHJDi4OB1RfWNgf0tsbR3fUDOFhgMyngXtn9cg91M0oyk2YJJjchKjviQMJAiAAAEBS
at java.net.URI$Parser.fail(URI.java:2848) ~[na:1.8.0_73]
at java.net.URI$Parser.checkChars(URI.java:3021) ~[na:1.8.0_73]
at java.net.URI$Parser.checkChar(URI.java:3031) ~[na:1.8.0_73]
at java.net.URI$Parser.parse(URI.java:3047) ~[na:1.8.0_73]
at java.net.URI.<init>(URI.java:588) ~[na:1.8.0_73]
at java.net.URI.create(URI.java:850) ~[na:1.8.0_73]

... 71 common frames omitted

*******************************************************************************************************************************************************************************

将空格删除后异常消除!










qq_37939020
关注
Illegal character in scheme name at index
m0_49194578的博客
03-20 783
花里胡哨！ url忘记写http：//了而已 淦！
Illegal character in scheme name at index 0: localhost:
热门推荐
stujike123456的博客
07-22 2万+
三种解决方式： 1、访问地址时需要有http:// 作为开头,查看是否有空格 2、发送url时的转化问题，使用URL u = new URL(原url)转化 3、ASCII装换问题。
链路追踪 Zipkin+Sleuth 解决 Illegal character in scheme name at index 0: 192.168.100.130:9411/xxx/xx
qq_37354060的博客
12-28 719
链路追踪 Zipkin+Sleuth 解决 Illegal character in scheme name at index 0: 192.168.100.130:9411/xxx/xx 1. 出现问题 日志中出现如下警告 这是访问url时, 出现Illegal character in scheme name at index 0: 192.168.100.130:9411/xxx/xx问题 2. 解决方法 错误的写法 应该改为 注意前缀 spring.zipkin.base-url=http
java.net.URISyntaxException: Illegal character in scheme name at index 0: 10
hxq133233的博客
12-29 8898
今天用java调用一个http请求结果报java.net.URISyntaxException: Illegal character in scheme name at index 0: 10这个错误，首先百度，跳出一堆博客结果全是复制黏贴，第一页全是一个答案，都是什么有|等特殊字符，结果我的url里面根本没有这些特殊字符。大家写技术博客只会抄袭他人，复制过来真是可耻。 下面是我自己的排查结果，...
java.net.URISyntaxException: Illegal character in scheme name at index 0:
小葫芦的博客
10-16 5830
开发中遇到了一个异常，在调用云信RESTful API接口时，报了 java.net.URISyntaxException: Illegal character in scheme name at index 0: 这个错： 原始代码： HttpGet httpGet = new HttpGet(" https://roomserver-dev.netease.im/v1/api/room...
properties 配置gateway Illegal character in scheme name at index 0: 'lb://' + serviceId
最新发布
09-07
在Spring Cloud Gateway的配置中，如果遇到了`properties`配置错误导致的异常信息，比如`Illegal character in scheme name at index 0: 'lb://' + serviceId`，这通常是因为在配置文件中使用了不合法的URI方案名。...
java.lang.IllegalArgumentException: Illegal character in scheme name at index 0:
09-27
java.lang.IllegalArgumentException: Illegal character in scheme name at index 0 是由于URL中的方案名称出现非法字符导致的错误。URL方案名称应该符合特定的命名规则，不允许包含非法字符。如果您在URL中使用了...
创建URL java.lang.IllegalArgumentException: Illegal character in scheme name at index
08-17
引用和提供了关于出现"java.lang.IllegalArgumentException: Illegal character in scheme name at index 0"异常的信息。这个异常通常是由于URL地址中出现非法字符导致的。中提到控制台显示了类似的错误信息，而中的...
Caused by: java.net.URISyntaxException: Illegal character in scheme name at index 0:
张小凡
05-22 5757
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at ...
【请求第三方 url 异常】Illegal character in scheme name at index x （已解决）
M_Love_U的博客
07-08 9789
Illegal character in scheme name at index x （已解决）
调用别人接口时出现 Illegal character in scheme name at index 0: https://(已解决)
weixin_88429的博客
04-17 1033
1.在使用Http发送请求时出现Illegal character in scheme name at index 0: https://错误。2.报的是0号索引异常,检查路径发现有个空格。3.删除之后,在测试就OK了。
Sqoop导出数据报错：Illegal character in scheme name at index 0: [file:///usr/.../hive-hcatalog-core.jar]
我是不冷的冰的博客
12-30 2618
Sqoop导出数据报错：Illegal character in scheme name at index 0: [file:///usr/…/hive-hcatalog-core.jar] 不积硅步，无以至千里。 1、作业任务 使用Sqoop导出hive的数据到SqlServer # 脚本 sqoop export --connect 'jdbc:sqlserver://主机名:端口;database=库名' --username '用户名' --password '密码' \ --table 'sqls
java.lang.IllegalArgumentException:
aa879131987的博客
10-08 629
报java.net.URISyntaxException: Illegal character in scheme name。某次在使用 spark调用 hdfs 的配置文件中，链接中开头写入空格。（2）URL前面前面。等特殊字符，导致报错。
redis Illegal character in scheme name at index 0: []r[]e[]d[]i[]s[]:[]/[]/[
church_qq的博客
12-25 661
此时，再去跑我的 java程序，就不再有"redis Illegal character in scheme name at index 0: []r[]e[]d[]i[]s[]:[]/[]/["这个错误了。IP是云服务器外网地址1.98.x.xxx，从本地远程连接云服务器跑这个命令，结果卡在"Waiting for the cluster to join........"它需要连接一个搭建在本机上的redis集群。1. 引用的redis jar 包版本有问题，换版本后解决。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值