But how did this got broken? Is this due to an update from Jaggery? This is a fundamental flaw & we are trying to do a patch release.
Madhuka - welcome back ;-) ... On Thu, Jul 24, 2014 at 4:33 AM, madhuka udantha <[email protected]> wrote: > Hi, > > You can used 'loadConfig()' to load carbon config file and read 'offset' > value. > This can be helpful for the $subject > > var conf = carbon.server.loadConfig(<config file>) > > > > On Thu, Jul 24, 2014 at 3:21 PM, Evanthika Amarasiri <[email protected]> > wrote: > >> Hi All, >> >> With API-M 1.7.1, we noticed that if we set a port offset, we need to >> change the site.json files of the publisher jaggery app. If you don't >> change these files, when you access the publisher URL, you are redirected >> back to https://{default_host}:{default_port}/publisher page. i.e.:- >> https://localhost:9443/publisher. >> >> So every time you set a port offset to your server, a user will have to >> change the site.json file manually to access publisher URL. >> >> My concern is, why are we introducing additional configuration changes >> like these? If we introduce changes, we need to make sure that they work >> out of the box, without a person having to change any files manually. >> >> Also, if you set a port offset, API console (Swagger) does not work out >> of the box. You need to change the port you give in >> *Access-Control-Allow-Origin* parameter. >> >> Regards, >> Evanthika Amarasiri >> Senior Technical Lead - Quality Assurance >> Mobile: +94773125935 >> >> wso2.com Lean Enterprise Middleware >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Cheers, > Madhuka Udantha > http://madhukaudantha.blogspot.com > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
