I'd like to understand if there's any cookie downloaded in the Desktop/Mobile browser, while browsing the MobileFirst Platform's Mobile Site.
Is there any information written inside it ?
Thanks in advance.
Typically, yes, there will be a cookie called WL_PERSISTENT_COOKIE used for working with authentication realms - you can find out more here.
In general, it's not too hard in most browsers to see if a cookie is set by any particular site, including the MFP mobile web environment - for example, here are some instructions on how to do that in Chrome.
Related
Suppose I am using WinInet/WinHTTP for crawling a website. In the past I could simply ask a user to login to a website using either embedded IE control or the IE browser and WinInet would use the same cookies as the IE browser. Now that will not anymore as the Internet Explorer is getting old and removed very soon.
For whatever reason Edge browser does not wrap/use the Windows Internet settings / cookies storage... Does anyone have experience login through an embedded webview2 ... fetch cookes and transfer to WinInet? For purpose being here that you can use WinInet/WinHTTP to crawl the website in login'ed state.
Is it a feasible solution login through embedded WebView2 control and transfer all cookies to WinInet before issuing WinInet HTTP requests?
(I have added a Delphi specific tag (TEdgeBrowser) but I am intersted in hearing if the above described concept in general can be brought to work.)
We added a CoreWebView2.CookieManager to WebView2 so you should be able to enumerate all cookies in WebView2 and set them on to wininet or vice versa. WebView2 and Edge is based on chromium and has its own HTTP stack and state location so is not connected to wininet.
I want build site using Sitecore(7.2) and also make it offline. Our requirement is not to use headless CMS. Is there any way to build or make it offline?
Internet websites cannot be delivered 'offline' without having all possible data delivered to the device so that it no longer needs to connect to the internet. This sounds less like a website, and more like an app that somebody would install?
If so, you probably DO need to look at headless and building an app that connects to the APIs for updates.
You might need to be more specific about the business use case because it seems contradictory to want to use a web application software that delivers web content, without using headless, and works without the web.
As already suggested that internet websites cannot work offline so either you have an app or intranet website.
Considering as an app you can consume sitecore OData apis for Content/Media however it will not work for Presentations and you have to implement your own mobile designs based on Xamarin or native.
For odata related information you can refer below link:
https://doc.sitecore.com/developers/90/sitecore-experience-manager/en/the-odata-item-service.html
Once you get the response from api, you can locally store it in your local db of app
I have created a chrome extension which gets data from the current active tab in chrome. I send the data to my webapp via an API which stores it in the database.
At the moment my chrome extension has a fixed user_id. I would like to prompt the user the user to log in in order to get the correct user.
Is it safe/valid to check for cookie - if it exists use it otherwise prompt user to sign in via the browser?
It's probably okay, as long as you're not storing anything sensitive in the cookie like a password (obviously).
However, the appropriate way to accomplish this would be through something like oAuth. In this scenario your web app's API would be a oAuth consumer, and you would use the following library to authenticate in a Chrome extension:
https://developer.chrome.com/extensions/tut_oauth.html
This library will save an authentication to local storage for you. It's pretty easy to use. The difficult part is ensuring your web app's API supports OpenID. Google's AppEngine supports this pretty much out of the box with little configuration on your side, but this may not be the case with your API.
I have developed a web application in Django and would like to go online i have an FTP access to the hosting server I am a beginner to "setting up a website" i would like to know how to install apache on that server and have my application working
Kindly provide detailed info as i am newbie, any links or tutorials would help a lot
Thanks in advance
If you only have user level access to the machine (ie: you don't have root), then you won't be able to control what web server runs and you can only control its settings to a limited regard. You will have to consider contacting your provider or looking for a different hosting package if the server doesn't meet you needs.
Typically, if it is a hosting server, the administrators will already have web server software like Apache running. You simply just have to upload what you would like to have displayed (typically to a directory called "public_html" or something like that), and it will display when someone visits your site. Hopefully they support things like Django, otherwise you might need to look at other options.
Your hosting provider is most likely to have specific and the most relevant instructions for how to upload your website.
I want to upload a file to a website via a desktop app and then take the user to the website. The website has a web service, but requires authentication as does the web site. Is there a way to do this without forcing the user to authenticate twice (once in the desktop app and once in the web browser)?
Unfortunately, you can't prefill an input of type file for security reasons, which makes sense since the user won't want you uploading arbitrary files from his/her computer. But if they have a desktop app, is there some way around this?
Or maybe make the user log into the web app first and then the authentication cookie can be reused?
Any other ideas?
Thanks,
Ben
I would use the dekstop app as a client to the website app via an api.
So, login via the desktop app. The api returns a authentication token (as Carlos suggested) which might be a md5 hash stored in your database for a certain period of time, possibly matched to the clients ip address.
The desktop app can then make calls on the api (like uploading a file) as a authenticated user (by using the auth token).
When loading the website, perhaps the url is http://website/login/{auth_token} where the auth token is added to the url. The api can check to see if its a valid auth token and consider the user logged in.
You could generate an authentication token that could later be used on the website.
It all depends on the type of authentication of the service and the site. Is it integrated Kerberos, WS-Auth, is it Basic/Digest HTTP, is it forms/cookie ?
This answer will most likely not work in the very general users-on-the-wide-open-web scenario, but in intranet contexts, using Windows Authentication (on an ASP .Net solution), would provide this.