Backendless Support
 
Works as Designed

nextPage URL http:/127.0.0.1:9000 on Standalone 3.6

Using Standalone 3.6, when I make a REST API from the console and from web client, the nextPage value is using url http://127.0.0.1:900 instead of the standalone server URL. I am not seeing this problem on developer.backendless.com.

  1. http://192.168.1.14:80/api/v1/data/bob?pageSize=1
  2. {
  3. "offset": 0,
  4. "data": [
  5. {
  6. "created": 1488520171000,
  7. "name": "sdf",
  8. "___class": "bob",
  9. "ownerId": null,
  10. "updated": null,
  11. "objectId": "47018260-4509-C4EF-FFF8-179C5F3BF500",
  12. "__meta": "{\"relationRemovalIds\":{},\"selectedProperties\":[\"created\",\"name\",\"___class\",\"ownerId\",\"updated\",\"objectId\"],\"relatedObjects\":{}}"
  13. }
  14. ],
  15. "nextPage": "http://127.0.0.1:9000/v1/data/bob?pageSize=1&offset=1";,
  16. "totalObjects": 10
  17. }

Leave a Comment

Comments (14)

photo
1

Hi Barry,

What is the exact version number so I can try reproducing with that build?

Regards,

Mark

photo
1

please fix typos

title: from http:/127.0.0.1:9000 to http://127.0.0.1:900

bofy: from http://127.0.0.1:900 to http://127.0.0.1:900

Thanks

photo
photo
1

You can find it in properties.ini located in the installation directory. The property name is:

base_stack_version

Mark

photo
1

base_stack_version=3.6.0-4

platform=linux-x64

photo
1

Thanks, I am getting an answer for you from the dev team.

Regards,

Mark

photo
photo
1

Hi Barry,

Can you please provide your backendless.config file? It's in the apps/backendless/conf directory. You can copy&paste it into this topic or send to support@backendless.com

photo
1

I made no changes to this file; the file is out of the box as I just downloaded the installerfrom the web site. The file you asked for was not in the backendless/conf folder but did find a file with that name in backendless/htdocs/conf

=====

<configuration>

<connections>

<connection>

<db>main_backendless</db>

<url>localhost:3306</url>

<login>bn_backendless</login>

<password>084ea38443</password>

<maxActive>10</maxActive>

<maxIdle>10</maxIdle>

<minIdle>5</minIdle>

<idleTimeout>600000</idleTimeout>

<idleTestPeriod>60000</idleTestPeriod>

<driver>com.mysql.jdbc.Driver</driver>

</connection>

<connection>

<db>backendless</db>

<url>localhost:3306</url>

<login>bn_backendless</login>

<password>084ea38443</password>

<maxActive>100</maxActive>

<maxIdle>100</maxIdle>

<minIdle>50</minIdle>

<idleTimeout>600000</idleTimeout>

<idleTestPeriod>60000</idleTestPeriod>

<driver>com.mysql.jdbc.Driver</driver>

</connection>

</connections>

<enableSynch>false</enableSynch>

<repository>

<relativeLocation>repo</relativeLocation>

<urlRelativeAddress>/VERSION/files/PATH/</urlRelativeAddress>

<resourcesRelativeLocation>resources</resourcesRelativeLocation>

<tmpRelativeLocation>resources/templates/</tmpRelativeLocation>

<createDefaultDomain>false</createDefaultDomain>

<minUnit>1024</minUnit>

</repository>

<console>

<rootUrl>http://192.168.1.9:80</rootUrl>;

<allowedHosts>

<host>http://localhost/</host>;

<host>https://localhost/</host>;

<host>http://127.0.0.2/</host>;

<host>https://127.0.0.2/</host>;

<host>http://192.168.1.14/</host>;

<host>http://www.192.168.1.14/</host>;

<host>https://192.168.1.14/</host>;

<host>https://www.192.168.1.14/</host>;

<host>http://192.168.1.9/</host>;

<host>http://www.192.168.1.9/</host>;

<host>https://192.168.1.9/</host>;

<host>https://www.192.168.1.9/</host>;

</allowedHosts>

</console>

<server>

<ipHeader>X-Real-IP</ipHeader>

<httpAddress>http://192.168.1.9:80/api</httpAddress>;

<host>192.168.1.9:80</host>

<pagingDefaultSize>100</pagingDefaultSize>

<dateFormats>

<!-- java.util.Date format -->

<dateFormat>EEE MMM dd HH:mm:ss zzz yyyy</dateFormat>

<!-- For Parse.com import. Order is sensitive -->

<dateFormat>yyyy-MM-dd'T'HH:mm:ss.SSS'Z'</dateFormat>

<dateFormat>MM/dd/yyyy HH:mm:ss 'GMT'z</dateFormat>

<dateFormat>MM.dd.yyyy HH:mm:ss 'GMT'z</dateFormat>

<dateFormat>MM-dd-yyyy HH:mm:ss 'GMT'z</dateFormat>

<dateFormat>MM/dd/yyyy HH:mm:ss z</dateFormat>

<dateFormat>MM.dd.yyyy HH:mm:ss z</dateFormat>

<dateFormat>MM.dd.yyyy HH:mm:ss</dateFormat>

<dateFormat>MM-dd-yyyy HH:mm:ss</dateFormat>

<dateFormat>MM/dd/yyyy HH:mm:ss</dateFormat>

<dateFormat>MM.dd.yyyy</dateFormat>

<dateFormat>MM-dd-yyyy</dateFormat>

<dateFormat useForResponse="true">MM/dd/yyyy HH:mm:ss 'GMT'Z</dateFormat>

<dateFormat>MM/dd/yyyy HH:mm</dateFormat>

<dateFormat>MM/dd/yyyy</dateFormat>

<dateFormat>dd/MMM/yyyy</dateFormat>

<dateFormat>dd-MMM-yyyy</dateFormat>

<dateFormat>EEEEE, d MMMMM yyyy</dateFormat>

<dateFormat>yyyy/MM/d/HH:mm:ss</dateFormat>

<dateFormat>yyyy-MM-dd'T'HH:mm:ss</dateFormat>

<dateFormat>EEEEE, MMMMM d, yyyy</dateFormat>

<dateFormat>MMMMM d, yyyy</dateFormat>

<dateFormat>yyyy M d</dateFormat>

<dateFormat>yyyyMMMd</dateFormat>

<dateFormat>yyyy-MMM-d</dateFormat>

<dateFormat>yyyy-M-d, E</dateFormat>

<dateFormat>'Date' yyyy-MM-dd</dateFormat>

<dateFormat>yyyy-MM-dd'T'HH:mm:ssZ</dateFormat>

<dateFormat>yyyy-MM-dd'T'HH:mmZ</dateFormat>

<dateFormat>yyyy-MM-dd</dateFormat>

<dateFormat>yyyy-'W'w</dateFormat>

<dateFormat>yyyy-DDD</dateFormat>

<dateFormat>d MMMMM yyyy, HH'h' mm'm' ss's'</dateFormat>

</dateFormats>

<defaultConfirmationUrl>http://192.168.1.9:80/develop/email-address-confirmed</defaultConfirmationUrl>;

<zipFileMaxSize>10</zipFileMaxSize>

<apiCallTimeout>30</apiCallTimeout>

<lockImpl>com.backendless.util.sync.RedisSync</lockImpl>

</server>

<analytics>

<workers>20</workers>

<db>

<host>127.0.0.1</host>

<port>27017</port>

<user>bn_backendless</user>

<password>5b0b8c2c8f</password>

</db>

</analytics>

<googleAnalytic>

<isEnabled>false</isEnabled>

<httpClientMaxConnections>50</httpClientMaxConnections>

</googleAnalytic>

<social>

<facebook>

<authUrl>http://192.168.1.9:80/api/console/social/facebook/authorize</authUrl>;

</facebook>

<google-plus>

<console>

<authUrl>http://192.168.1.9:80/api/console/social/googleplus/authorize</authUrl>;

</console>

<service>

<authUrl>http://192.168.1.9:80/api/users/social/googleplus/authorize</authUrl>;

</service>

</google-plus>

</social>

<servercode>

<apiUrl>http://192.168.1.9:80/api</apiUrl>;

<compressionEnabled>

<cloud>false</cloud>

<debug>false</debug>

</compressionEnabled>

<debugRedis>

<host>192.168.1.9</host>

<port>7738</port>

<connectionPoolSize>10</connectionPoolSize>

</debugRedis>

<notifyEmail>info@backendless.com</notifyEmail>

</servercode>

<messaging>

<maxRepeat>100</maxRepeat>

<messageTimeToLiveSeconds>60</messageTimeToLiveSeconds>

</messaging>

<reservedApplications>

<applications>5</applications>

</reservedApplications>

<repoFolder>

<folder>files</folder>

</repoFolder>

<files>

<operation>

<zip>

<executionTime>1000</executionTime>

</zip>

<unzip>

<executionTime>1000</executionTime>

</unzip>

</operation>

</files>

<import>

<loadFactor>32</loadFactor>

<importTimeout>1800</importTimeout> <!-- timeout in seconds -->

</import>

<migration>

<directory>repo</directory>

<export>

<timeout>86400</timeout>

<destination>

<url>http://localhost:9000/admin/migrate</url>;

</destination>

</export>

</migration>

<monitor>

<host>localhost</host>

<port>2502</port>

</monitor>

<version>

<major>3</major>

<minor>6</minor>

<patch>0</patch>

</version>

<docker>

<nodejs>

<allowedHosts>

<host>localhost</host>

<host>http://127.0.0.2/</host>;

<host>https://127.0.0.2/</host>;

<host>http://192.168.1.14/</host>;

<host>http://www.192.168.1.14/</host>;

<host>https://192.168.1.14/</host>;

<host>https://www.192.168.1.14/</host>;

<host>http://192.168.1.9/</host>;

<host>http://www.192.168.1.9/</host>;

<host>https://192.168.1.9/</host>;

<host>https://www.192.168.1.9/</host>;

</allowedHosts>

</nodejs>

</docker>

<mediaServer>

<host>media.backendless.com</host>

<port>1935</port>

<app>mediaAppVod</app>

</mediaServer>

<timers>

<task>

<timeout>30</timeout>

</task>

</timers>

</configuration>

photo
1

Please provide status update

photo
1

Barry, it appears to be a problem in 3.6.0.4. How critical is it for your code? Can you work around it by calculating the nextPage URL using current offset and page size?

Regards,

Mark

photo
1

Yes. I can work around the problem. The easiest solution might just be to replace within the URL string "127.0.0.1:9000" with my standalone url.

photo
1

Yes, that will also work.

Regards,

Mark

photo
photo
1

I will mark this topic as "works as designed" since there is a workaround you could use.

Mark

photo
1

Is the problem fixed in the 4.X version?

Why is the 3.X standalone version different from the hosted version?

photo
1

The 4.x API does not return the "nextPage" property, so yes, you can say it is fixed.

The Pro release is an iteration behind the Cloud version.

Regards,

Mark