Yes, it looks like that. in LzHTTPDataProvider.lzs I found this code:
if (secure) {
tloader.baserequest = lz.Browser.getBaseURL(secure,
dreq.secureport);
tloader.secureport = dreq.secureport;
}
tloader is an instance of LzHTTPLoader class, and for the DHTML
runtime (LzHTTPLoader.js), the property secureport is not defined.
On Tue, May 3, 2011 at 6:48 PM, Henry Minsky <[email protected]> wrote:
> I doubt that feature has been tested for a long time... easy to believe it
> is just broken.
>
> On Tue, May 3, 2011 at 12:37 PM, Raju Bitter
> <[email protected]> wrote:
>>
>> I'm looking into http://jira.openlaszlo.org/jira/browse/LPP-9923, and
>> it seems the secureport attribute for datasets is not used when making
>> requests. When I set the @secureport for a dataset making a request to
>> an https resource, setting the @secureport to a port different from
>> 443 doesn't lead to any errors. The request is still made to the port
>> 443.
>
>
>
> --
> Henry Minsky
> Software Architect
> [email protected]
>
>
>
