MSXML2 Post requests are not working anymore with Domino 8.5.1

HCL Domino Domino Forum
1

With the “MS XML Parser” you can get and POST Domino Forms automatically,e.g like this:

AServer := createOleObject(‘MSXML2.XMLHTTP.3.0’);

AServer.OPEN(‘POST’,‘dominoserver.de’, FALSE);

    AServer.setRequestHeader('Content-Type', 'application/x-www-form-urlencoded; charset=windows-1252');



    AParams := TStringlist.create;

    AParams.Values['name']         := '_DataFormular';

    AParams.Values['__Click']      := '0';

    AParams.Values['IsAutoPost']   := '1';

    AParams.Values['Line_1_Text']  :=  APublischerRule.OwnerItem.getitem.OIDHex;

    AParams.Values['Line_5_Text']  := urlencode(ADataRec.FirmenName,false);

    AParams.Values['Line_6_Text']  := urlencode(ADataRec.KontaktPerson,false);

    AParams.Values['Line_7_Text']  := urlencode(ADataRec.PLZ,false);

    AParams.Values['Line_8_Text']  := urlencode(ADataRec.Ort,false);

    ...



    AServer.send(AParams.Text);



    Result     := AServer.status = 200;

    Msg        := AServer.ResponseText;

Since update to Domino Server 8.5.1 this POST requests will not be saved anymore.

The domlog.nsf shows the POST as well as before.

The log.nsf and neither the console doesnt show any errors.

But “only” the document is missing in the nsf.

Can somebody confirm this ?

Is this a bug or a new security feature in 8.5.1 ?

It was still running without any problems in 8.5 FP1

2

Subject: POST parameters syntax

Hello,

We noticed a similar problem. Since update to Domino Server 8.5.1 our POST requests were not saved anymore.

We use a Javascript library to make AJAX requests. We passed POST parameters as a string like this one : “&param1=value1&param2=value2” (which is not correct in this function specification but it worked ;p) instead of “param1=value1&param2=value2”.

We think 8.5.1 is less permissive and doesn’t permit this syntax.

You should check “AParams.Text” value. Maybe it begins with an “&” character.

Hope this help.

Frodon

3

Subject: HTTPS Post Fails also

We have also just solved this problem after moving to 851fp1.

Removing the extra & at the start of the PostData fixed the problem

Thanks

Chris