I have question about mobile visitors. What information can a website administrator get from mobile user?
For example: when I visit www.site.com from my phone device (I use mobile internet, not WiFi)
what they will know about me? Can they can get my mobile number, imei code, or mobile device information?
This is kind of a broad question, but I will try to explain briefly the general concept.
First of all it's fundamental to understand what a connection is, and what a protocol is.
A protocol, briefly said, is a way the two objects communicate in. I would recommend you to watch this playlist.
https://www.youtube.com/playlist?list=PL6gx4Cwl9DGBpuvPW0aHa7mKdn_k9SPKO
Now about the connection. The connection by itself involves all the path from you/your device to the server you need to communicate with, and thus, summarising these two, we can make a basic conclusion. The server can gets your IP address, which is due to the connection concept, and also info about what program exactly do you use, because of the protocol. The protocol may require your program to send lot's of information from it, but if we are talking about web browsers, they do not share the users private information for privacy and security reasons.
That's it, I hope I could help you somehow.
Related
I am doing registration in my app using HTTP. If I do registration via MOBILE DATA my cookies are not coming from server But If i do the same task via WIFI cookies are coming properly. And this problem is being faced on just one handset i.e. "SONY XPERIA M". On other handset, cookies are coming on both via mobile data and via wifi too.
Why so?
It is almost impossible to answer this question with this little information, but here's some general help to get your problem sorted out:
Take a look at your cookie parameters. The domain, path, etc have to match the domain, path, etc. you are serving the page from. Some devices may be more lenient, others may not be.
Try to route your internet traffic via a VPN, so you bypass any wonky filtering or CGN your network provider may apply.
Switch your application to HTTPS. HTTPS cannot be manipulated by intermediaries, so your cookies should be safe.
Do extensive traffic logging on the server if possible. You can capture packets from your mobile device if you know it's IP address using tcpdump and then display them in Wireshark. This should enable you to piece together why it isn't working.
In the traffic dump take a look at the headers sent from the client. Be suspicious of any headers that may indicate the presence of proxies. Also take a look if the IP address your device thinks has is the same the traffic is coming from. If it isn't, a NAT or transparent proxy is in place.
Try to sniff the traffic directly on the device and compare it to what the server sees. If the traffic differs, there is some proxying in place. There are some android apps for that.
I hope this helps. If you need additional help, please post a lot more information, especially the exact cookie header you are sending out.
Starting to build an app where we will have a desktop and a mobile client applications. These two apps will exchange messages/info on frequent basis. The idea is not to have any server/central entity for this communication. We want to send/receive messages without any server implementation. I googled on these and got peerjs.com, openpeer.org and google project apprtc. Peerjs and apprtc are kind of web based applications which are not in our kind of.
But still it's not very clear on how this things works out as they involve any server or not. Kind of stuck and not sure where to start and how. Is it possible at all?
We are not yet tied to any platform, so open to any kind of implementation. Please share if you have any similar experiences of any applications using this kind of technical stack?
use webrtc ios project, and its what you need
https://github.com/gandg/webrtc-ios
Sockets is what I'd use, assuming the network requirements mentioned above
Those two devices may or may not be on the same network.
Then you need a server of some form, whether you want one or not. That server may simply be a data broker (see PeerJS) or provide more functionality, but it must exist. That server may be one that you host yourself or be some common cloud provider, but it must exist.
Has anyone tried sending emails automatically (without user interaction) from your android app through exchange protocol? I saw a lot of examples through SMTP and they are working perfectly. But I am wondering if it's possible to send using Exchange protocol? Does android allow to build our own exchange client?
Are there any libraries to use? Or should I build from scratch? If so, can anyone point me a good starting point?
Can anyone give me a lead? any idea? any suggestion where to start looking at? or anything?
Thanks,
Karthik
The exchange protocal (depending on how things are set up) is nearly always RPC over HTTP/HTTPS as a mobile user. ActiveSync is the alternative but has few advantages.
An issue you may come up against is MS Exchange has client access policies that require the Exchange server to have certain amount of control over the phone (Mandatory PIN Lock, remote wiping of phone etc that probably need root access). There are also Certificate trust requirements.
If you are developing an in house platform it may be quicker to look at IMAP which exchange does reasonably well.
Alright I have two questions which are interrelated.
Using Google OAUTH can I send communications between an android phone and a chrome browser extension? I was thinking that I could write some info somewhere and it would be stored in the account info or something? This was just a theory (not really supported by any info I have read)
If that doesn't work I was going to use Android to node.js communication idea using http://static.brandedcode.com/nws-docs/ documentation for an android to websocket server communication then a chrome extension to the websocket server. I was then going to use the gmail from each device to verify they belong to each other and pass the message that way.
Does anyone have any knowledge about how feasible this is/how challenging it is? I also need to know how secure the communication is if I only rely on a gmail account. Is there any information done by using OAUTH or another method that I could use to secure it more?
Finally is there a method to turn a chrome extension into a websocket server? That way I could just bypass the need for an external server and any sort of verification method.
I'm willing to do some work and/or research if necessary so list anything you think I should look into and any ideas you might have. I'm thinking of having a nice coding weekend so I will be playing around with this A LOT!
I appreciate any help that anyone can give.
I need a very simple server that listens for connections, retrieves a question and simply answers yes or no. Then the connection is broken.
As my Android device is the only device that is powered on and connected to the internet 24/7, I'm thinking of using it as the server.
Is this possible, and how could I achieve this? The biggest problems that I'm facing is the ip-address, as it could be changing a lot. I'm thinking of storing it in a public dropbox file, so the client can retrieve the address from that
There's a whole slew of reasons why you shouldn't use your android device as a server, but I won't go into those. I'll just assume you have a good reason for doing what you want to do.
Since your question is very general, the best I can do is give you a very general answer. You'd implement a server on android like you would any other server using java using sockets. For a simple java implementation of a socket based server, checkout this tutorial. The tricky part is going to be getting your IP address to share with clients so that they can connect to your device. As nick suggested, dyndns might be an option here, but I'm not sure if they have a mobile client.