Webware for Python

Looking at the include path I assume its an Apache 1.2.6
Not sure if mod_webkit can handle that; as far as I know
its 1.3.x only..

Paul

At 17:28 -0400 22-08-2002, Love, Jay wrote:
>Are you using Apache 1.3.X?  I don't think it's been ported to 2.0 yet.
>
>Jay
>
>>  -----Original Message-----
>>  From: Tracy Ruggles [mailto:trace@...]
>>  Sent: Thursday, August 22, 2002 5:11 PM
>>  To: Webware
>>  Subject: [Webware-discuss] mod_webkit install on freebsd?
>>
>>
>>  Hi, I'm trying to make the mod_webkit apache module, but it
>>  seems to be choking on compiling mod_webkit.c...  Does anyone
>>  know what might be going wrong?
>>
>>  I'm using Python 2.2.1, WebKit 0.7, on FreeBSD:
>>      (FreeBSD 4.4-RELEASE (VKERN) #7: Fri Aug  9 08:53:32 MDT 2002)
>>
>>  Thanks for any help...
>>  --Tracy
>>
>>  ----------
>>
>>  axionf% make
>>  /usr/local/bin/apxs -o mod_webkit.so -c    mod_webkit.c marshal.c
>>  gcc -DSTATUS -DVSERV -DISERVER -DSTANDALONE -DFRONTPAGE
>>  -funsigned-char -fpic -DSHARED_MODULE
>  > -I/usr/local/apache/1.2.6/include  -c mod_webkit.c

On August 22, 2002 02:11 pm, Tracy Ruggles wrote:
> I'm using Python 2.2.1, WebKit 0.7, on FreeBSD:
>     (FreeBSD 4.4-RELEASE (VKERN) #7: Fri Aug  9 08:53:32 MDT 2002)

On August 23, 2002 12:58 am, Paul Jongsma wrote:
> Looking at the include path I assume its an Apache 1.2.6
> Not sure if mod_webkit can handle that; as far as I know
> its 1.3.x only..

Tracy,
for security reasons alone you should upgrade your system to FreeBSD=20
RELENG_4_6 and the current /usr/ports tree, then install Apache 1.3.26 fr=
om=20
/usr/ports/www/apache13-modssl/.  I had no problems installing mod_webkit=
=20
from that point.
Tavis

Hi,
does anyone here know how to access the fragment part of=20
http://your.own.server/some/path/somePage.py?query=3D1234#fragment
from a servlet?  request.environ()['REQUEST_URI'] doesn't include it.  Is=
 this=20
possible from a cgi-like interface at all?
Tavis

On Fri, Aug 23, 2002 at 09:53:40AM -0700, Tavis Rudd wrote:
> does anyone here know how to access the fragment part of 
> http://your.own.server/some/path/somePage.py?query=1234#fragment
> from a servlet?  request.environ()['REQUEST_URI'] doesn't include it.  Is this 
> possible from a cgi-like interface at all?

Shouldn't the fragement come before the query string?

-- 
-Mike (Iron) Orr, iron@...  (if mail problems: mso@...)
   http://iron.cx/     English * Esperanto * Russkiy * Deutsch * Espan~ol

On 23/8/02 at 9.40a, Tavis Rudd (tavis@...) said:

>On August 22, 2002 02:11 pm, Tracy Ruggles wrote:
>> I'm using Python 2.2.1, WebKit 0.7, on FreeBSD:
>>     (FreeBSD 4.4-RELEASE (VKERN) #7: Fri Aug  9 08:53:32 MDT 2002)
>
>On August 23, 2002 12:58 am, Paul Jongsma wrote:
>> Looking at the include path I assume its an Apache 1.2.6
>> Not sure if mod_webkit can handle that; as far as I know
>> its 1.3.x only..
>
>Tracy,
>for security reasons alone you should upgrade your system to FreeBSD=20
>RELENG_4_6 and the current /usr/ports tree, then install Apache 1.3.26 fr=
>om=20
>/usr/ports/www/apache13-modssl/.  I had no problems installing mod_webkit=
>=20
>from that point.

Actually, my system is running Apache 1.3.26.  For some reason, though, the ipxs command from the makefile was somehow creating a gcc command with the -I...1.2.6 option in it.  I altered the include line in the makefile, but it included both the 1.2.6 and 1.3.26 versions.  

I couldn't figure out how to get rid of it, so I just hand compiled mod_webkit.c and marshal.c, then ran "ld -G -o mod_webkit.so ..." on it and it seemed to work.  I just now modified my apache config file and got it working.

Thanks for the pointers!

--Tracy

On August 23, 2002 10:41 am, Mike Orr wrote:
> On Fri, Aug 23, 2002 at 09:53:40AM -0700, Tavis Rudd wrote:
> > does anyone here know how to access the fragment part of
> > http://your.own.server/some/path/somePage.py?query=3D1234#fragment
> > from a servlet?  request.environ()['REQUEST_URI'] doesn't include it.=
  Is
> > this possible from a cgi-like interface at all?
>
> Shouldn't the fragement come before the query string?

Not according to the specs and how the browsers work.

> Hi,
> does anyone here know how to access the fragment part of
> http://your.own.server/some/path/somePage.py?query=3D1234#fragment
> from a servlet?  request.environ()['REQUEST_URI'] doesn't include it.  Is=
>  this=20
> possible from a cgi-like interface at all?
> Tavis

I don't believe this is possible. Running tcpdump, my browser (ie6) does not 
even make a new request if I add a fragment to a previously loaded page, and 
does not include the fragment in the HTTP request if it is a new request.

Additionally, making a raw telnet connection to port 80 and requesting (for 
example)

GET /index.html#frag HTTP/1.0

Causes an apache error, about illegal characters in the request, so I would 
imagine all browsers keep the fragment to themselves.

Luke


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

On Fri, 2002-08-23 at 13:33, Luke Opperman wrote:
> > Hi,
> > does anyone here know how to access the fragment part of
> > http://your.own.server/some/path/somePage.py?query=3D1234#fragment
> > from a servlet?  request.environ()['REQUEST_URI'] doesn't include it.  Is=
> >  this=20
> > possible from a cgi-like interface at all?
> > Tavis
> 
> I don't believe this is possible. Running tcpdump, my browser (ie6) does not 
> even make a new request if I add a fragment to a previously loaded page, and 
> does not include the fragment in the HTTP request if it is a new request.
> 
> Additionally, making a raw telnet connection to port 80 and requesting (for 
> example)
> 
> GET /index.html#frag HTTP/1.0
> 
> Causes an apache error, about illegal characters in the request, so I would 
> imagine all browsers keep the fragment to themselves.

You're definitely right on this.  I wonder, though, if there's a way to
access the fragment through JavaScript?  I can't remember why, but I've
wanted to do this before.

  Ian

On August 23, 2002 01:42 pm, Ian Bicking wrote:
> You're definitely right on this.  I wonder, though, if there's a way to
> access the fragment through JavaScript?  I can't remember why, but I've
> wanted to do this before.

window.location.hash.

I'm working on a page that has a listing of many items, one per row.  Eac=
h row=20
has a form so that the user can modify metadata.  When the user saves the=
ir=20
changes the forms will post back to the same page.  I wanted to reload th=
e=20
page on the specific row the user was looking at, rather than reloading a=
t=20
the top of the page.  If I set each form's action on the WebKit side I=20
couldn't do that as I didn't have access to the #fragment.  In the end, I=
=20
used the form's onSubmit event handler to set theForm.action =3D=20
window.location.href before submitting.

On Fri, 2002-08-23 at 15:56, Tavis Rudd wrote:
> On August 23, 2002 01:42 pm, Ian Bicking wrote:
> > You're definitely right on this.  I wonder, though, if there's a way to
> > access the fragment through JavaScript?  I can't remember why, but I've
> > wanted to do this before.
> 
> window.location.hash.
> 
> I'm working on a page that has a listing of many items, one per row.  Each row 
> has a form so that the user can modify metadata.  When the user saves their 
> changes the forms will post back to the same page.  I wanted to reload the 
> page on the specific row the user was looking at, rather than reloading at 
> the top of the page.  If I set each form's action on the WebKit side I 
> couldn't do that as I didn't have access to the #fragment.  In the end, I 
> used the form's onSubmit event handler to set theForm.action = 
> window.location.href before submitting.

I was doing something like this.  It was a pain to get working, but it
involved hitting a link that make a popup window go up, and it saved
where the document was scrolled to.  Then when you submitted in the form
in the popup window, it reloaded the master window (with a new URL, to
force reload), which involved a little (dynamic) Javascript that got run
on page load, which rescrolled the page back to where it was.  If you
want it I can dig up the code -- not much code, and I remember the were
problems which I don't know if I fixed (on some platforms), but it
seemed like the best way to do it.  

  Ian

Remember the web application testing discussion? Well, I listened. It just
took me a while......

Thank you, Chuck (and many others from that thread here so long ago). Your
suggestions made Puffin much much better.

Keyton


Welcome to the Puffin Automation Framework Version 0.9

Download Here:
http://www.puffinhome.org/download.cgi?file=puffin.zip

More Information and Setup Instructions Here:
http://puffinhome.org/README

Introduction
What is the Puffin Automation Framework and how does it differ
from the earlier versions of Puffin?

The Puffin Automation Framework (Puffin) picks up where the
original Puffin web application testing tool stopped. You can
still use Puffin to do web testing (and it's even easier and
more powerful than it was before). But now, you can do a great
deal more!

Changes in Version 0.9:
1) Total architectural rewrite.
2) Extendable now in Python.
3) Not backwards compatible.
4) More flexibility in plan.xml files (repeats, etc).
5) Great new reporting features (HTML/XML).
6) Better failed task alerting (email, file log, etc).

Caveats:
1) 0.9 is a *HUGE* change from previous versions (i.e. not backwards
compatible).
2) The old Puffin docs are out of date (though still useful).
3) More docs are on their way -- I promise.

Thanks:
1) Brian Norman. Tirelessly helping me server the GNU/Linux and UNIX
communities.
2) Bryan Richard. HTML help. General support.
3) Ernie Hershey. For the demo app, etc.
4) Others!

And, as always, contact me immediately should you run into any
problems.

Keyton Weissinger
keyton@...

Remember the web application testing discussion? Well, I listened. It just
took me a while......

Thank you, Chuck (and many others from that thread here so long ago). Your
suggestions made Puffin much much better.

Keyton


Welcome to the Puffin Automation Framework Version 0.9

Download Here:
http://www.puffinhome.org/download.cgi?file=puffin.zip

More Information and Setup Instructions Here:
http://puffinhome.org/README

Introduction
What is the Puffin Automation Framework and how does it differ
from the earlier versions of Puffin?

The Puffin Automation Framework (Puffin) picks up where the
original Puffin web application testing tool stopped. You can
still use Puffin to do web testing (and it's even easier and
more powerful than it was before). But now, you can do a great
deal more!

Changes in Version 0.9:
1) Total architectural rewrite.
2) Extendable now in Python.
3) Not backwards compatible.
4) More flexibility in plan.xml files (repeats, etc).
5) Great new reporting features (HTML/XML).
6) Better failed task alerting (email, file log, etc).

Caveats:
1) 0.9 is a *HUGE* change from previous versions (i.e. not backwards
compatible).
2) The old Puffin docs are out of date (though still useful).
3) More docs are on their way -- I promise.

Thanks:
1) Brian Norman. Tirelessly helping me server the GNU/Linux and UNIX
communities.
2) Bryan Richard. HTML help. General support.
3) Ernie Hershey. For the demo app, etc.
4) Others!

And, as always, contact me immediately should you run into any
problems.

Keyton Weissinger
keyton@...