#1 2014-09-10 05:34:57

cheemeng
Member
From: Malaysia
Registered: 2011-08-09
Posts: 61

TSQLHttpServer.AddServer does not follow TSQLHttpServerOptions

Hi Arnaud,

When the HttpServer is instantiated with useHttpApiRegisteringURI, all initial roots get registered.

However, subsequent calls to AddServer does not check this value and will pass False to AddUrl's aRegisterURI parameter, thereby causing those roots to not be automatically registered.

Suggestion:

1. Store the value of the initial TSQLHttpServerOptions.

2. mORMotHttpServer.pas line 419

        aServer.Model.Root,fPort,(aHttpServerSecurity=secSSL),fDomainName)<>NO_ERROR then

to

        aServer.Model.Root,fPort,(aHttpServerSecurity=secSSL),fDomainName,useHttpApiRegisteringURI=fHttpServerOptions)<>NO_ERROR then


Thanks!

Offline

#2 2014-09-10 07:42:03

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,182
Website

Re: TSQLHttpServer.AddServer does not follow TSQLHttpServerOptions

Done!
See http://synopse.info/fossil/info/2dc23da077

Thanks for the proposal!
smile

Offline

Board footer

Powered by FluxBB