I want to create a web application in Laravel. Which runs on the firefox browser. Inside this Laravel Application, I want another firefox browser (firefox browser inside a firebox browser) with the USA proxy. Access through Admin Panel.
Can you guide me with it?
Thanks
Related
I have deployed my laravel website in a shared web hosting service provider. All other pages are working except pages like login, and register pages. The pages expire immediately i click the send button. The same pages are working properly on my local website. I am using laravel-7 and vuejs
Someone help me please
Google just changed their oauth model to the new specification:
Modernizing OAuth interactions in Native Apps for Better Usability and Security
I am trying to follow (specifically section 7 of) the ietf "draft-ietf-oauth-native-apps-09" linked in the above blog, and also this reference from google:
OAuth 2.0 for Mobile & Desktop Apps
The issue I have encountered is that the custom uri-scheme behavior varies across browsers, and in some cases does not work as expected. In Firefox, which maybe be the default system browser, the app actually open inside Firefox, embedded - it does not return to the app it embeds the app in the browser, while the app from which the authentication flow was started remains open.
In chrome, it correctly redirects back to the app, however the chrome page with the authentication confirmation page remains open and does not close, which could be confusing to users.
How can I make sure that the oauth provider will always redirect to my app (without the browser embedding it), and close the tab or window which had the authentication flow open?
I need to integrate google contacts import in my nw.js app. How should I create the google app ? When I create the app as web app, it asks for redirect uri which is not available for desktop apps. I'm not clear about how to implement google integration for desktop apps. Can anyone help me on this. ?
There is an option in OAuth for desktop applications, when instead of http://domain you will redirect to app://something and you application will be started or receive a callback.
To make this, in your application you need to open request token url in new window (new window in your node-webkit app).
Also: google docs and node-webkit github issue and other issue about this.
For me I thought better would be open a default browser, there is a high chance that user already authenticated, and then just need to click "allow". So I start simple webserver inside node-wekit app and redirect to localhost.
You can see implementation in my project https://github.com/Paxa/postbird/blob/90cfb53b1775310eb2f262c8b54c9dba15b5cc0a/app/heroku_client.js#L185
To open default browser I use command "open" (only for mac)
child_process.spawn('open', [url]);
I also try to close browser window when user redirected back, it works but not always.
response.writeHead(200, {"Content-Type": "text/html"});
response.end("<script type='text/javascript'>window.close();</script>");
May be I should also make a window active when receive redirect back (didn't try it yet):
var currentWin = require('gui').Window.get();
currentWin.focus();
If google not allows to make localhost as a callback url, you can try to use some domain (even free) and point it to 127.0.0.1 or use http://readme.localtest.me/
I have installed User Agent Switcher in my firefox and some of the websites when opened automatically redirects to mobile while some of them render desktop websites only.
For example nytinmes.com when opened automatically redirected to http://mobile.nytimes.com/?referrer= while thehindu.com didnt get redirected to m.thehindu.com. My phone mobile does redirect thehindu.com to m.thehindu.com though.
What is making the difference. How do I truly get mobile browser behaviour on my desktop browser?
I am navigating to web page in windows phone web browser control. How to detect whether the requested web page url is authenticated or not in web browser control?
I don't think there is a way as cookies in web browser control are inaccessible. If they were accessible we could have checked their value and it would have been easy.