Strange, accessing the url outside your test-environment shows a permissions issue :
"Forbidden
You don’t have permission to access /inlay-client/ on this server.
Apache/2.2.16 (Debian) Server at inlay.ontwerpzaam.nl Port 80"
Even now all files and folders’ permissions have been changed into 777?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I also have a copy running here (same result though) : Domain parking page
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On May 29, 2014, at 9:49 AM, Richard van Heukelum wrote:
Strange, accessing the url outside your test-environment shows a permissions issue :
"Forbidden
You don’t have permission to access /inlay-client/ on this server.
This could be if you were trying to link to the folder, which doesn’t include an index.html file – this would be the correct response to that request.
Are you sure that the file is in the htdocs (or whatever that’s named in your system) folder?
Apache/2.2.16 (Debian) Server at inlay.ontwerpzaam.nl Port 80"
Even now all files and folders’ permissions have been changed into 777?
Files should never be set to 777. 664 or 644 only. Apache won’t serve a 777 file ever, AFAIK.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Ah, that’s possibly due to misunderstanding the necessary steps to do the test, so I’ve uploaded a test-site to the inlay-client folder and receive this result via the form:
Url: Domain parking page
Page:
Array
(
[base] => http://www.pxbypx.com/inlay/inlay-client
[remote] => Success! Your server can reach Inlay.io
[pages] => Array
(
[0] => /test.html
[1] => /index.html
[2] => /work/index.html
[3] => /web/backup.service.html
[4] => /web/content.management.html
[5] => /web/domeinregistratie.html
[6] => /web/index.html
[7] => /web/site.html
[8] => /web/social.media.html
[9] => /web/webshop.html
[10] => /print/index.html
[11] => /inlay-client/test.html
[12] => /corporate.branding/index.html
[13] => /contact/index.html
[14] => /about/index.html
)
[templates] => Array
(
[0] => /template.html
[1] => /inlay-client/template.html
)
[partials] => Array
(
)
)
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yay! This means Inlay works for you!
Walter
On May 29, 2014, at 11:22 AM, Richard van Heukelum wrote:
Ah, that’s possibly due to misunderstanding the necessary steps to do the test, so I’ve uploaded a test-site to the inlay-client folder and receive this result via the form:
Url: Domain parking page
Page:
Array
(
[base] => Domain parking page
[remote] => Success! Your server can reach Inlay.io
[pages] => Array
(
[0] => /test.html
[1] => /index.html
[2] => /work/index.html
[3] => /web/backup.service.html
[4] => /web/content.management.html
[5] => /web/domeinregistratie.html
[6] => /web/index.html
[7] => /web/site.html
[8] => /web/social.media.html
[9] => /web/webshop.html
[10] => /print/index.html
[11] => /inlay-client/test.html
[12] => /corporate.branding/index.html
[13] => /contact/index.html
[14] => /about/index.html
)[templates] => Array ( [0] => /template.html [1] => /inlay-client/template.html ) [partials] => Array ( ))
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options