Kryptronic Software Support Forum

You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.

#1 12-11-2017 01:38:00

dh783
Moderator
From: Avondale, Arizona
Registered: 04-06-2005
Posts: 6233
Website

Problem resolving root media directory

After a server crash and rebuild, including a fresh install of ccp8 I seem to be having problems in accessing the files contained in the root/media directory. It seem to be the directory name of "media" as any other name does not cause a problem, even if I rename the call for the directory to "Media". So the following call thru WC3 CSS validator of:

Code:

http://www.slpdoghousemusic.com/media/skins/css/all.css

returns a "Bad request" response and thus does not get read. If I change the request to

Code:

http://www.slpdoghousemusic.com/Media/skins/css/all.css

it does read the all.css file, but the actual directory is named "media". While the site will not pull file information from the "root/media/" directory it is not calling any of the JS scripts, the base all.css information and no images for the site. Has anyone seen this problem before?

Offline

 

#2 12-11-2017 08:09:30

webmaster
Administrator
From: York, PA
Registered: 04-20-2001
Posts: 19514
Website

Re: Problem resolving root media directory

I'm assuming you've got a webserver rewrite rule (either local .htaccess, vhost-based, or server-wide httpd.conf) which is rewriting requests for /media to something else.  Eliminate that rule, restart the webserver and you should be able to use that directory name.


Nick Hendler

Offline

 

#3 12-11-2017 10:26:26

dh783
Moderator
From: Avondale, Arizona
Registered: 04-06-2005
Posts: 6233
Website

Re: Problem resolving root media directory

I know it's not a local htacces as it was happening before I created one with the standard ccp8 entries hoping that might clear it up. The other strange part is I pointed a different url to the public root directory (wwwslpservone.com) as a test but the http:// (port 80) side will not pull form the "media" directory at all but the https:// (prot 443) side pulls the js scripts with out changing to the upper case of the directory (Media) but does not get the all.css files located in media/skins/css/.  I will go looking into the httpd.conf  file. Thnaks

Offline

 

#4 12-11-2017 12:40:40

dh783
Moderator
From: Avondale, Arizona
Registered: 04-06-2005
Posts: 6233
Website

Re: Problem resolving root media directory

I checked the httpd.config file, didn't see any thing that should cause the problem. Any other ideas?

Offline

 

#5 12-12-2017 08:29:02

webmaster
Administrator
From: York, PA
Registered: 04-20-2001
Posts: 19514
Website

Re: Problem resolving root media directory

http://www.slpdoghousemusic.com/media/skins/css/all.css comes up with a Mac OSX error '400: Unimplemented method'.  Doing a Google search on that brings up similar issues with /media directories and OSX. 

https://discussions.apple.com/thread/22 … p;tstart=0
https://forum.joomla.org/viewtopic.php?t=894687
https://www.spinics.net/lists/apache-us … 11755.html

Seems like there is a rewrite in the config you're missing.  Not much info on where.


Nick Hendler

Offline

 

#6 12-12-2017 17:29:51

dh783
Moderator
From: Avondale, Arizona
Registered: 04-06-2005
Posts: 6233
Website

Re: Problem resolving root media directory

Nick, you where correct, Mac OSX webserver has a "Web Services" tab which has selections for Wikis, Blogs, Calendar, Mail, configure-server-side-mail-rules and "change their password", it seems that any one of these will cause the problem of the media directory being redirected leaving the current web page with a "Bad Response" 400 error.
Funny all searches I did on the subject came up with ending a command with \r\n instead of \n which didn't make much sense to me either.

Thanks.

Offline

 

#7 12-13-2017 08:20:00

webmaster
Administrator
From: York, PA
Registered: 04-20-2001
Posts: 19514
Website

Re: Problem resolving root media directory

Glad to hear it's resolved.  FYI, line endings on Macs, Windows and Unix are all different defaults.  You're using a Mac webserver, so I'd assume the comments regarding line endings you were reading were regarding importing or editing configuration files and ensuring you were using proper line endings for the OS.


Nick Hendler

Offline

 

Board footer