-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
"Hosted on same domain name" note not completely true #36
Comments
You set it right. You're totally right about the cross-origin thing. I didn't want to test this and I think that there were only a few people interested in this. You're proving me wrong ;-) I'll update the README and point to your post & a litte doc on MDN I find good: https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS |
Doc updated |
Great writeup. Just a little tip on the
Enable the module with:
|
Is this still supported? At least, the variables:
Don't exist any more in the latest release. I assumed that just setting:
Would be enough, in collaboration with the |
False alarm. It actually seems to work just setting:
And the Sorry for the noise, and thanks for your awesome work :) |
The readme states that ttrss-mobile " should be hosted on the same domain name." Without additional configuration this true, but with a simple .htaccess file it is possible to install ttrss-mobile in any domain you want.
My ttrss is installed on http://rss.mydomain.com. I wanted ttrss-mobile install on http://mrss.mydomain.com. After setting everything up the browsers throws a cross-origin resource sharing exception and that is expected.
If ttrss is running with an Apache web server this is easy to solve. I only had to copy this
.htaccess
file into the ttrss/api folder and everything works.My conf.js looks like this:
Not sure if I set the window.webappPath variable correctly. But it looks like everything works.
The text was updated successfully, but these errors were encountered: