… (for instance: NPH ("Non-Parsed Header") scripts as described in Section 5 of [RFC3875] ). Servers and proxies implementing Basic authentication need to store user passwords in some form in order to authenticate a request. These passwords ought to be stored in such a way that a …

…nment that is vulnerable to code injection attacks. For example, a CGI script [ RFC3875 ] echoing user input could allow the inclusion of untrusted scripts that could be executed in an otherwise trusted environment. This threat scenario is subject to security considerations that …

… (for instance: NPH ("Non-Parsed Header") scripts as described in Section 5 of [RFC3875] ). Servers and proxies implementing Basic authentication need to store user passwords in some form in order to authenticate a request. These passwords ought to be stored in such a way that a …

…nment that is vulnerable to code injection attacks. For example, a CGI script [ RFC3875 ] echoing user input could allow the inclusion of untrusted scripts that could be executed in an otherwise trusted environment. This threat scenario is subject to security considerations that …

…to code injection attacks. For example, a Common Gateway Interface (CGI) script RFC3875 echoing user input could allow the inclusion of untrusted scripts that could be executed in an otherwise trusted environment. This threat scenario is subject to security considerations that ar…

… (for instance: NPH ("Non-Parsed Header") scripts as described in Section 5 of [RFC3875] ). Servers and proxies implementing Basic authentication need to store user passwords in some form in order to authenticate a request. These passwords ought to be stored in such a way that a …

…GI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [ RFC3875 is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen ("-…

…CGI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [RFC3875] , is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen …

…GI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [ RFC3875 is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen ("-…

…GI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [ RFC3875 is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen ("-…

…CGI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [RFC3875] , is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen …

…GI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [ RFC3875 is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen ("-…

…GI) mapping of protocol- specific meta-variables, defined by Section 4.1.18 of [RFC3875], is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen (…

…GI) mapping of protocol- specific meta-variables, defined by Section 4.1.18 of [RFC3875], is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen (…

…GI) mapping of protocol-specific meta-variables, defined by Section 4.1.18 of [ RFC3875 is applied to received header fields that do not correspond to one of CGI's standard variables; the mapping consists of prepending "HTTP_" to each name and changing all instances of hyphen ("-…