@AMIGASYSTEM - when you see this problem on 64 bit native, what network adapter are you using? I'm just wondering if it can be pinned down to an owb or a diver problem. Althogh there is one more vaiable; I suppose it could be an issue in AROSTCP itself.
Cheers,
Nigel.
As I mentioned in the attached link, the problem occurs when I am connected via ‘USB tethering’.
Just an uneducated observation, but I wonder if the issue with timeout on Google etc. is due to the cookie acceptance panel. I've noticed for many sites first time of loading is slow and the first thing that appears on opening the page is the cookie preferences box. Once this is set subsequent page loads seem to be faster. Google has quite an involved 'terms and conditions' panel, so could that be causing the timeout?
The site eab.abime.net does a verification to see if the user is not a bot, ant it FAILS saying that it needs cookies, BUT cookies ARE enabled in the browser.
Same thing happens when doing a web search using the search engine marginalia-search.com !
The home page of the search engine is loaded normally though.
@arossystem
The site eab.abime.net does a verification to see if the user is not a bot, ant it FAILS saying that it needs cookies, BUT cookies ARE enabled in the browser.
Same thing happens when doing a web search using the search engine marginalia-search.com !
The home page of the search engine is loaded normally though.
I just tested this search engine and I immediately got the "Oh noes! invalid response" error message.
Mind you, I was using the latest version of Firefox...
So, I am afraid there is nothing that needs to be fixed in Odyssey.
@AMIGASYSTEM
Searching on marginalia-search.com works fine on my updated Firefox on Windows 7 64-bit.
The point I was trying to make was that if the same behavior happens with mainstream web browsers (I am using the term loosely here since Firefox is pretty niche by now), the problem is most likely with the Anubis server software, which handles the browser check, and not web browsers like either Firefox or Odyssey Web Browser.
The fact that it happened to work for you does not disprove this theory.
I'm also using Odyssey under AxRuntime and it works for me on EAB - I'm visiting it daily. Are you using default Odyssey user agent or spoofing as some other browser? I'm using default Odyssey user agent. Alternativelly write to admins of EAB to add Odyssey to whitelist.
About bot detection, there is nothing much that can be helped TBH. Maybe update to WebKit engine will work, but there is no guarantee. You can write the the support of the pages you tried to visit and ask them to add Odyssey to white list.
About temu.com and other non-working pages - again possibly a WebKit engine will help, but I'm not planning on working on Odyssey for the next 3-6 months.
You can view all discussion threads in this forum. You cannot start a new discussion thread in this forum. You cannot reply in this discussion thread. You cannot start on a poll in this forum. You cannot upload attachments in this forum. You cannot download attachments in this forum.