Is the iis url case sensitive (the question of automatically changing the URL of FF) difficult )?, Ffurl
(II8 VS14 CTP3 Windows7 ASP. net webform)
In my impression, the iis url is case-insensitive in general.
So the two URLs below should be the same.
Http: // localhost: 61658/default. aspx
Http: // localhost: 61658/Default. aspx
Yes, I found that the above one in FF is OK,
The following is 404. When you enter the address in the address bar of the browser, the address is automatically changed to http: // localhost: 61658/Default.
I interviewed for the same thing in IE, And it is OK in both case and case.
Let's start with this question. For example, I have a website that was previously developed and is named WebSiteAAA.
One day, I copied the website to another directory and used the Onsite of VS to open the website for debugging. The port is 61658.
Then F5 was implemented, and the website started normally, of course, in FF. Enter a page and return to the home page, that is
Http: // localhost: 61658/Default. aspx. At this time, the address is changed to http: // localhost: 61658/Default.
I can't explain why it turned into this.
Is there a problem with the code? I copied the code to another place and found that the port number has changed (I guess the port number should be the port number calculated by the directory name)
The same operation is normal and perfect. Of course, if I modify the Directory Name of the problematic directory, the port number will also change, and the same code can be completely migrated.
I suspect that FF will automatically change the http: // localhost: 61658/Default. aspx address to http: // localhost: 61658/Default, and save it somewhere.
The following IIS execution LOG, the first one is IE, which is normal,
In the next two lines, I enter http: // localhost: 61658/Default. aspx in the FF address bar.
Then, when it comes to IIS, it has become
2014-09-06 08:48:28 127.0.0.1 GET /Default - 61658
2014-09-06 08:44:19 127.0.0.1 GET /Default.aspx - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/ShowBlog.aspx?BlogId=2014021714122550 200 0 0 2962014-09-06 08:44:19 127.0.0.1 GET /Scripts/jquery-1.9.1.js - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 312014-09-06 08:44:19 127.0.0.1 GET /Scripts/UIKit/js/sticky.min.js - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 152014-09-06 08:44:19 127.0.0.1 GET /Scripts/UIKit/js/uikit.min.js - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 312014-09-06 08:44:19 127.0.0.1 GET /Scripts/Utility.js - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 152014-09-06 08:44:19 127.0.0.1 GET /Scripts/UIKit/css/uikit.min.css - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 1242014-09-06 08:44:19 127.0.0.1 GET /Scripts/Waterful/jquery.masonry.min.js - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 622014-09-06 08:44:19 127.0.0.1 GET /Image/Waterful/2014021713591697.JPEG - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 152014-09-06 08:44:19 127.0.0.1 GET /Image/Waterful/2014021714121718.PNG - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 622014-09-06 08:44:19 127.0.0.1 GET /Scripts/Waterful/jquery.infinitescroll.min.js - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 932014-09-06 08:44:19 127.0.0.1 GET /Image/Waterful/2014021811405527.JPEG - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 312014-09-06 08:44:19 127.0.0.1 GET /Image/Waterful/2014021811501165.JPEG - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 152014-09-06 08:44:19 127.0.0.1 GET /Image/Waterful/2014022115234855.JPEG - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 152014-09-06 08:44:19 127.0.0.1 GET /Image/Waterful/2014022115350832.JPEG - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 312014-09-06 08:44:19 127.0.0.1 GET /Scripts/UIKit/fonts/fontawesome-webfont.eot - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 312014-09-06 08:44:19 127.0.0.1 GET /favicon.ico - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 404 0 2 152014-09-06 08:44:19 127.0.0.1 GET /__browserLink/requestData/aec8c5e119724733a19c97e269f8d888 version=2 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost:61658/Default.aspx 200 0 0 622014-09-06 08:48:28 127.0.0.1 GET /Default - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+rv:31.0)+Gecko/20100101+Firefox/31.0 - 404 0 2 02014-09-06 08:48:28 127.0.0.1 GET /favicon.ico - 61658 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+rv:31.0)+Gecko/20100101+Firefox/31.0 - 404 0 2 0
Due to the same code, IE is OK in IE and FF, and FF is faulty. IIS suspects can be cleared.
If it is FF, it is OK for other port numbers and will be automatically converted for specific port numbers. So I think what strange operations did I perform during the first debugging,
This causes FF to automatically change http: // localhost: 61658/Default. aspx to http: // localhost: 61658/Default.
At the same time, this automatic transformation is saved to a configuration file of FF.
I don't think it is possible to be a problem with IIS. If IIS saves it internally and accesses an address in FF, it will automatically remove the extension. This may be the result of the immature IIS of VS14 CTP3.
Of course, my machine has not been restarted, maybe it will solve the problem after restarting or deleting all FF caches.
Does anyone know why? Please kindly advise. Thank you.
An intractable disease
For example, it is recommended that you check the local TCM
Case sensitivity of URLs