One Hat Cyber Team
Your IP :
216.73.216.115
Server IP :
194.44.31.54
Server :
Linux zen.imath.kiev.ua 4.18.0-553.77.1.el8_10.x86_64 #1 SMP Fri Oct 3 14:30:23 UTC 2025 x86_64
Server Software :
Apache/2.4.37 (Rocky Linux) OpenSSL/1.1.1k
PHP Version :
5.6.40
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
home
/
mellit
/
doc
/
Edit File:
TESTING.txt
Testing ------- As supplied, the scripts should be accessible through http://yourwebserver/cvs-web/read/cvswebread.cgi You should try this URL first. If you get errors getting it to start, first check your Apache error log (apache/logs/error.log) If this doesn't solve it, try testing from the command line. To test from the command line you must first move into the directory containing the script. The script will work out what location it is in and use this location to determine the location of the library files. e.g. cd cvs-web/read/ perl cvsweb.cgi (waiting for HTTP query on standard input) Then type return, followed by any (i.e. optional) GET parameters followed by return followed by the end-of-file character for your platform, Ctrl-D on UNIX, Ctrl-Z on Win32. Finally, the following log files can be very useful. -> CVSWEBCLIENT Script Logs: cvs-web/temp/cvswebedit.out cvs-web/temp/cvswebview.out These will be written to with diagnostics telling you what was returned to the webserver. -> Apache Script Log: Additionally if you enabled the ScriptLog in httpd.conf, try looking at that. cvs-web/temp/script.out -> Audit Log [This contains the CVS commands run] cvs-web/temp/auditlog.txt Common Error Messages and where to look to fix them --------------------------------------------------- Internal Server Error -> Stop the webserver -> Look at error.log Not the output you expected -> Look at script.out, especially the %stderr% stream Can't locate CGI/Base.pm in ... -> Make sure you are running the script from within its directory. THIS IS IMPORTANT BECAUSE IT ASSUMES THIS TO FIND THE libs directory. Test Cases ---------- What happens if you give a URL to check in with to a file that has not been checked out? Are newlines etc accepted in the comments box? Does a big download/upload work? Does the locking work? Does the unlocking work? (after unlock and after commit) What should cvs status say after cvs admin -l? Does the upload refreshing page work? Is the Audit Log used everywhere? Is it used in cvswebcreate? Ideally all the test cases would be automated. Until that happens, here is a manual test cycle! 1) Open cvs-web/read/cvsweb.cgi -> You should see the root directory of your repository 2) Click 'Create file' -> This should allow you to create a file 3) Type 'a-file' as the filename Type 'a comment' as the comment Leave the vendor and release fields as they are Click submit 4) You should be taken to the File Add Results page. This should show you whether the add was successful. @On Win2000, this showed no results. 5) Generic considerations ---------------------- Can the system handle really big files? Can we teach the web user the cvs syntax as we go along? Do not use single quotes in the command line. This screws NT as it does not recognise them! Code Conventions ---------------- The per-program logs are useful because of the do_logs() calls. If you are in doubt of what is happening, find the do_logs call that makes the entry in the log file. Programmatically testing. ------------------------- The CGI libs have a testing mode in which you can emulate a browser doing a GET command by specifying the parameters on the command line. Hence, you can do: C:\DATA\Mcleaver\New\cvswebclient\cvs-web\edit>perl cvswebedit.cgi edit=show-status Set-Cookie: cvswebedit=mcleaver; path=/C:/DATA/Mcleaver/New/cvswebclient/cvs-web /cvswebedit.cgi Content-type: text/html <HTML><HEAD><TITLE>CVSWebEdit ownerships in repository</TITLE></HEAD> <BODY> <H2>CVSWebEdit ownerships in repository</H2> <H2></H2><pre> <HR><h2>Users owning file:</h2> <UL> </UL><HR><h2>Files belonging to users:</h2> <UL> </UL><P> Return to viewing <A HREF='/cvs-web/read/cvswebread.cgi'>repository</A> <P> </BODY></HTML> DON'T BOTHER WITH THE TESTS DIRECTORY. IT IS ALL OBSOLETE. Other stuff: ------------ NOTE: If you have problems, it may make sense to remove the perl -s option and run the scripts manually.
Simpan