X
點擊此處開啟此網站的行動版。

技術支援討論區

Trouble with Content Security Policy (CSP)

已張貼

In the latest Firefox 33 there seem to be an issue with Content Security Policy (CSP) and how it handles url that are url encoded. For instance when some CSP directive is set to like https://mywebsite.com/application/do;jsessiond=1234 - it will get URL encoded so the ; gets replaced by %3B. In Firefox 32 and earlier this worked, but not in this new solution.

In the latest Firefox 33 there seem to be an issue with Content Security Policy (CSP) and how it handles url that are url encoded. For instance when some CSP directive is set to like https://mywebsite.com/application/do;jsessiond=1234 - it will get URL encoded so the ; gets replaced by %3B. In Firefox 32 and earlier this worked, but not in this new solution.

額外的系統細節

已安裝的外掛程式

  • Next Generation Java Plug-in 10.67.2 for Mozilla browsers
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.8
  • VLC media player Web Plugin 2.1.3
  • Adobe Shockwave for Director Netscape plug-in, version 12.1.3.153
  • Google Update
  • 5.1.30514.0
  • The plugin allows you to have a better experience with Microsoft Lync
  • Citrix URL-Redirection Helper Plugin
  • Citrix Receiver Plugin (Win32)
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • The plugin allows you to have a better experience with Microsoft SharePoint
  • Office Plugin for Netscape Navigator

應用程式

  • User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0

更多資訊

guigs 1072 個解決方法 11697 個答案

It may be that it needs a header application/x-www-form-urlencoded is this included in your url request as well as charset UTF-8?

If you select a different encoding via web dev https://developer.mozilla.org/en-US/d.../encodeURI

This sounds like what it did before? http://www.justarrangingbits.org/fire.../index.html

It may be that it needs a header application/x-www-form-urlencoded is this included in your url request as well as charset UTF-8? If you select a different encoding via web dev [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI] This sounds like what it did before? [http://www.justarrangingbits.org/firefox-magic-decoding-address-bar/index.html]