我在bash中找到了以下CGI的工作示例。如果我将前两行更改为
#!/bin/sh
echo "Content-type: text/html\n\n"
脚本停止工作后,当我在浏览器中浏览脚本时,脚本底部声明的'foo','bar'和'foobar'消失。
任何想法如何让同一个例子与sh一起工作。实际上我需要在嵌入式设备上运行这样一个例子,我没有bash但是sh。
#!/bin/bash
echo -e "Content-type: text/html\n\n"
echo "
<html>
<body>
<form action="http://${HTTP_HOST}:${SERVER_PORT}${SCRIPT_NAME}?foo=1234" method="POST">
<input type="text" name="bar">
<textarea name="foobar"></textarea>
<input type="submit">
</form>"
# (internal) routine to store POST data
cgi_get_POST_vars()
{
# check content type
# FIXME: not sure if we could handle uploads with this..
[ "${CONTENT_TYPE}" != "application/x-www-form-urlencoded" ] && \
echo "Warning: you should probably use MIME type "\
"application/x-www-form-urlencoded!" 1>&2
# save POST variables (only first time this is called)
[ -z "$QUERY_STRING_POST" \
-a "$REQUEST_METHOD" = "POST" -a ! -z "$CONTENT_LENGTH" ] && \
read -n $CONTENT_LENGTH QUERY_STRING_POST
return
}
# (internal) routine to decode urlencoded strings
cgi_decodevar()
{
[ $# -ne 1 ] && return
local v t h
# replace all + with whitespace and append %%
t="${1//+/ }%%"
while [ ${#t} -gt 0 -a "${t}" != "%" ]; do
v="${v}${t%%\%*}" # digest up to the first %
t="${t#*%}" # remove digested part
# decode if there is anything to decode and if not at end of string
if [ ${#t} -gt 0 -a "${t}" != "%" ]; then
h=${t:0:2} # save first two chars
t="${t:2}" # remove these
v="${v}"`echo -e \\\\x${h}` # convert hex to special char
fi
done
# return decoded string
echo "${v}"
return
}
# routine to get variables from http requests
# usage: cgi_getvars method varname1 [.. varnameN]
# method is either GET or POST or BOTH
# the magic varible name ALL gets everything
cgi_getvars()
{
[ $# -lt 2 ] && return
local q p k v s
# get query
case $1 in
GET)
[ ! -z "${QUERY_STRING}" ] && q="${QUERY_STRING}&"
;;
POST)
cgi_get_POST_vars
[ ! -z "${QUERY_STRING_POST}" ] && q="${QUERY_STRING_POST}&"
;;
BOTH)
[ ! -z "${QUERY_STRING}" ] && q="${QUERY_STRING}&"
cgi_get_POST_vars
[ ! -z "${QUERY_STRING_POST}" ] && q="${q}${QUERY_STRING_POST}&"
;;
esac
shift
s=" $* "
# parse the query data
while [ ! -z "$q" ]; do
p="${q%%&*}" # get first part of query string
k="${p%%=*}" # get the key (variable name) from it
v="${p#*=}" # get the value from it
q="${q#$p&*}" # strip first part from query string
# decode and evaluate var if requested
[ "$1" = "ALL" -o "${s/ $k /}" != "$s" ] && \
eval "$k=\"`cgi_decodevar \"$v\"`\""
done
return
}
# register all GET and POST variables
cgi_getvars BOTH ALL
echo "<pre>foo=$foo</pre>"
echo "<pre>bar=$bar</pre>"
echo "<pre>foobar=$foobar</pre>"
echo "</body>
</html>"
更新1:
sh -x script
返回以下内容:
+ echo Content-type: text/html\n\n
Content-type: text/html
+ echo
<html>
<body>
<form action=http://:?foo=1234 method=POST>
<input type=text name=bar>
<textarea name=foobar></textarea>
<input type=submit>
</form>
<html>
<body>
<form action=http://:?foo=1234 method=POST>
<input type=text name=bar>
<textarea name=foobar></textarea>
<input type=submit>
</form>
+ cgi_getvars BOTH ALL
+ [ 2 -lt 2 ]
+ local q p k v s
+ [ ! -z ]
+ cgi_get_POST_vars
+ [ != application/x-www-form-urlencoded ]
+ echo Warning: you should probably use MIME type application/x-www-form-urlencoded!
Warning: you should probably use MIME type application/x-www-form-urlencoded!
+ [ -z -a = POST -a ! -z ]
+ return
+ [ ! -z ]
+ shift
+ s= ALL
+ [ ! -z ]
+ return
+ echo <pre>foo=</pre>
<pre>foo=</pre>
+ echo <pre>bar=</pre>
<pre>bar=</pre>
+ echo <pre>foobar=</pre>
<pre>foobar=</pre>
+ echo </body>
</html>
</body>
</html>
答案 0 :(得分:2)
与POSIX规范相比,Bash有很多扩展,而你的脚本正在使用其中的一些。你的/bin/sh
显然不是bash(可能是ash,dash,mksh或者其他东西)并且没有这些扩展名。您必须完成脚本并根据sh或POSIX specification的文档检查每个构造。
Quckly look:
function cgi_get_POST_vars()
:函数关键字不应该在那里,并且左括号应该在同一行。read -n $CONTENT_LENGTH QUERY_STRING_POST
:read(shell builtin)在POSIX中没有-n选项。t="${1//+/ }%%"
,h=${t:0:2}
:Bourne不支持这些修饰符。但可能会有更多。
编辑:
echo
是shell之间最不兼容的命令。该标准只是说\
的行为是实现定义的。您必须使用printf
代替。答案 1 :(得分:1)
function
关键字的函数声明与Bourne脚本不兼容。 sh
的正确语法是
cgi_get_POST_vars() {
...
}
答案 2 :(得分:0)
对这样的脚本也要非常小心。此参数解析器容易受到shell注入攻击。例如,如果传递了一个变量:
cgi-bin/myscript.cgi&foo=bar`ls`bar
我相信“ls”命令将在参数解码期间执行。你可以想象比“ls”更具破坏性的命令。还要考虑如果敌对用户传递的参数&PATH=""
将会发生什么。这个东西很难做到,如果你正在处理一个嵌入式设备,如果web服务器以root权限运行,我不会感到惊讶。