Номер ошибки: | Ошибка 308 | |
Название ошибки: | Windows Update Error Code 308 | |
Описание ошибки: | Ошибка 308: Возникла ошибка в приложении Windows Update. Приложение будет закрыто. Приносим извинения за неудобства. | |
Разработчик: | Microsoft Corporation | |
Программное обеспечение: | Windows Update | |
Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
Проверка «Windows Update Error Code 308»
Как правило, практикующие ПК и сотрудники службы поддержки знают «Windows Update Error Code 308» как форму «ошибки во время выполнения». Разработчики тратят много времени и усилий на написание кода, чтобы убедиться, что Windows Update стабилен до продажи продукта. К сожалению, такие проблемы, как ошибка 308, могут не быть исправлены на этом заключительном этапе.
После установки программного обеспечения может появиться сообщение об ошибке «Windows Update Error Code 308». В случае обнаруженной ошибки 308 клиенты могут сообщить о наличии проблемы Microsoft Corporation по электронной почте или сообщать об ошибках. Microsoft Corporation вернется к коду и исправит его, а затем сделает обновление доступным для загрузки. Таким образом, в этих случаях разработчик выпустит обновление программы Windows Update, чтобы исправить отображаемое сообщение об ошибке (и другие сообщенные проблемы).
В чем причина ошибки 308?
Проблема с исходным кодом Windows Update приведет к этому «Windows Update Error Code 308», чаще всего на этапе запуска. Три распространенные причины, по которым ошибки во время выполнения, такие как всплывающее окно ошибки 308:
Ошибка 308 Crash — Номер ошибки вызовет блокировка системы компьютера, препятствуя использованию программы. Обычно это происходит, когда Windows Update не может обработать данные в удовлетворительной форме и поэтому не может получить ожидаемый результат.
«Windows Update Error Code 308» Утечка памяти — Ошибка 308 утечка памяти происходит и предоставляет Windows Update в качестве виновника, перетаскивая производительность вашего ПК. Это может быть вызвано неправильной конфигурацией программного обеспечения Microsoft Corporation или когда одна команда запускает цикл, который не может быть завершен.
Ошибка 308 Logic Error — Компьютерная система создает неверную информацию или дает другой результат, даже если входные данные являются точными. Виновником в этом случае обычно является недостаток в исходном коде Microsoft Corporation, который неправильно обрабатывает ввод.
Основные причины Microsoft Corporation ошибок, связанных с файлом Windows Update Error Code 308, включают отсутствие или повреждение файла, или, в некоторых случаях, заражение связанного Windows Update вредоносным ПО в прошлом или настоящем. Основной способ решить эти проблемы вручную — заменить файл Microsoft Corporation новой копией. В некоторых случаях реестр Windows пытается загрузить файл Windows Update Error Code 308, который больше не существует; в таких ситуациях рекомендуется запустить сканирование реестра, чтобы исправить любые недопустимые ссылки на пути к файлам.
Распространенные проблемы Windows Update Error Code 308
Наиболее распространенные ошибки Windows Update Error Code 308, которые могут возникнуть на компьютере под управлением Windows, перечислены ниже:
- «Ошибка программного обеспечения Windows Update Error Code 308. «
- «Ошибка программного обеспечения Win32: Windows Update Error Code 308»
- «Возникла ошибка в приложении Windows Update Error Code 308. Приложение будет закрыто. Приносим извинения за неудобства.»
- «Windows Update Error Code 308 не может быть найден. «
- «Windows Update Error Code 308 не найден.»
- «Ошибка запуска программы: Windows Update Error Code 308.»
- «Файл Windows Update Error Code 308 не запущен.»
- «Отказ Windows Update Error Code 308.»
- «Неверный путь к приложению: Windows Update Error Code 308.»
Проблемы Windows Update Error Code 308 с участием Windows Updates возникают во время установки, при запуске или завершении работы программного обеспечения, связанного с Windows Update Error Code 308, или во время процесса установки Windows. При появлении ошибки Windows Update Error Code 308 запишите вхождения для устранения неполадок Windows Update и чтобы HelpMicrosoft Corporation найти причину.
Источник ошибок Windows Update Error Code 308
Большинство проблем Windows Update Error Code 308 связаны с отсутствующим или поврежденным Windows Update Error Code 308, вирусной инфекцией или недействительными записями реестра Windows, связанными с Windows Update.
Точнее, ошибки Windows Update Error Code 308, созданные из:
- Поврежденные ключи реестра Windows, связанные с Windows Update Error Code 308 / Windows Update.
- Зазаражение вредоносными программами повредил файл Windows Update Error Code 308.
- Другая программа (не связанная с Windows Update) удалила Windows Update Error Code 308 злонамеренно или по ошибке.
- Другая программа, конфликтующая с Windows Update Error Code 308 или другой общей ссылкой Windows Update.
- Windows Update (Windows Update Error Code 308) поврежден во время загрузки или установки.
Продукт Solvusoft
Загрузка
WinThruster 2023 — Проверьте свой компьютер на наличие ошибок.
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
Код ответа состояния перенаправления 308 Permanent Redirect
протокола передачи гипертекста (HTTP) 308 указывает на то, что запрошенный ресурс был окончательно перемещен по URL-адресу, указанному в заголовках Location
. Браузер перенаправляет на эту страницу, и поисковые системы обновляют свои ссылки на ресурс (в «SEO-слове» говорится, что «сок ссылок» отправляется на новый URL-адрес).
Метод запроса и тело не будут изменены, тогда как 301
иногда может быть неправильно изменен на метод GET
.
Примечание. Некоторые веб-приложения могут использовать 308 Permanent Redirect
нестандартным образом и для других целей. Например, Google Диск использует ответ 308 Resume Incomplete
, чтобы указать клиенту, когда незавершенная загрузка остановилась. (См. Выполнение возобновляемой загрузки в документации Google Диска.)
HTTP response status code 308 Permanent Redirect is returned by the server to indicate that the requested resource has been permanently moved to a new location.
Usage
When the 308 Permanent Redirect status code is received, clients are expected to update their stored links to the new URI. This will be specified by the Location HTTP header and can be used by the client for automatic redirection.
This message might be sent by servers that have migrated to a new domain, or have reorganized their internal file structure, and do not plan on reverting to the former URI.
The 308 Permanent Redirect status code differs from the 301 Moved Permanently status code in that the client is required to make an identical HTTP request to the specified Location, whereas 301 Moved Permanently allows for the client to change the HTTP request method. For example, in response to a POST HTTP request by the client, a 301 Moved Permanently HTTP response signals to the client that it is okay to change the POST HTTP request to a GET HTTP request for the subsequent HTTP request. However, 308 Permanent Redirect status code stipulates that if it was originally a POST HTTP request then the follow-up HTTP request also has to be a POST HTTP request.
Example
In the example, the client attempts to retrieve an HTML resource. The server responds to say that the resource has permanently moved to a new URI and includes it in the Location HTTP header. Client-side, a message is presented in the message body to suggest updating the relevant bookmarks, however this is seldom visible in modern browsers which straight away redirect to the new location.
Request
GET /news.html HTTP/1.1
Host: www.example.re
Response
HTTP/1.1 308 Permanent Redirect
Location: http//www.example.re/feeds/news.html
Content-Type: text/html; charset=UTF-8
Content-Length: 150
<h1>The Newsfeed has moved</h1>
<body>
The newsfeed has moved permanently to <a href=/feeds/news.html>here</a>. Please update your bookmarks.
</body>
Code references
.NET
HttpStatusCode.PermanentRedirect
Rust
http::StatusCode::PERMANENT_REDIRECT
Rails
:permanent_redirect
Go
http.StatusPermanentRedirect
Symfony
Response::HTTP_PERMANENTLY_REDIRECT
Python3.5+
http.HTTPStatus.PERMANENT_REDIRECT
Apache HttpComponents Core
org.apache.hc.core5.http.HttpStatus.SC_PERMANENT_REDIRECT
Angular
@angular/common/http/HttpStatusCode.PermanentRedirect
Takeaway
The 308 Permanent Redirect status code indicates that the resource has moved to a new location that is specified within the HTTP response. Clients are expected to update their internal data accordingly and when making the follow-up HTTP request, they are not to change the HTTP request method.
See also
- 301 Moved Permanently
- 302 Found
- RFC 7538
Last updated: August 2, 2023
Jan 11, 2018 6:00:19 PM |
308 Permanent Redirect: What It Is and How to Fix It
A close look at the 308 Permanent Redirect response code, including troubleshooting tips to help you resolve this error in your own application.
A 308 Permanent Redirect message is an HTTP response status code
indicating that the requested resource has been permanently moved to another URI
, as indicated by the special Location
header returned within the response. The 308 Permanent Redirect
code was added to the HTTP standard relatively recently in April 2015, as detailed in the RFC7538 specification document for the 308
status code. As written in the RFC specification, the 308 Permanent Redirect
code was necessary to fill in the gap left with similar codes of 301
, 302
, and 307
.
There are dozens of possible HTTP status codes used to represent the complex relationship between the client, a web application, a web server, and the multitude of third-party web services that may be in use, so determining the cause of a particular HTTP response status code can be difficult. Since there are so many potential codes, each of which represents a completely different status or event, it can be difficult to differentiate between many of them and determine the exact cause of such errors, including the 308 Permanent Redirect
response code.
Throughout this article we’ll explore the 308 Permanent Redirect
code by looking at a handful of troubleshooting tips. We’ll also examine a few useful and easy to implement fixes for common problems that could be causing 308
codes to appear in your own web application. Let’s get down to it!
The Problem is Server-Side
All HTTP response status codes within the 3xx
category are considered redirection messages
. These codes indicate to the user agent (i.e. your web browser) that an additional action is required in order to complete the request and access the desired resource. The 3xx
response code category is distinctly different from the 5xx
codes category, which encompasses server error
messages. For example, the 503 Service Unavailable
error we explored a late last year indicates that a server is temporarily unavailable, or is unable to handle the request for some reason. Thus, while a 5xx
category code indicates an actual problem has occurred on a server, a 3xx
category code, such as 308 Permanent Redirect
, is rarely indicative of an actual problem — it merely occurs due to the server’s behavior or configuration, but is not indicative of an error or bug on the server.
The 308 Permanent Redirect
code is similar to the 301 Moved Permanently
code we explore in our 301 Moved Permanently: What It Is and How to Fix It article. As discussed in that post, the RFC1945 HTTP/1.0 specification document explicitly states that the 301
code should not necessarily inform user agents (i.e. browsers) to automatically redirect POST
HTTP method requests to GET
HTTP method requests. However, many user agents did erroneously change POST
requests to GET
redirect requests, which led to unintentional problems.
To handle this explicit allowance or denial of changing POST
requests to GET
requests the HTTP standards included the following codes:
- 301 Moved Permanently: The resource has been permanently moved and request method conversion from
POST
toGET
is allowed. - 307 Temporary Redirect: The resource has been temporarily moved and request method conversion from
POST
toGET
is forbidden. - 302 Found: The resource has been temporarily moved and request method conversion from
POST
toGET
is allowed.
As you can see, this set of three HTTP status codes is missing a code that indicates a permanent redirect that forbids POST
to GET
conversion. This is the exact role that the 308 Permanent Redirect
status code fulfills.
The appearance of a 308 Permanent Redirect
is usually not something that requires much user intervention. All modern browsers will automatically detect the 308 Permanent Redirect
response code and process the redirection action to the new URI
automatically. The server sending a 308
code will also include a special Location
header as part of the response it sends to the client. This Location
header indicates the new URI
where the requested resource can be found. For example, if an HTTP POST
method request is sent by the client as an attempt to login at the https://airbrake.io
URL, the web server may be configured to redirect this POST
request to a different URI
, such as https://airbrake.io/login
. In this scenario, the server may respond with a 308 Permanent Redirect
code and include the Location: https://airbrake.io/login
header in the response. This informs the user agent (browser) that the POST
request data (login info) was received by the server, but the resource has been permanently moved to the Location
header URI
of https://airbrake.io/login
.
It’s also important to distinguish the purpose and use-cases of the 308 Permanent Redirect
response code from many seemingly similar 3xx
codes, such as the 307 Temporary Redirect
we looked at in the past. The 307 Temporary Redirect
code informs the client that the passed Location
URI
is only a temporary resource, and that all future requests should continue to access the originally requested URI
. On the other hand, the 308 Permanent Redirect
message is permanent and indicates that the passed Location
URI
should be used for future (identical) requests.
Additionally, since the 308 Permanent Redirect
indicates that something has gone wrong within the server
of your application, we can largely disregard the client
side of things. If you’re trying to diagnose an issue with your own application, you can immediately ignore most client-side code and components, such as HTML, cascading style sheets (CSS), client-side JavaScript, and so forth. This doesn’t apply solely to web sites, either. Many smart phone apps that have a modern looking user interface are actually powered by a normal web application behind the scenes; one that is simply hidden from the user. If you’re using such an application and a 308 Permanent Redirect
occurs, the issue isn’t going to be related to the app installed on your phone or local testing device. Instead, it will be something on the server-side, which is performing most of the logic and processing behind the scenes, outside the purview of the local interface presented to the user.
If your application is generating unexpected 308 Permanent Redirect
response codes there are a number of steps you can take to diagnose the problem, so we’ll explore a few potential work around below.
Start With a Thorough Application Backup
As with anything, it’s better to have played it safe at the start than to screw something up and come to regret it later on down the road. As such, it is critical that you perform a full backup of your application, database, and so forth, before attempting any fixes or changes to the system. Even better, if you have the capability, create a complete copy of the application onto a secondary staging
server that isn’t «live,» or isn’t otherwise active and available to the public. This will give you a clean testing ground with which to test all potential fixes to resolve the issue, without threatening the security or sanctity of your live application.
Diagnosing a 308 Permanent Redirect Response Code
A 308 Permanent Redirect
response code indicates that the requested resource has been permanently moved to the new URI
specified in the Location
response header. However, the appearance of this error itself may be erroneous, as it’s entirely possible that the server is misconfigured, which could cause it to improperly respond with 308 Permanent Redirect
codes, instead of the standard and expected 200 OK
code seen for most successful requests. Thus, a large part of diagnosing the issue will be going through the process of double-checking what resources/URLs are generating 308 Permanent Redirect
response codes and determining if these codes are appropriate or not.
If your application is responding with 308 Permanent Redirect
codes that it should not be issuing, this is a problem that many other visitors may be experiencing as well, dramatically hindering your application’s ability to service users. We’ll go over some troubleshooting tips and tricks to help you try to resolve this issue. If nothing here works, don’t forget to try Googling for the answer. Search for specific terms related to your issue, such as the name of your application’s CMS or web server software, along with 308 Permanent Redirect
. Chances are you’ll find others who have experienced this issue and have (hopefully) found a solution.
Troubleshooting on the Server-Side
Here are some additional tips to help you troubleshoot what might be causing the 308 Permanent Redirect
to appear on the server-side of things:
Confirm Your Server Configuration
Your application is likely running on a server that is using one of the two most popular web server softwares, Apache
or nginx
. At the time of publication, both of these web servers make up over 84%
of the world’s web server software! Thus, one of the first steps you can take to determine what might be causing these 308 Permanent Redirect
response codes is to check the configuration files for your web server software for unintentional redirect instructions.
To determine which web server your application is using you’ll want to look for a key file. If your web server is Apache then look for an .htaccess
file within the root directory of your website file system. For example, if your application is on a shared host you’ll likely have a username associated with the hosting account. In such a case, the application root directory is typically found at the path of /home/<username>/public_html/
, so the .htaccess
file would be at /home/<username>/public_html/.htaccess
.
If you located the .htaccess
file then open it in a text editor and look for lines that use RewriteXXX
directives, which are part of the mod_rewrite
module in Apache. Covering exactly how these rules work is well beyond the scope of this article, however, the basic concept is that a RewriteCond
directive defines a text-based pattern that will be matched against entered URLs. If a matching URL is requested by a visitor to the site, the RewriteRule
directive that follows one or more RewriteCond
directives is used to perform the actual redirection of the request to the appropriate URL.
For example, here is a simple RewriteCond
and RewriteRule
combination that matches all incoming requests to airbrake.io
using the HTTP POST
method, and redirecting them to https://airbrake.io/login
via a 308 Permanent Redirect
response:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^airbrake.io$
RewriteRule ^(.*)$ https://airbrake.io/login$1 [R=308]
Notice the extra flag at the end of the RewriteRule
, which explicitly states that the response code should be 308
, indicating to user agents that the request should be repeated to the specified URI
, but while retaining the original HTTP method (POST
, in this case). Thus, if you find any strange RewriteCond
or RewriteRule
directives in the .htaccess
file that don’t seem to belong, try temporarily commenting them out (using the #
character prefix) and restarting your web server to see if this resolves the issue.
On the other hand, if your server is running on nginx
, you’ll need to look for a completely different configuration file. By default this file is named nginx.conf
and is located in one of a few common directories: /usr/local/nginx/conf
, /etc/nginx
, or /usr/local/etc/nginx
. Once located, open nginx.conf
in a text editor and look for return
or rewrite
directives that are using the 308
response code flag. For example, here is a simple block directive
(i.e. a named set of directives) that configures a virtual server by creating a redirection from airbrake.io
to airbrake.io/login
for POST
HTTP method requests:
server {
listen 80;
listen 443 ssl;
server_name airbrake.io;
if ($request_method = POST) {
return 308 https://airbrake.io/login$request_uri;
}
}
Return
directives in nginx
are similar to the RewriteCond
and RewriteRule
directives found in Apache
, as they tend to contain more complex text-based patterns for searching. Either way, look through your nginx.conf
file for any abnormal return
or rewrite
directives that include the 308
flag. Comment out any abnormalities before restarting the server to see if the issue was resolved.
Scour the Logs
Nearly every web application will keep some form of server-side logs. Application logs
are typically the history of what the application did, such as which pages were requested, which servers it connected to, which database results it provides, and so forth. Server logs
are related to the actual hardware that is running the application, and will often provide details about the health and status of all connected services, or even just the server itself. Google «logs [PLATFORM_NAME]» if you’re using a CMS, or «logs [PROGRAMMING_LANGUAGE]» and «logs [OPERATING_SYSTEM]» if you’re running a custom application, to get more information on finding the logs in question.
Debug Your Application Code
If all else fails, it may be that a problem in some custom code within your application is causing the issue. Try to diagnose where the issue may be coming from through manually debugging your application, along with parsing through application and server logs. Ideally, make a copy of the entire application to a local development machine and perform a step-by-step debug process, which will allow you to recreate the exact scenario in which the 308 Permanent Redirect
occurred and view the application code at the moment something goes wrong.
No matter what the cause, the appearance of a 308 Permanent Redirect
within your own web application is a strong indication that you may need an error management tool to help you automatically detect such errors in the future. The best of these tools can even alert you and your team immediately when an error occurs. Airbrake’s error monitoring software provides real-time error monitoring and automatic exception reporting for all your development projects. Airbrake’s state of the art web dashboard ensures you receive round-the-clock status updates on your application’s health and error rates. No matter what you’re working on, Airbrake easily integrates with all the most popular languages and frameworks. Plus, Airbrake makes it easy to customize exception parameters, while giving you complete control of the active error filter system, so you only gather the errors that matter most.
Check out Airbrake’s error monitoring software today and see for yourself why so many of the world’s best engineering teams use Airbrake to revolutionize their exception handling practices!
An IETF RFC draft The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect) defines HTTP status 308 as Permanent Redirect. It should, of course, be noted that this is a draft document and contains in its document header the text «Expires: September 27, 2012», which I presume would mean it should be considered invalid now, but I’m not familiar with IETF’s processes and so don’t feel confident about this.
The Wikipedia article List of HTTP status codes uses this definition of 308, also:
308 Permanent Redirect (approved as experimental RFC)[12]
The request, and all future requests should be repeated using another URI. 307 and 308 (as proposed) parallel the behaviours of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.
…
[12]: «The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)». IETF. 2012. Retrieved March 27, 2012.
Eric Law, of Microsoft at the time, comments on this HTTP/308 code in Pushing the Web Forward with HTTP/308. That caused me to discover that Firefox supports 308 under this meaning.
However, when I was looking in the python-requests library, I found that there is another usage of 308:
308: ('resume_incomplete', 'resume'),
This seems to come from a Google Gears resumable HTTP requests proposal, defining 308 Resume Incomplete
. There seems to be some usage of that. Of course, neither of these proposals acknowledges the existence of the other.
So what’s going on? Is 308 Permanent Redirect
alive? What’s happening with the status code 308? What should I do?