vijibhanu wrote:I have obscured the das.id in the above log as that is what is used to create the URLs that goes out to the album invitees (Another disconcerting thing is that when you invite a group of people, it seems to send the same URL to all the invitees. It is not using any parameter besides the das.id in the incoming request URL to do some type of authentication and differentiate each incoming request. This is a bad design for a server application)
vijibhanu wrote:Surely, it must be opening up some ports if the photos all reside locally on my ReadyNAS Duo and are served up from there.
The visitor information is not figure in *visible* part of the HTTP request viz the URL.
minerva wrote:The URL <username>.readynasphtos.com does not resolve to your ReadyNAS device. This URL resolves to readynasphotos network which maintains private communication with the ReadyNAS devices. This is similar to you are using skype, you do not have to open any ports.
minerva wrote:ReadyNAS Photos does not open any ports on your ReadyNAS device. Only your ReadyNAS device has to be connected to the internet for the shared photos to be accessible.
If you are having problems viewing this email, copy and paste the following into your browser:
http://dns-name/go/rd/YYYYYY. The latter, of course, does not have the das.id that I spoke of earlier.
vijibhanu wrote: Can you explain the architecture of the server application?
The URL http://dns-name/go/rd/YYYYYY is different for every invitation that is sent out.
Like you observed, this URL redirects to the URL which has the das-id. But it also sets a cookie containing the user identity. So the subsequent URLs does not contain information about the visitor.
Hence visitor identity is readily available on every request, and the access control are performed before serving the content.
minerva wrote:vijibhanu wrote: Can you explain the architecture of the server application?
There is no server on the ReadyNAS Duo that *accepts* requests on any port. So even after blocking all the ports for incoming traffic ReadyNAS Photo works and the shared photos remain accessible.
However, outgoing communication on ports 80 and optionally 8081 on your ReadyNAS Duo should be allowed. If you block outgoing communication either on 80 or on 8081, the ReadyNAS Add photos has to be restarted, for the shared photos to be accessible.
Please ensure that you have 1.7 version of ReadyNAS Photos Add on installed.
vijibhanu wrote:Is the "Dekoh Listener" that is started up on the ReadyNAS Duo device constantly polling the portal to check for user requests and push the requested file?
Users browsing this forum: Baidu [Spider] and 0 guests