For certain characters when putting in query string parameters they need to be URL encoded or they will cause problem to the web service.
I faced this problem with the # character, encoding it and use %23 instead solved the problem.
Bruce Ng's software development blog
An archive of solutions of programming problems I have faced in my career
For certain characters when putting in query string parameters they need to be URL encoded or they will cause problem to the web service.
I faced this problem with the # character, encoding it and use %23 instead solved the problem.
Today while testing the Ext JS application I was writing on various browsers, something strange happened. The app works on IE and Chrome, while on Firefox it breaks.
It turns out if not configured correctly WebAPI will return data depending on the Accept HTTP header sent by browsers, and different browsers sent different HTTP Accept header.
More details in the SO answer: http://stackoverflow.com/a/31934984
Firefox prefers XML, so Web API try to serialize data in XML format to return to Firefox.
IE and Chrome doesn’t prefer one over other, so Web API chooses Json.
I solved this issue in Firefox by configuring the web api to always return JSON by adding the following line to WebApiConfig.cs
config.Formatters.JsonFormatter.SupportedMediaTypes.Add(new MediaTypeHeaderValue(“text/html”));
This issue occurred today while I was trying to run an Ext JS application from IIS, because .json files are not accepted by IIS I tried to add this file extension to the application. But instead I got a 500 error when trying to browse the application.
After some digging and searching the MIME types section of the website and all other applications, I couldn’t find the conflicting extension.
I was able to solve the issue by editing the application’s web.config file, right before the mimeMap tag, add a remove tag like following:
<staticContent>
<remove fileExtension=“.json“/>
<mimeMap fileExtension=“.json“ mimeType=“application/json“ />
</staticContent>
I still have no idea why this works, but it works.
Not entirely sure why, but when using ajax proxies, specifying the URL is not enough, the data won’t be displayed on lists/panels.
A reader must also be defined in the proxy, otherwise the data will not be read correctly
proxy: {
type: ‘ajax’,
url: ‘data.json’,
reader:{
type:’json’,
rootProperty: ‘DATA’
}
}
Make sure that
I faced this problem today after installing sencha cmd. Even after adding the path to sencha cmd to the user environment path variable, trying to run it from the command line showed only an empty line.
After a while I managed to resolve the problem by adding the path to the system PATH environment variable.
If the app was generated using Sencha Cmd without specializing either option ‘–classic’ or ‘–modern’, the app will be generated with both and the views will be in both folders ‘classic’ and ‘modern’
When I encountered this issue, it was because of the grid panel. According to this Stackoverflow answer http://stackoverflow.com/a/21740832/5539403 it is because the grid panel tries to shrink-wrap its content but there was no content at the time the layout run is executed.
I fixed it by setting the width of the grid panel somehow.
Follow the StackOverflow answer here: http://stackoverflow.com/a/10501908/5539403
The steps are copied here in case link is dead
C:\Windows
called MSJAVA.DLL
. The setup process will look for this file, and if it doesn’t find it, will force an installation of old, old Java, and require a reboot. By creating the zero-byte file, the installation of moldy Java is bypassed, and no reboot will be required.SETUP.EXE
, select Run As Administrator
.C:\Program Files\Microsoft Visual Studio\VB98\
After changing these settings, fire up the IDE, and things should be back to normal, and the IDE is no longer sluggish.
I was able to solve this problem by install Visual Basic 6.0 and Service Pack 6 for VB6, the control is in mscomctl2.ocx file.
Alternatively, the problem can be solved by installing the windows common controls pack manually.
Follow the article: https://support.microsoft.com/en-us/kb/957924
And it seems in order to install this pack, Visual Basic 6.0 sp6 needs to be installed?
This is a stupid mistake of mine that took me hours to figure out the reason why.
Check the following things
-Any filters applied to datasets
-Any filters applied to the charts/graphs, etc
In my case it was because the dataset I used for the tablix had a filter that returns only 1 record from the source data.