I'm upgrading an app to Swift 2 (Xcode 7).
When I'm loading a URL in a Webview a strange problem occurs: some HTTPS URLs won't load. Other URLs (also HTTPS) are working fine.
I already tried setting the NSAppTransportSecurity - NSAllowsArbitraryLoads to YES, but this doesn't fix the problem. Does anybody have any idea what may cause this issue?
Also tried to log via
setenv("CFNETWORK_DIAGNOSTICS", "3", 1);
but actually I don't know what to search for in the log file in order to track down the cause of this problem.
Related
I am working on a site in MODX 2.6.1-pl and have a template that uses 7 different MIGX template variables.
Everything seemed to work fine to work fine initially, but now some pages cause many (several hundred) of the following xpdo errors when I try to edit them in Firefox 58.0.1:
[2018-02-05 11:34:55] (ERROR in xPDOConnection::connect # /home/user/public_html/core/xpdo/xpdo.class.php : 3116) SQLSTATE[HY000] [1203] User user_modx already has more than 'max_user_connections' active connections
It would appear this is only happening on pages that contain large amounts of data stored in the MIGX TVs.
Also, this error does not occur in:
Chrome 64.0.3282.140
Safari 10.1.2 (10603.3.8)
Opera 50.0.2762.67
Why is this happening?
Is it due to how the new Firefox handles Ajax or something?
How can I work around this?
Am I asking too much of MIGX? Would it be better to put all my data in a custom table and use MIGXdb instead?
I found the answer : Firefox was blocking some of the calls because I was logged in with HTTPS security exception.
I tried without using an HTTPS connection and it works.
I have a 4.2.17 version of laravel that was working perfectly fine for months. All of a sudden one of the views is returning a 500 server error, and is not logging anything into the storage/logs file (already checked all permissions).
I was able to manually track down the line causing the error and it turned out to be carbon\carbon that was causing the issue. For some reason it was crashing when I call Carbon:now() from a view. So I thought it might be carbon that was causing the issue or not loading properly.
However, Carbon:now() only crashes the app when it is being loaded from storage/cache.
If i go into storage/cache and delete everything and refresh, the page will work including the carbon line. Once i try and refresh a second time with files now in the cache folder, I will get the 500 server error.
If I remove all the carbon lines the page loads perfectly fine from cache.
This was all working perfectly before so I am not sure why it broke. Does anyone have any ideas? Is this an issue with loading from cache? Is there a better way I should be clearing it?
Thank you in advance for any help. Cheers.
Turned out to be a timeout issue, I guess loading from cache + carbon turned out to be too much for the server. Increasing max_execution_time did the trick.
FireFox will get the error
"The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies."
when I run cucumber test.
I can open firefox and can't get any error messages. And I have tried all clear cookie, cache , accept the third-party cookie and so on. But it didn't work.
Is there any other ways I can tried ?
Is this firefox specific issue?
If not check the URL on other browsers
Faced this issue some time back and the reason being url redirection
Ex:
Assume there are two URLS :
URL A , URL B
Apparently there were two URL redirect entries in a table:
URL A was redirecting to URL B
URL B redirecting back to URL A
which caused the issue.
Let me know how it goes!
I solved my problem.
Two tips:
1.empty cache file
2.empty download gems and bundle
The web app that I am building in meteor works in chrome and I.E.(Other than a UI bug in I.E.) but it starts acting strange in Firefox. When I run it on my localhost and on the deployment to meteor.com, I don't get any errors in the console in the browsers' developer tools.
When I run it in Firefox, things start acting weird. On Mac OSX, if I run the app on my localhost and open it in FF it is just fine. However, when I open up the app that deployed to meteor.com via meteor deploy [my-app-url].com, I get the following errors but I can still use everything in my app:
Error 1:
mutating the [[Prototype]] of an object will cause your code to run very slowly;
instead create the object with the correct initial [[Prototype]] value using Object.create
Error 2:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource
at https://ddp--3071-[my-app-url].com/sockjs/info?cb=v9pygo9mzn.
(Reason: CORS request failed).
While right now I am not able to figure out what is causing the first error, I am mostly worried about the second error.
When I open up the app from it's deployment in FF on Windows 8, I get the first error once, and then I get the second error repeatedly and the app never loads(it just stays on my loading template from the iron router). My deployed app runs just fine on Chrome and I.E.
I don't send any kind of request to another server in my app, so I am not sure why I am getting a CORS request error. I have not set up SSL or began to make a certificate yet, so I am not sure if this could be causing this kind of error in FF as I got another exception on my login page in FF on my localhost saying that I shouldn't have password elements when I'm not using https.
Does anyone know what could be causing this?
Sorry that I provide any code, as I don't know what code I would post to solve this problem since I don't actually request anything from another server in code that I have written.
Thanks in advance for any responses!
If anyone is interested, it seems as if my combination of the aldeed:collectio2 package and one of my other packages was the cause of my problems. I removed this package and my issues went away.
Ok so since I applied an SSL Cert to our site the graphs in the dashboard have stopped working. i read this site
EDIT: forgot to add, im trying to get this working in the magento dashboard.
http://www.phpro.be/blog/detail/magento-dashboard-charts-not-working
which states to add "true" to the GetChartUrl() function within
app/design/adminhtml/default/default/template/dashboard/graph.phtml
this works on a site not using SSL.
I then found this site
http://webguru.org/2009/11/09/php/how-to-use-google-charts-api-in-your-secure-https-webpage/comment-page-1/#comment-988
but this supposedly opens up opportunity for SQL injection and other malicious attacks.
next I found this site
http://store.ivvy.ru/blog/chartssl/
and followed the instructions but still the charts aren't working.
i tried changing
const API_URL='http://chart.apis.google.com/chart';
to both
const API_URL='//chart.apis.google.com/chart';
const API_URL='https://chart.apis.google.com/chart';
but neither worked.
Can anyone point me to any other examples / explanations, or explain how to get this working?
Many Thanks
Do you use Firebug or another browser debug tool? If so, what is the error on the Console tab when you load the page containing the charts. I can tell you now, it's most likely due to trying to load a HTTP JS script over an HTTPS connection...which will fail.
Try using their latest API URL which supports HTTPS:
https://chart.googleapis.com/chart