with HTMLForm1 do
    begin
    url := 'modules/ewbmodule?SessionAddress='+SessionAddress+
           '&SessionUser='+SessionUser+
           '&SessionPassword='+SessionPassword+
           '&SessionDb='+SessionDb+
           '&ContactID='+IntToStr(v_contact_ID)+
           '&Action=ResetPaswoord'+
           '&ResetCode='+TRIM(EdtResetCode.text)+
           '&Paswoord='+TRIM(PasswordEdit1.Text);
    output:=Browser1;
    submit;
    end;

does TPasswordEdit no accept special characters?    for example:     &é"'(§è!

Paul.

Paul Waegemans wrote:

>             '&Paswoord='+TRIM(PasswordEdit1.Text);
>      output:=Browser1;
>      submit;
>      end;
>
> does TPasswordEdit no accept special characters?    for example:     &é"'(§è!

Two things - first, the parameter is "paswoord" in your code, and not "password" as spelled in English. If that is how you spell it, then fine, but just making sure - far too many times I've spent an hour chasing some non-obvious parameter typo.

Second, it will do, but you are going to be doing URL encoding on the string, so it probably gets sent as %1234 instead of the character. Thus you have to decode it to get it back to the proper character, and make sure it is in the right character set too.

I find it sensible to log at both ends for this sort of thing. Or, to be careful that you don't fix it and break existing passwords. The existing ones may actually be "pass%1234word".

--

Matthew Jones

Did you try a simple:

ShowMessage(TPasswordEdit.Text);   This works - so it is not the TPasswordEdit.

On the server side you need to URL_Decode the request.

As Matthew said - double check variable spelling...

Walter

I would use Params rather than relying on the assumption you can pass unicode on the URL.

Erick
EWB Programming Books and Component Library
http://www.erickengelke.com

Paul,

<< does TPasswordEdit no accept special characters?    for example:     &é"'(§è! >>

What problem are you having, exactly ?

EWB encodes all parameters in URLs when using the TServerRequest component, the browser encodes all parameters in URLs when using HTML forms, and the EWB Web Server decodes all URL parameters on the server side, so there shouldn't be any issues with what you're doing.

Tim Young
Elevate Software
www.elevatesoft.com