Apache-RewritingProxy
view release on metacpan or search on metacpan
REFERER the client sees. This needs to be fixed soon. Should be fixed before
the next commit.
----------------------------
revision 1.9
date: 1999/12/27 17:04:19; author: khhaga01; state: Exp; lines: +0 -5
Took out the part of the cookie code that named the
cookie nnnnnnnnnnnn where the n's are part of the IP address.
The problem was that 136.165.1.128 would share a cookie jar with
136.165.11.28 and that would be bad.
----------------------------
revision 1.8
date: 1999/12/14 19:39:53; author: khhaga01; state: Exp; lines: +32 -25
Fixed a number of bugs relating to special characters such as
(,*,+,),% being in the url being parsed.
Fixed a problem I had parsing some sites with a huge first line of
text. I wasn't printing out the headers properly and that line was
ignored. I only noticed it when the first line was huge.
Still missing any handling of cookies set in the Meta HTTP-Equiv tag.
----------------------------
revision 1.7
date: 1999/12/13 20:54:43; author: khhaga01; state: Exp; lines: +25 -13
Fixed the Documentation to reflect the other modules that are needed.
Apache::Util
Apache::Table
are really needed for this thing to work. The Makefile will need to
reflect this also.
----------------------------
revision 1.6
date: 1999/12/13 20:40:58; author: khhaga01; state: Exp; lines: +47 -42
Added Tim DiLauro's suggestions to fix the hardcoded
<Location > bug. Basically this means that one can specify any
<Location Foo> Directive when configuring RewritingProxy and it should now
work.
Also added plenty of stuff to make cookies work a little better.
I fixed the version numbering to be consistent with the numbers under which
these files are being uploaded to CPAN. This is really 0.5. THere
had been some version cornfusion since I had cvs dump its own version
tag into the file. Bad move.
----------------------------
revision 1.5
date: 1999/12/08 22:43:48; author: khhaga01; state: Exp; lines: +114 -7
Added bunches of code to build a cookie database on the server. This
database stays there and the client is sent one cookie with the name of
the file. When a request is made, the proxy sends only the cookies
that should go to the remote web server. This works somewhat but is
not 100% and is not very elegant. The file locking for the cookie
database file is very primitive.
----------------------------
revision 1.4
date: 1999/11/05 20:13:20; author: khhaga01; state: Exp; lines: +3 -1
*** empty log message ***
----------------------------
revision 1.3
date: 1999/11/05 20:10:28; author: khhaga01; state: Exp; lines: +32 -2
Fixed some of the meta refresh pages. I now see that
tag and rewrite the URL properly. Cookies are still a
major problem. It looks like I may have to build some
sort of cookie database and give the client a cookie poining
to his/her entry in that database. Looks like the safest way to go.
----------------------------
revision 1.2
date: 1999/11/04 20:34:39; author: khhaga01; state: Exp; lines: +5 -0
Added the version number and some other silliness I didn't know about
real perl modules. Fixed Makefile.PL to actually check for the necessary
modules.
----------------------------
revision 1.1
date: 1999/11/04 20:09:00; author: khhaga01; state: Exp;
RewritingProxy.pm created. Renamed from invisibleProxy.pm which
was not a terribly informative or relavant name.
=============================================================================
( run in 1.975 second using v1.01-cache-2.11-cpan-39bf76dae61 )