خطا در هنگام لاگین کاربران!

[yaser1]

[quote author=مجید link=topic=12907.msg68550#msg68550 date=1208282422]
405 - Method Not Allowed
[/quote]
سلام
این خطا یعنی چی و چطوری میشه رفعش کرد؟
بعد از انتقال بکاپم روی یه هاست دیگه، موقع لوگین کاربران به سایت این خطا دیده میشه

HTTP/1.1 405 Method not allowed

من در برنامه نویسی اش تغییری نداده ام!. همین نسخه الان در جای دیگه داره کار می کنه و این نسخه فقط یه بکاپ از اونه که روی هاست جدید این خطا رو میده.

بعدشم مشکل من فقط با IE نیست!

در IE خطای Can not be displayed
و
در FF3 خطای HTTP/1.1 405 Method not allowed رو می بینم

[atoofy]

سلام.فایل های بک آپ کامل و سالم اند؟
این بک آپ را روی جای دیگه هم تست کردید؟

یــــــــــــــــاعــــــ ــــــــــلی

[yaser1]

سلام
سلامتشون رو چطوری باید چک کنم؟ جای دیگه هم نصب نکردم چون هاست دیگه ای ندارم

[atoofy]

سلام.یکی از راه هاش مقایسه حجم فایل های مبدا و مقصدهست که خوب مشکلات خاص خودشو داره.

-روی لوکال...

یـــــــــــــــــــاعـــ ـــــــــــــــلی

[yaser1]

سلام
حجمشون یکیه!

[atoofy]

سلام. تست هم کردید؟(روی لوکال)
در نهایت می خواهیم مطمئن بشیم که مشکل از بک آپ نبوده...

یـــــــــــــــاعـــــــ ــــــــلی

[yaser1]

سلام
تا عصر برسم خونه... ممنون از پیگیریت علی آقا

[yaser1]

سلام
روی لوکال این خطا رو میده :
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 367 bytes) in C:\wamp\www\fa\includes\database.php on line 332

شبیه ساز م wamp هست و تا حالا مشکلی باهاش نداشتم. الان رفتم در php.ini مقدار memory_limit رو هم از 8 به 256 تغییر دادم اما همون پیغام رو میده

بی خیال این خطا! کسی مشکل اصلی منو نمیدونه چطوری میشه حل کرد؟

[mhadaily]

یاسر تاجایی که یادم زبانت خوب بود پس اینجا رو بخون

HTTP Error 405 - Method not allowed

Introduction

  The HTTP protocol defines methods to indicate the action to be performed on the Web server for the particular URL resource identified by the client (e.g. your Web browser or our CheckUpDown robot). The methods are as follows:

    * OPTIONS: Find out the communication options available for a particular URL resource. Allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without a specific action involving transfer of data.
    * GET: Retrieve the information identified by the URL resource e.g. GET a particular Web page or image. The most common method by far.
    * HEAD: Identical to GET except that the server returns header information only, not the actual information identified by the URL resource. Useful to obtain metainformation about the entity implied by the request without transferring the entity-body itself. Often used to test hypertext links for validity, accessibility, and recent modification.
    * POST: Submit data to the Web server such as 1) post a message to a bulletin board, newsgroup or mailing list, 2) provide input data - typically from a CGI form - to a data-handling process, 3) add a record directly to a database.
    * PUT: Set (place/replace) the data for a particular URL to the new data submitted by the client. For example, upload a new Web page to a server.
    * DELETE: Remove the data associated with the URL resource. For example, delete a Web page.
    * TRACE: Run a remote, application-layer loop-back of the request message. Effectively a 'ping' which tests what data the Web server is receiving from the client.
    * CONNECT: Reserved for use with tunneling (e.g. SSL) via a proxy server. This method is defined only for HTTP version 1.1, not the earlier version 1.0.

  All Web servers can be configured to allow or disallow any method. For example if a Web server is 'read-only' (no client can modify URL resources on the Web server), then it could be set up to disallow the PUT and DELETE methods. Similarly if there is no user input (all the Web pages are static), then the POST method could be disallowed. So 405 errors can arise because the Web server is not configured to take data from the client at all. They can also arise if the client does not have sufficient authority to the particular URL resource identified on the request.

405 errors in the HTTP cycle

  Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:

    * Obtain an IP address from the IP name of your site (your site URL without the leading '[مهمان/کاربر گرامی برای دیدن لینک ها ابتدا باید عضو سایت شوید و لاگین کنید برای ثبت نام اینجا کلیک کنید]). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
    * Open an IP socket connection to that IP address.
    * Write an HTTP data stream through that socket.
    * Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

  This error occurs in the final step above when the client receives an HTTP status code that it recognises as '405'.

Resolving 405 errors - general

  405 errors often arise with the POST method. You may be trying to introduce some kind of input form on your Web site, but not all ISPs allow the POST method necessary to process the form.

  All 405 errors can be traced to configuration of the Web server and security governing access to the content of the Web site, so should easily be explained by your ISP.

Resolving 405 errors - CheckUpDown

  This error should simply never occur on your CheckUpDown account. If it does, it typically indicates defective programming of our systems or of the Web server which manages your site. We use the GET method only, which all Web servers should allow (otherwise no-one would ever be able to see your Web site).

  Please contact us (email preferred) whenever you encounter 405 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of your Web server software to agree the exact reason for the error.

[yaser1]

سلام
یعنی متد پست روی سرور جدید اجازه داده نشده؟ همین؟
من همینو فهمیدم. اگه چیز دیگه ای هم باید در تنظیمات سرور تغییر کنه لطفاً بفرمائید
سپاس