Why is the PDF download failing in a different environment (Galaxy Tab)? - pdf

We have an option to download PDF on our mobile website. PDF download is working in one environment, but not working in another environment in Samsung Galaxy tab.
In the environment where it is not working in the Galaxy tab, it's working absolutely fine in both iPad and Desktop. The pdf is generated and the "starting download" toast message also appears, but after that the download fails.
Has anyone faced this issue before?
OS version : 4.0.3
Browser. : Native android browser

I've looked into this a bit, and I found that it works ok when the downstream/upstream ratio of my internet connection is about 2:1, but it doesn't work when the ratio is 10:1. Based on that, I'd suggest that the Android end of the transport protocol isn't very good about adapting to highly asymmetric connections. The upstream path is used for acknowledgements, and a highly asymmetric path can interfere with the protocol - particularly when each end of the protocol is designed by different parties (and not thoroughly tested). All of your testing is consistent with this theory. And it is a known issue that transport protocols can sometimes fail to adapt adequately to asymmetric paths.

Related

WebStorm, Meteor and phone tests

I am developing a web application with Meteor and WebStorm as IDE.
This application can be called from a PC, a tablet or a phone, which does not pose a problem of execution since it is called in the browser.
On the other hand problems appear, which are due to the size of the screen and the positioning portrait or landscape.
To test, a solution is to deploy the app, open it in the phone browser and see what works or does not work. A bit heavy ...
Is there a method to test a web application on a device connected to the development PC, through WebStorm, can be with an added package, or with another tool
Any leads or ideas would be welcome.
Thank you for your answers
YC
I have had a similar issue, I used Ghostlabs (https://www.vanamco.com/ghostlab/), to test different screensizes simultaneously. You will need to have physical devices present and connected to your development machine.
Saucelabs(https://saucelabs.com/) in my opinion is an extension of Ghostlabs, with the advantages of using the cloud.
One other tool I would recommend is Browser stack (https://www.browserstack.com/) it gives similar benefits as Saucelabs.
These tools I find are very effective for cross browser testing too.

check point ssl network extender installation mac os safari

SSL Network Extender fails to launch.
launching SSL Network Extender fails with "failed to download" on safari.
I think there is a solution but they do not share it public.
Does anyone have a solution for this?
In checkpoint user center Solution ID sk96108.
Thanks
EDIT: From the Safari 12 release notes:
Legacy NPAPI Plug-ins
Removed support for running legacy NPAPI plug-ins other than Adobe Flash.
This means that plugins such as Java and Silverlight will no longer work in Safari 12. This answer still works for Safari 11 and earlier. For a solution that works on newer versions, see this workaround (which uses an old version of Firefox).
Simply hold down "alt/option" and click on the Java trust settings for the relevant website, deselect "Run in Safe Mode", and click "Trust" in the dialog that pops up:
Source: Apple Support.

Screen Sharing on webRTC

Is it possible to capture desktop screen sharing through webRTC.. As we know that it just captures the screen on the browser tab but is it possible to capture the whole desktop screen like navigating through files on computer or opening and viewing files like pdf etc..
Currently, only "stateless" screen capturing is available in RTCWeb implementations (both chrome & firefox). E.g.
Install chrome extension and then try this demo
Above demo will simply capture screen of "any" opened application's screen. Though, such screen capturing API fails to capture screens of full-screen game applications.
More information available here:
https://developer.chrome.com/extensions/desktopCapture (HTTPs+getUserMedia+postMessage)
Regarding remote desktop sharing from a web-browser, it has a pile
more security risks associated with it compared to screen sharing. The
UI/security aspects will be tough to deal with, and the feature will
be very susceptible to social engineering -- phone call: "this is
Google/Dell/Computer-Management; we've detected your machine has a
virus on it; could you browse to and we'll assist you in
removing it" -- etc. Ref
Yes, it's possible. At least using Chrome. There are several ways of doing it, but the simplest one is:
Add this constaint when you invoke getUserMedia:
constraints.video.mandatory.chromeMediaSource = 'screen'
When starting chrome, use this argument (chrome version > 35):
--enable-usermedia-screen-capturing
You can find an example of sharing screen and recording the shared screen at a remote server repository here:
https://github.com/Kurento/kurento-tutorial-js/blob/develop/kurento-recorder-screen/static/index.js
If you try to execute that example, play close attention to the security restrictions. All signalling needs to travel using TLS. Using raw HTTP will produce chrome to refuse sharing screen.
Yes it is. I recently worked on WebRTC and was able to stream desktop easily. Following links helped me implement my requirements :
Firefox Extension : http://mozilla.github.io/webrtc-landing/
Dont forget to add your *.github.io to about:config -> getUserMedia screensharing allowed domains
Google Chrome extension : https://developer.chrome.com/extensions/samples#search
Open this in Run : Chrome.exe --enable-usermedia-screen-capturing
Other Reference : https://github.com/muaz-khan/WebRTC-Experiment

Cannot view video from publisher using Chrome to iPad with OpenTok

I'm currently trying to set up a connection between my web client and my iOS app, but for some reason my iOS client only sees a black box when using Chrome (version 33). I can see the video just fine if I use Firefox (both in my app and when I put the browsers side-by-side, they can see each other).
This doesn't appear to be a documented known issue with the JavaScript SDK, and I can't see any recent discussion about this on the forums (last post was mine).
The iOS sample can be located here (samples/OpenTokHelloWorld) with the browser page in samples/OpenTokHelloWorld/browser_demo.html
I suggest cd'ing into samples/OpenTokHelloWorld and running python -m SimpleHTTPServer, as it can't be run from a file:/// path.
Here is what my iPad sees:
Chrome:
Firefox:
And Chrome/Firefox (respectively), both publishing video from the same camera
Edit: after testing on other machines, it may be something specific to my environment even though none of my extensions run in Incognito and I don't have any custom plugins installed.
It looks like the OpenTok mobile SDKs with the specific webcam I was using has issues. On Android the video stream will display for a brief moment then segfault, and on iOS there will be no video at all.
I have tested this many times and could not reproduce what you are seeing in your chrome.
Without seeing any console errors or iOS logs the best suggestion is to try clearing your cache, or maybe restarting your computer (longshot)

How to export Safari Web Inspector timeline data?

Just like in Chrome Developer Tool, I was wondering if there is any tool/extension/plugin which would allow me to export timeline data in Safari. I tried the nightly build of webkit but it does not have that feature. Seems like this is a Chrome specific functionality.
I have to use Safari because I am testing a webapp on iPhone.
I searched around for any hints but could not get any. As of now I am thinking of two options to get the timeline information:
Build a Safari extension
Get Chrome Dev Tool's timeline code and build my own version of webkit (if that's even possible!)
Any guides/insights would be highly appreciated!
Update 1: I downloaded Webkit and found out that it supports remote iPhone debugging through USB. Probably I can find the code for web inspector for Webkit and use that code to export the timeline data.
Safari's Web inspector does use the WebKit remote debugging protocol.
However, Safari does not use TCP/HTTP as a transport layer, thus
making it incompatible with Chrome. source
Thankfully, someone from Google wrote a proxy allowing to overcome this limitation.