Yes I'm good now, thanks. :)

Hi,

you're right, the problem exists on all versions of Safari (iOS and OS X).

I tried a few things in my code, but to no avail.

The only advice I can give to work around this:

• use HTTPS: I read somewhere that Safari was not using HTTP pipelining (the root cause of the problem) in HTTPS mode
• configure Ubooquity to display less images per page: from what I read, the problem happens more often when pages contain a lot of images
• Use another browser, Safari is the only browser having these kind of problems with HTTP pipelining, all others work fine

I'll add it to my todo list.

Dont expect it soon though.

I guess you should try to ask your question on a QNAP forum, you're more likely to find QNAP "experts" there.

Sorry.

Hello,

the restriction to CBZ and CBR files is by design: the extension of the file carries a meaning which tells what kind of data we can expect to find inside. CBZ/CBR files are supposed to contain images and sometimes metadata files, so Ubooquity knows what to do with them. Zip and rar files can contain anything, so it's better for Ubooquity to ignore them as more often than not they will not be comics.

This problem I have sometimes too. It happens on my iPad 3.

But I think it's different from the "pure" slowness problem Eric and Mike have.

Usually I reload the page and it works.

I have never been able to understand it, especially the part where thumbnails get mixed up, but I'm almost sure this is an iOS only problem (thanks Apple, again):

http://www.steckinsights.com/images-randomly-swapping-iphones-mobile-safari-ios/

https://openradar.appspot.com/19027882

No problem. I was indeed already using Safari.

If there is a solution simple enough to implement fullscreen on iOS I'll do it, but it seems unlikely so far.

iOS users can still use alternative browsers with a fullscreen mode provided by the browser itself. iCab Mobile offers this functionality, for example.

Here is how it works.

The first time you go on the admin page, Ubooquity asks you to create a password.

The password is hashed and stored in a file ("webadmin.cred", in Ubooquity's working directory).

You are then redirected to the admin page and a cookie is created.

The next time you go on the admin page, if the cookie still exists has not expired (it lasts 30 days), you'll not be asked for your password.

If the cookie has been deleted or has expired, you'll be asked to provide your password again, which will be compared to the content of the "webadmin.cred" file.

By the way, did you look for errors in your log file ?