alibaba / alibaba/nginx-http-concat
nginx/1.7.6新版本对JS使用标准MIME-Type(application/javascript)导致的400 Bad Request
- Dominant language
- C
- Stars
- 863
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
复现过程:删除nginx的目录:rm /usr/local/nginx/ -rf,重新安装Nginx的1.7.6版本,并添加本模块,按说明文档配置后,按照说明访问css文件没有问题,但访问js文件时候,会出现400的错误提示。
原因是:Nginx1.7.6使用了标准的MIME-Type:application/javascript,而本模块的代码中,写的是application/x-javascript的类型,不匹配,所以导致这个问题
解决方案:1、修改nginx的mime.types配置文件,修改js的文件类型为application/x-javascript;2、修改模块的源文件,重新编译nginx并安装,统一为application/javascript;3、等待这个模块更新
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the module source and Nginx's mime.types configuration, comparing the JavaScript MIME values described in the report. Done means the module and Nginx 1.7.6 agree on application/javascript and JavaScript requests no longer return 400; verify by repeating the reported CSS and JS access steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, nginx
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100