Last Piece Hacktivist Crew

Editing: KNOWN-ISSUES.html

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html 
     PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <title>File: KNOWN-ISSUES</title>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
  <meta http-equiv="Content-Script-Type" content="text/javascript" />
  <link rel="stylesheet" href=".././rdoc-style.css" type="text/css" media="screen" />
  <script type="text/javascript">
  // <![CDATA[

function popupCode( url ) {
    window.open(url, "Code", "resizable=yes,scrollbars=yes,toolbar=no,status=no,height=150,width=400")
  }

function toggleCode( id ) {
    if ( document.getElementById )
      elem = document.getElementById( id );
    else if ( document.all )
      elem = eval( "document.all." + id );
    else
      return false;

elemStyle = elem.style;
    
    if ( elemStyle.display != "block" ) {
      elemStyle.display = "block"
    } else {
      elemStyle.display = "none"
    }

return true;
  }
  
  // Make codeblocks hidden by default
  document.writeln( "<style type=\"text/css\">div.method-source-code { display: none }</style>" )
  
  // ]]>
  </script>

</head>
<body>

<div id="fileHeader">
    <h1>KNOWN-ISSUES</h1>
    <table class="header-table">
    <tr class="top-aligned-row">
      <td><strong>Path:</strong></td>
      <td>KNOWN-ISSUES
      </td>
    </tr>
    <tr class="top-aligned-row">
      <td><strong>Last Update:</strong></td>
      <td>Thu Dec 05 17:13:57 -0500 2019</td>
    </tr>
    </table>
  </div>

<div id="description">
      <h1>Known issues with <a href="../classes/Rack.html">Rack</a> and ECMA-262</h1>
<ul>
<li>Many users expect the escape() function defined in ECMA-262 to be
compatible with URI. Confusion is especially strong because the
documentation for the escape function includes a reference to the URI
specifications. ECMA-262 escape is not however a URI escape function, it is
a javascript escape function, and is not fully compatible. Most notably,
for characters outside of the BMP. Users should use the more correct
encodeURI functions.

</li>
</ul>
<h1>Known issues with <a href="../classes/Rack.html">Rack</a> and Web servers</h1>
<ul>
<li>Lighttpd sets wrong SCRIPT_NAME and PATH_INFO if you mount your FastCGI app
at &quot;/&quot;. This can be fixed by using this middleware:

<pre>
  class LighttpdScriptNameFix
    def initialize(app)
      @app = app
    end

def call(env)
      env[&quot;PATH_INFO&quot;] = env[&quot;SCRIPT_NAME&quot;].to_s + env[&quot;PATH_INFO&quot;].to_s
      env[&quot;SCRIPT_NAME&quot;] = &quot;&quot;
      @app.call(env)
    end
  end
</pre>
<p>
Of course, use this only when your app runs at &quot;/&quot;.
</p>
<p>
Since lighttpd 1.4.23, you also can use the &quot;fix-root-scriptname&quot;
flag in fastcgi.server.
</p>
</li>
</ul>
<h1>Known conflicts regarding parameter parsing</h1>
<pre>
 * Many users have differing opinions about parameter parsing. The current
   parameter parsers in Rack are based on a combination of the HTTP and CGI
   specs, and are intended to round-trip encoding and decoding. There are some
   choices that may be viewed as deficiencies, specifically:
    - Rack does not create implicit arrays for multiple instances of a parameter
    - Rack returns nil when a value is not given
    - Rack does not support multi-type keys in parameters
   These issues or choices, will not be fixed before 2.0, if at all. They are
   very major breaking changes. Users are free to write alternative parameter
   parsers, and their own Request and Response wrappers. Moreover, users are
   encouraged to do so.
</pre>

</div>

</div>

<div id="validator-badges">
  <p><small><a href="http://validator.w3.org/check/referer">[Validate]</a></small></p>
</div>

</body>
</html>

Cancel