You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.
The source uses google.com as an example for a site that we can proxy through miniProxy (there's even a link for it when opening miniProxy.php in the browser).
The problem with that is that Google automatically redirects calls from http to https (see: https://productforums.google.com/forum/#!topic/websearch/1l2KMUfgyo4). This will usually fail for people testing miniProxy in a WAMP/MAMP/LAMP dev environment, because localhost usually doesn't support SSL (if it does and they access miniProxy through https, everything will work as expected). This can mislead potential users to think that miniProxy doesn't work or that it's broken.
I suggest that we'll do one of the following:
Change the examples to use some other service. For example we can use http://www.bing.com which works just fine (no redirect to https).
Add a comment about this in the readme file and/or the source code so users will know to try something else if it doesn't work for them instead of giving up.
Use some special links to Google that don't redirect to https (keep in mind that there are no guarantees that Google won't break them in the future). The links that work for me: http://www.google.com/?nord=1 , http://www.google.co.uk/?gws_rd=ssl.
The text was updated successfully, but these errors were encountered:
The source uses
google.com
as an example for a site that we can proxy through miniProxy (there's even a link for it when opening miniProxy.php in the browser).The problem with that is that Google automatically redirects calls from http to https (see: https://productforums.google.com/forum/#!topic/websearch/1l2KMUfgyo4). This will usually fail for people testing miniProxy in a WAMP/MAMP/LAMP dev environment, because localhost usually doesn't support SSL (if it does and they access miniProxy through https, everything will work as expected). This can mislead potential users to think that miniProxy doesn't work or that it's broken.
I suggest that we'll do one of the following:
http://www.bing.com
which works just fine (no redirect to https).readme
file and/or the source code so users will know to try something else if it doesn't work for them instead of giving up.http://www.google.com/?nord=1
,http://www.google.co.uk/?gws_rd=ssl
.The text was updated successfully, but these errors were encountered: