On pages that use the UltraWebTab control, I find 404 errors in my web site log for requests to /dummy.htm. There is no dummy.htm anywhere in my site, and this only happens with pages that have the UltraWebTab.
Upon viewing the source for a rendered page, I see src="dummy.htm" in the rendered tags for the UltraWebTab control. What is this and is there any way to eliminate these bogus 404 entries?
Hi Ajarn,
You probably use rather old version of UltraWebTab. Currently the "BLOCKED SCRIPT''" is used. You may change value of that string in the DummyTargetUrl property of UltraWebTab.
Yes, this is the 5.3 version. We have purchased the latest version of all the controls, but have not yet rolled them out.
I see in the Properties window that if I don't set anything for DummyTargetUrl that "dummy.htm" is the default. And if I understand the documentation correctly, if I forced a blank, then something would not render or perform correctly (will have to test to determine exact consequences). It was rather frustrating to keep seeing this 404 in the IIS logs, and I don't want to create a dummy dummy.htm just to eliminate a 404. So I'll look for another solution. Perhaps I'll point it to a spacer image or something.
I don't understand what you are saying about "BLOCKED SCRIPT". I couldn't find any reference to that in any of the documentation. Can you elaborate?
OK, I get the idea of what you're doing. Maybe I didn't craft the syntax quite right, but in my very brief test it still logged a 404 error. If I use the empty string, then the IFRAME doesn't render and therefore there is no SRC to trigger the 404.
If I typed-in a value which filter of this editor does not like, then it replaces it by warning which you saw in capital letters. So, I tried somehow to trick that filter.
You should set
UltraWebTab1.DummyTargetUrl="javascript..."
where "..." should be equal to "='';"
If filter see javascript=something_it_does_not_like, then whole statement is gone.
If UltraWebTab1.DummyTargetUrl="" works for you, then you may use that.
Viktor, I appreciate you helping me, but I still don't understand what you're trying to tell me there. Can you just put it into regular words and not worry about code?
It appears that the Tab control still works fine if I include a DummyTargetUrl="" in my declarative syntax. From the documentation, it says that this will cause the IFRAME elements to not be written to the HTML (verified in my page by using ViewSource) and that in this case, the client side function setTargetUrl is not available for those tabs. This does not appear to be a problem for me since I am not doing anything on the client side that uses setTargetUrl. Is there something native to the control that uses that function?
Hi,
That is probably was replaced by filtering.
I will break suggested/current value for that property with _xx_ separators (1) and on separate lines (2). Maybe that will come through.
1.javascript_xx_=_xx_'_xx_'_xx_;
2.javascript='';