HTTP response status code 409 Conflict is a client error that is returned by the server to indicate that the request can not be satisfied because the current state is incompatible with what is required. The response from the server may contain information in the message body that the client can use to resolve the conflict.
Usage
When the 409 Conflict error message is received, it means that the request is valid, but cannot be completed due to some kind of mismatch. For example, if the client is replying to a post that has since been deleted, then the target resource is no longer in a compatible state and the server may return this status.
The client is expected to examine the message body to determine how to resolve the conflict. In the case of replying to the deleted post, the client may opt to abandon the request. Alternatively, it can undelete the former thread or instead, create a new thread with the former text quoted. This action will be entirely the responsibility of the client, following any requirements or policies put in place by the server.
Note
Search engines like Google will not index a URL with 409 Conflict response status, and consequently, URLs that have been indexed in the past but are now returning this HTTP status code will be removed from the search results.
Example
In the example, the client attempts to tag an existing blog post with “ID = 111” with a “like”. The server responds to say that the post has been frozen and can no longer accept replies or tags.
Request
POST /blog/update?postid=111&flag=like HTTP/1.1
Host: www.example.ai
Response
HTTP/1.1 409 Conflict
Content-Type: text/html
Content-Length: 288
<html>
<head>
<title>Blog Entry Frozen</title>
</head>
<body>
<p>This post has been marked read-only. To post a reply or tag it, please change the status and try again.</p>
</body>
</html>
Code references
.NET
HttpStatusCode.Conflict
Rust
http::StatusCode::CONFLICT
Rails
:conflict
Go
http.StatusConflict
Symfony
Response::HTTP_CONFLICT
Python3.5+
http.HTTPStatus.CONFLICT
Java
java.net.HttpURLConnection.HTTP_CONFLICT
Apache HttpComponents Core
org.apache.hc.core5.http.HttpStatus.SC_CONFLICT
Angular
@angular/common/http/HttpStatusCode.Conflict
Takeaway
The 409 Conflict status code is a client error that the server sends to indicate that the resource is not in a state that is compatible with the request. The response may contain information sufficient to rectify the problem and allow the request to be resubmitted.
See also
- RFC 7231
Last updated: June 2, 2022
Ошибка HTTP 409 Conflicting Request – это конфликт между запросом пользователя и сервером, к которому он обращается. Например, есть сайт, с которого пользователь хочет скачать файл с названием «файл1», но этот файл раньше был на сервере и его упоминание сохранилось в кеше. Однако, теперь файл называется “файл01» и сервер не понимает, что пользователь хочет от него. Это очень образный пример для того, чтобы максимально понятно определить значение ошибки.
Ситуации при которых возникает ошибка 409 HTTP сильно разнятся, но сводятся к конфликту между запросами. Иногда, задавая запрос, браузер сам уходит в цикличную обработку, и он либо закрывается, либо виснет так, что пользователю ничего не остается, как просто перезагрузить компьютер. Это явление часто замечают пользователи браузера Mozilla и Opera.
Выше упоминалось, что природа происхождения ошибки 409 кроется в конфликте запросов. Не всегда эти запросы относятся к пользовательским. Например, такая ошибка может возникнуть при конфликте файлов сайта, если они обращаются к разным данным в одном файле. В результате этого, сервер возвращает ошибку, которая на самом деле не имеет отношения к запросам пользователей.
Основные причины возникновения ошибки 409:
- Пользователь обращается к данным, имеющим отличное значение или более новую версию. В итоге, сервер выдает ошибку 409, т.к. существует обновленная версия файла, страницы или скрипта.
- Ошибка 409 появилась в результате конфликтующих запросов внутри файлов на сервере. Решить проблему может программист.
- Использование прокси, которое конфликтует с определенными адресами или форматами запрашиваемых данных. Не путайте эту ошибку с ошибкой 407.
- Более распространенная причина – троян или вирус, который блокирует запросы к определенным сайтам или подгружает файл, который имеет конфликт с конфигурацией браузера.
Ошибка 409 Conflicting Request в большинстве случае решается системным администратором или программистом, если это не касается заражения компьютера вирусом или трояном. Как проверить и какой программой расскажем ниже.
Как исправить ошибку 409 (Conflicting Request – Конфликт запросов)?
На некоторых сайтах приведен целый список шагов для устранения ошибки 409. Вот только проблема в том, что это не имеет смысла, т.к. эта ошибка касается программистов или разработчиков сайта / приложения. Конечный пользователь не сможет исправить ошибку 409, если только это не касается вируса или трояна.
- Чистим от вируса или трояна, чтобы убрать ошибку 409
Определить вирус/троян у вас или нет просто – установите программу Cureit от Dr.Web и просканируйте систему этой программой. Она бесплатная и не требует установки. Скачиваем только с официального сайта. В программе отмечаем все пункты для проверки и шагаем спать/на работу, т.к. сама проверка займет длительное время. На скриншоте ниже вы можете рассмотреть, как и что отмечать в программе. Свой антивирус лучше отключить перед проверкой.
Чистим от вируса или трояна, чтобы убрать ошибку 409
Можно также использовать бесплатную утилиту от Касперского, но она довольно сложная и нужно понимать, какие скрипты вводить в консоль. Остальные программы – платные, поэтому не пишу о них. Кстати, не рекомендую скачивать бесплатные ключи, т.к. такие генераторы могут с собой принести тот самый вирус или троян. Не пожалейте 30$ в год за нормальную защиту.
- Исправляем ошибку 409 в конкретном браузере
В случае, если ошибка 409 Conflicting Request появляется буквально на каждом сайте, чтобы вы ни нажимали – это точно троян или вирус. Причем это должно происходить в любом браузере. Если нет – можете сразу удалить и заново установить браузер. Возможно произошел сбой конфигурации браузера.
Перед удалением браузера сохраните закладки!
Заранее нужно сохранить закладки, т.к. можно потерять все нажитое непосильным трудом. Делается это просто. На скриншоте выше вы видите пример сохранения настроек в браузере Mozilla. Аналогично делается и в остальных браузерах.
- Ошибка 409 в результате правок на сайте
Если вы являетесь администратором сайта или программистом… Вы знаете, что такое бэкап и как им пользоваться. Если не знаете – спросите в комментариях. Что с ним делать? Думаю, ответ знаете сами.
Последнее слово про ошибку
Ошибка 409 HTTP Conflicting Request редко относится к пользователю, если только это не вирус или троян. Почти 80% случаев с этой ошибкой касается разработчиков, поэтому разбираться в этом нужно точно не обычному пользователю. Все советы про чистку реестра и прочее – не актуальны. Это не относится к этой ошибке.
Если уж сильно хочется – установите программу CCleaner и пройдитесь по реестру с помощью этой программы. Во всяком случае это безопаснее, чем делать что-то лично ручками. Манипуляции с компьютером в случае с ошибкой 409 делать не стоит.
When you attempt to view a website, you may see an error message that prevents you from accessing the page. If the server notices a conflict between the HTTP request and the resource, it will display a “409 Conflict” error.
Although this scenario can be frustrating, you can easily fix the 409 error. On the client side, you can fix typos in the requested URL, clear your browser cache, and uninstall browser extensions. Alternatively, you can solve this conflict as a website administrator by uninstalling core software and plugins or reviewing your server configuration.
In this post, we’ll give you an overview of the 409 error and its causes. Then, we’ll show you how to check your website for this issue and fix it if necessary. Let’s get started!
Check Out Our Video Guide to Fixing the “409 Conflict” Error
What Is the “409 Conflict” Error?
After making an HTTP request (such as loading a page), you may see an error message informing you that the request couldn’t be completed. In most cases, your browser will tell you what went wrong.
For example, a 400 Bad Request error will occur after a client-side error, like incorrect request syntax, corrupted browser cache, or large file sizes:
However, there are many other HTTP status codes. They belong to five different classes:
- 100s: Informational status codes that indicate continuing requests.
- 200s: Success codes for well-functioning requests.
- 300s: Redirection messages explaining a redirect to another resource.
- 400s: Error codes for client-side problems.
- 500s: Error codes for server-side issues.
If you see a “409 Conflict” error, this is a 400 HTTP status code. In short, the request wasn’t completed because of a conflict with the resource’s current state.
Although this issue might seem complicated, you can usually resolve the conflict and try the request again. Fortunately, unlike server-side errors, the “409 Conflict” error code has some simple solutions.
Don’t worry- fixing the 409 error is easier than it may seem! 🚀 Keep reading to see exactly how to get it sorted… 💪Click to Tweet
What Causes the “409 Conflict” Error?
As its name suggests, the “409 Conflict” error results from some conflict in the HTTP request. It may happen because the requested resource is not in its expected state. Alternatively, the request itself could create a conflict if completed.
A 409 error usually occurs in response to a PUT request. This request updates the target resource. You can use a PUT request to make a new resource or replace an existing one.
However, if there are conflicting values in the PUT payload, they can cause a 409 error. For example, if you mistype certain fields, the server can notice these inconsistencies and reject the request.
You might also see a 409 response if you try to upload a file to your site that’s older than the existing one. Doing this will create a version control conflict that can result in a 409 error.
How To Locate the “409 Conflict” Error
To identify any 409 errors on your website, you can evaluate your HTTP requests and start troubleshooting them. This process will depend on the web hosting company for your site.
With a Kinsta hosting plan, you can manage your site logs in the MyKinsta dashboard. First, log in to your account and select the Sites tab. Then, choose the website you want to evaluate:
This will open a page with basic information about your website. On the left-hand side, click on the Logs option:
After opening the Log viewer, you can see a record of specific errors on your website. If you don’t see a 409 error here, switch to access.log, which contains all of the requests processed by DevKinsta:
Here is the basic information you’ll see in each request:
- Date and time
- Request (method and URI)
- HTTP error code or “200 OK” for successful requests
- Bytes sent
- HTTP referer
- User-agent
- HTTP X Forwarded for
You can look through the list of server requests to find any 409 HTTP status codes. Be sure to look for PUT requests since these can also contribute to conflict errors.
If needed, you can use the search bar to filter your results. Once you locate a “409 Conflict” error, you can proceed with the following solutions.
How To Fix the “409 Conflict” Error (5 Methods)
Even after you experience a 409 error, there are a few ways to resolve it. If you’re unsure what’s causing the issue, you may have to try a combination of different methods. Here are five of the most common fixes!
1. Check the Requested URL
As we mentioned earlier, the “409 Conflict” error can arise from incorrect information in a PUT request. When updating a resource, you’ll want to make sure that you entered its destination correctly.
Before you try more complex solutions, it’s a good idea to review the requested URL. If you manually entered this information, you may have accidentally made a typo that caused an error in the request.
If you made a mistake in this data, you can correct it and try the request again. Sometimes, this will enable you to continue with the request without causing a 409 error.
You can also try simply refreshing the page. Sometimes, old errors can disappear given enough time. Plus, the website owner could have already resolved the issue.
2. Clear Your Browser Cache
When you first view a website, your browser stores that page’s data in a cache. This way, you can easily reaccess those resources. Once you visit the site a second time, your browser will pull the cached data instead of requesting the resources from the server.
After you’ve recently fixed an error in your request, like a mistyped URL, you may still see the 409 error. Although the issue could already be resolved, the error message might still display because of your browser cache. In this case, you can clear your cache to remove the HTTP status code.
The method you use to do this will depend on your browser type. For Google Chrome users, you can start by clicking the three-dot icon in the top-right corner of the page. Then select More Tools > Clear Browsing Data:
In the new pop-up, select Cached images and files. If needed, you can also clear your browsing history, cookies, and other site data. Then, click on Clear data:
Although this will clear most of your cache, your browser will likely keep additional data that most users don’t want to be deleted. However, if you want to remove your full cache, navigate to the Advanced tab:
Here, you can select the data you want to delete from your cache. You can choose from these options:
- Browsing history
- Download history
- Cookies and other site data
- Cached images and files
- Passwords and other sign-in data
- Autofill form data
- Site settings
- Hosted app data
Once you specify the information to remove, click on Clear data. Now you can try the request again to see if the 409 error has been resolved!
3. Roll Back Recent Updates
Sometimes, HTTP error codes can be caused by conflicting software. To troubleshoot a “409 Conflict” error, consider downgrading your WordPress website. This downgrade can help you evaluate whether the core software conflicted with other tools on your site.
However, you’ll need to back up your website before starting this process. If not, you risk losing important changes you made with this new software update. After troubleshooting the issue, you can quickly restore your site to its former state.
Since Kinsta performs daily automatic backups, you can downgrade WordPress by restoring a previous backup. To do this, click on the Backups tab in your MyKinsta dashboard:
Then, select the backup you want to restore. Click on Restore to and choose whether to implement these changes in your staging environment or live site:
Finally, confirm the restoration by entering the given text:
If you updated your website long ago, you’ll likely need to use another method of downgrading your site. Since Kinsta only saves your daily backups for 14 days, you may not be able to restore an older version.
As an alternative, you can install the WP Downgrade plugin. This tool will enable you to easily reinstall an older version of WordPress:
First, install and activate the plugin. Then go to Settings > WP Downgrade:
Enter the exact number for the previous WordPress version to downgrade your software. When you’re finished, save your changes.
You may want to consider rolling back your computer update as well. For Windows users, you can do this in the update history settings. You can also downgrade a Mac computer by reverting to a Time Machine backup.
4. Uninstall Plugins and Extensions
If you don’t want to downgrade your website completely, you can deactivate your plugins and third-party tools. By removing this software, you’ll likely eliminate any conflicts.
To deactivate your plugins, go to the Plugins page on your WordPress dashboard. Then, select all of your plugins:
Click on the Bulk actions menu and select the Deactivate option. To finalize these changes, hit Apply:
Now you can try the request to see if you receive the 409 error. If the request is successful, you’ll know there was a conflict with one of your plugins.
To identify which plugin is causing the issue, activate each plugin one at a time. After each activation, check to see if the error happens again.
Once you locate the problematic plugin, you can delete it. If it performs a necessary task on your website, consider browsing the WordPress Plugin Directory for an alternative. Usually, you can find a different tool with similar functionality.
Alternatively, there could be an issue on the client-side of the request. To solve a 409 error, you can disable your browser extensions. On Chrome, go to More Tools > Extensions:
This will open a list of your enabled extensions. To disable them, make sure the switch next to each one is turned off:
You can also delete the extensions completely. This should eliminate any software conflicts. However, you should only do this with unnecessary tools.
5. Review Your Server Configuration
As a last resort, you can check your server configuration for errors. In MyKinsta, you can use the built-in Application Performance Monitoring (APM). With this APM tool, you can identify any long external requests, unoptimized plugin code, and slow database queries:
To open the Kinsta APM, sign in to MyKinsta. Next, head to Sites > Kinsta APM:
Then, you’ll have to enable performance monitoring for a certain period. At the top of the page, click on Enable:
In the pop-up window, select the amount of time you want Kinsta to evaluate. You can enable a monitoring time window between 2 hours and 24 hours:
After you enable performance monitoring, you can use your results to troubleshoot the 409 error. You’ll be able to view all your requests and analyze your server’s response time:
Alternatively, you can use the Query Monitor plugin. This free tool enables you to see the performance level of your database queries, scripts, hooks and actions, block editor blocks, and more:
First, install and activate Query Monitor. Then, click on the new tab at the top of your WordPress dashboard:
Here, you can view reports for your site’s queries, requests, scripts, and other data. Under HTTP API Calls, you can see a list of any request errors:
With either of these tools, you can easily find 409 errors and discover the root cause of the issue. Then you don’t have to waste time troubleshooting other areas of your website.
There are several options to fix this error- and they’re all covered in this helpful guide 🚀Click to Tweet
Summary
When a conflict occurs during a request, you’ll likely see a 409 error. In this case, the server can’t send the relevant information because of a problem with the state of the requested resource. After identifying the conflicting requested values, you can try the request again.
To review, here’s how you can fix the “409 Conflict” error in WordPress:
- Check the requested URL.
- Clear your browser cache.
- Roll back recent updates.
- Uninstall plugins and extensions.
- Review your server configuration.
With Kinsta web hosting, we provide all the tools you need to troubleshoot performance errors as soon as they occur. Using our APM, you can review your external requests and fix conflicts to keep your website functioning properly!
The 409 HTTP Status Code means that the request is in conflict. The 409 HTTP Status Code indicates that the request could not be processed due to a conflict in the request, such as the requested resource not being in the expected state, or the processing of the request causing a conflict within the resource. Data constraint violations and concurrent modification exceptions are two scenarios in which an HTTP 409 Status Code would be used within Agile Lifecycle Manager. The difference between the 409 HTTP Status Code and the 400 HTTP Status Code is that the 400 HTTP Status Codes could not understand the request due to invalid syntax, whereas the 409 HTTP Status Code sent a response when a request conflicted with the server’s current state.
What does 409 HTTP Status Code Mean?
The 409 HTTP Status Code indicates a request conflict with the target resource’s current state. Conflicts are most likely to arise as a result of a PUT request. For example, if you upload a file that is older than the one already on the server, you may receive a 409 response, resulting in a version control conflict.
How to Use 409 HTTP Status Code for a Website?
Conflicts are most likely to arise as a result of a PUT request. For example, if versioning is used and the representation being PUT includes changes to a resource that conflict with those made by an earlier third-party request, the origin server may respond with a 409 HTTP Status Code to indicate that it is unable to complete the request. Based on the revision history, the response representation would most likely contain information useful for merging the differences in this case.
How to Check 409 HTTP Status Code?
To check the 409 HTTP Status Code use the web browser network tab and developer tools for every resource that the client uses.
Which HTTP Method is used with 409 HTTP Status Code?
There is only one HTTP method used with the 409 HTTP Status Code which is the PUT HTTP method. The PUT HTTP method is used to 409 HTTP Status Code to include changes to a resource that conflict with those made by an earlier third-party request.
The PUT HTTP method replaces the request payload with all existing representations of the target resource.
There is only one related HTTP Response Header with the 409 HTTP Status Code which is the 412 HTTP Status Code because they are both client error responses that do not understand the request due to invalid syntax.
What are the Browsers Compatibility of the 409 HTTP Status Code?
You can see the table that shows the browser’s compatibility with the 409 HTTP Status Code below.
| Browser Name | Browser Compatibility of 409 HTTP Status Code |
| Chrome | YES |
| Edge | YES |
| Firefox | YES |
| Internet Explorer | YES |
| Opera | YES |
| Safari | YES |
| WebView Android | YES |
What are the other Similar Status Codes to 409 HTTP Status Code?
There are other similar HTTP Status Codes to 409 HTTP Status Code. The following HTTP Status Codes are listed below.
- 400 Bad Request HTTP Status Code: Due to incorrect syntax, the server was unable to understand the request. The 400 HTTP Status Code is similar to the 409 HTTP Status Code which is also a client error response.
- 401 Unauthorized HTTP Status Code: Although the HTTP standard specifies “unauthorized,” this response means “unauthenticated” semantically. That is, in order to receive the requested response, the client must authenticate itself. The 401 HTTP Status Code is similar to the 409 HTTP Status Code which is also a client error response.
- 402 Payment Required HTTP Status Code: The 402 Payment Required HTTP Status Code will be used in the future. The initial goal of developing this code was to use it in digital payment systems; however, the 402 HTTP Status Code is rarely used, and no standard convention exists. The 402 HTTP Status Code is similar to the 409 HTTP Status Code which is also a client error response.
- 403 Forbidden HTTP Status Code: Because the client lacks access rights to the content and is thus unauthorized, the server refuses to provide the requested resource. Unlike 401 Unauthorized, the server knows who the client is. The 403 HTTP Status Code is similar to the 409 HTTP Status Code which is also a client error response.
- Author
- Recent Posts
Holistic SEO & Digital has been built by Koray Tuğberk GÜBÜR. Holistic SEO is the process of developing integrated digital marketing projects with every aspect including Coding, Natural Language Processing, Data Science, Page Speed, Digital Analytics, Content Marketing, Technical SEO, and Branding. Structured, Semantic Search Engine improves its ability to detect the real-world entities, today. Having a simple website is not enough anymore. To show that your brand is authoritative, trustworthy, and expert on its own niche, you need entity-based Search Engine Optimization Projects. Holistic SEO & Digital’s main focus is on improving the brand’s organic visibility and growth potential.
Код состояния ответа HTTP 409 Conflict указывает на конфликт запроса с текущим состоянием целевого ресурса.Конфликты чаще всего возникают в ответ на запрос PUT.
Ошибка,возникающая,когда файл не может быть создан из-за конфликта.
Действие создания обычно реализуется с помощью метода POST HTTP. В RESTful API эти конечные точки используются для создания новых ресурсов или токенов доступа. 200 OK — это основной код состояния, сообщающий клиенту, что все прошло хорошо.
Что такое код состояния 409? Запрос не может быть выполнен из-за конфликта с текущим состоянием целевого ресурса.Этот код используется в ситуациях,когда пользователь может разрешить конфликт и повторно отправить запрос.
Код ответа на ошибку клиента HyperText Transfer Protocol (HTTP)410 Gone указывает на то,что доступ к целевому ресурсу больше не доступен на сервере происхождения и что это состояние,вероятно,является постоянным.
Код зоны 409-это телефонный код зоны в Североамериканском плане нумерации (NANP)для американского штата Техас.В зону действия плана нумерации входят районы Бомонт и Галвестон.
Код состояния ответа протокола передачи гипертекста (HTTP)400 Bad Request указывает,что сервер не может или не хочет обрабатывать запрос из-за чего-то,что воспринимается как ошибка клиента (например,неправильный синтаксис запроса,некорректное обрамление сообщения запроса или обманчивая маршрутизация запроса).