Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.
IIS not publishing images
Strange problem I am having. I have three website servers running IIS. Two of them work fine. Each server is paired with its own separate file server that stores the images that the website looks for and publishes. The third one will give a web page but the pictures have that "missing image" look. Now, we thought it might be something wrong with the file server but the other two servers, when we change the path, are able to get images off the file server that is paired with the third IIS. We even pointed the third server to look at the other two file servers and we got the same results. Quite confusing. Any ideas?
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
All three IIS servers are on 2012 R2. I don't know if I ran that correct or not but the response I got was content-type txt/html. I might have typed something wrong because there is no return echo when I type.
We are running ASP.net to run the whole website
Here is the return I got when I put in the above. BTW was the spelling of refererer supposed to be referrer?
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 07 Jun 2015 14:57:38 GMT
Connection: close
Content-Length: 326
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/str
ict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Verb</h2>
<hr><p>HTTP Error 400. The request verb is invalid.</p>
</BODY></HTML>
Connection to host lost.
C:\Users\Home>
We are running ASP.net to run the whole website
Here is the return I got when I put in the above. BTW was the spelling of refererer supposed to be referrer?
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 07 Jun 2015 14:57:38 GMT
Connection: close
Content-Length: 326
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/str
ict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Verb</h2>
<hr><p>HTTP Error 400. The request verb is invalid.</p>
</BODY></HTML>
Connection to host lost.
C:\Users\Home>
The response you received is an error.
Does the .net application you use the same on all three or does each have their own written app.
Look at the source on IIS server 3 for the <Img src=
The issue is either the mechanism does not allow access to the fileserver where the images are stored in this case or the output image is not properly designated as image/png etc.
Do you have an asp page that you can use that will access the fileserver share and list the names and directories within the share?
The issue is isolated to the IIS server 3 since none of the other fileservers can be accessed.
Does the .net application you use the same on all three or does each have their own written app.
Look at the source on IIS server 3 for the <Img src=
The issue is either the mechanism does not allow access to the fileserver where the images are stored in this case or the output image is not properly designated as image/png etc.
Do you have an asp page that you can use that will access the fileserver share and list the names and directories within the share?
The issue is isolated to the IIS server 3 since none of the other fileservers can be accessed.
Actually I found the problem. Feeling pretty dumb. We set the virtual directory to the image server and forgot to put the right permissions in the virtual directory. :-) Problem solved. I had a feeling it was something simple and stupid :-)
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server
From novice to tech pro — start learning today.
-
Microsoft IIS Web ServerCertification: MCP Microsoft Certified Partner - Installing and Configu… 288 lessons
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Word 2016 Part … 125 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
What is the mechanism that accesses the files from the file server?
Try the following
telnet thirdiisserver 80
GET http://URL/image path/image HTTP/1.1
Host: your_hostname
Refererer:
And see what you get as a response, the item of interest is the HTTP header I.e. you might be outputting the wrong Content-Type:
This presumes that you have an ASP or some dynamic script that accesses the file share and feeds/streams the image to the user.
At times a better approach is to place a reverse proxy I front of the dynamic content such that the static images are fed from the proxy.