>Number: 1562 >Category: os-sco >Synopsis: BrowserMatch variable cause CGI failure: 'variable=1: is not >an identifier' - SCO /bin/sh >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Dec 16 11:30:00 PST 1997 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2.4 >Environment: $ uname -a btsu4 btsu4 3.2 2 i386 (SCO 3.2v4.2)
Set Release Notes --- ------- ----- NET382D Enhanced TCP/IP 1.2.1 Dr 4.0.0a removed Console Keyboard Driver SLS 2.0.0a installed SCO NFS Development System 1.2.0j installed SCO NFS Runtime System 1.2.0m installed ClusStar Async Device Driver 5.4.0 partially installed Software Development System 3.2.4n installed Specialix RIO Intelligent I/O dr 2.04T-1.1 partially installed 3Com EtherLink III Driver Releas 1.1 removed SCO LLI Driver Disk 3.1.0j installed SCO TCP/IP Runtime System 1.2.1o installed Comtrol RocketPort Driver v1.2 1.2 installed SCO UNIX System V Extended Utili 3.2.4l installed SCO UNIX System V Operating Syst 3.2.4l installed (prd = unixos) 3.2.4l installed >Description: If the BrowserMatch line advised for getting round the MSIE 4/Java/HTTP 1.1 bug fails on a Browser match (not specific to MSIE - one can change the string to get the same effect on Lynx), there is a 500 error with the following in the log file: downgrade-1.0=1: is not an identifier [Tue Dec 16 17:25:47 1997] access to /usr/bts/wrm/cgi-bin/wrm/repdefinition failed for columbine.bts.co.uk, reason: Premature end of script headers >How-To-Repeat: Access /cgi-bin/test-cgi (NCSA one) after having applied the MSIE 4 workaround and with your browser string set to match the browser used. >Fix: Experiments indicate that bash will accept: export fred=jim but /bin/sh fails thus: $ export fred=jim fred=jim: is not an identifier $ I'd therefore surmise that Apache is assuming an extension in the shell language. (Also, the string is obviously in /bin/sh, as confirmed by strings, but not in apache). Unfortunately the logistics of rebuilding Apache are a bit fraught (it has to be sent to another office, who have the TCP/IP development kit) and for marketing (not technical) reasons, Netscape server is being used in the system to be sold, so actually testing this is outside my budget (I can work round it by disabling HTTP/1.1 in MSIE) >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
