RE: Form submittal and http_auth problem

On 2003-07-28, "Grzegorz Adam Hankiewicz" <[email protected]> wrote: 
>On 2003-07-25, "Molek, Gordon" <[email protected]> wrote:
> > Ok, here's another issue I just hit.  If I have a password
> > protected web page, I can use http_auth to set the login and
> > password and I'll get an initial 401 error, and tclwebtest
> > will retry with the authentication data and the page will load.
> > So far so good.
> > 
> > However, if I have a form on that page and try to post the form,
> > the post will generate a 401 error, but tclwebtest doesn't re-post
> > the form with the authentication data, but rather does a "get"
> > of the data which results in a 404 error.
> 
> Looks like an omission. Does the following patch make it work?
> 
> Index: lib/tclwebtest.tcl
> ===================================================================
> RCS file: /cvsroot/tclwebtest/tclwebtest/lib/tclwebtest.tcl,v
> retrieving revision 1.40
> diff -u -r1.40 tclwebtest.tcl
> --- lib/tclwebtest.tcl  4 Jun 2003 17:40:38 -0000       1.40
> +++ lib/tclwebtest.tcl  28 Jul 2003 07:23:34 -0000
> @@ -2329,7 +2329,7 @@
>                  if { $inject_string != "" } {
>                      set ::tclwebtest::http_auth_string $inject_string
>                      log "Retrying url with preset authentication"
> -                    eval "do_request $nocomplain_option
$followequiv_option $url"
> +                    eval "do_request $nocomplain_option
$followequiv_option $url
>$query_key_values"
>                  } else {
>                      log "This url requires http authentication set
through the http_auth
>command"
>                      eval $failure_treatement
> 
> -- 
>  Grzegorz Adam Hankiewicz, [email protected] Tel: +34-94-472 35 89.
>  eFaber SL, Maria Diaz de Haro, 68, 2         http://www.efaber.net/
>  48920 Portugalete, Bizkaia (SPAIN)

First, let me apologize for not being able to respond properly in threads,
but I have
yet to receive any of the mailing list e-mails in my in-box.  I don't know
if they're
being filtered somewhere or what.

The above fix seems to solve the problem with one additional change,
basically surrounding
the "$query_key_values" argument with curly braces, e.g.,
"{$query_key_values}".

Thanks,

Gordon Molek


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01