url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0ODBxi9Ky_q5Zd-o4dYpnmHyfX6cU94o0TSebfXayTVSpJVZhsLNiaEOYJD4tF5NyHmlhcHvBZpujDEdp7WEIct_OsB2vtYxvgex9BobCz0QD-I7CT9qU5M2_9NMDpfEnKNwsIMtWszByH | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:30:33 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fawscommunity-asean%252Fcountermeasure-against-cve-2021-44228-with-aws-waf-4n3d%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:33 |
https://www.iso.org/es/perspectivas/lista-filtrada-cambio-climatico | ISO - Cambio climático Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Cambio climático Cambio climático: qué es, cómo funciona y por qué es importante Hoy en día, las noticias están plagadas de recordatorios sobre cómo el cambio climático afecta la población de todo el mundo, desde incendios forestales e inundaciones hasta la pérdida de biodiversidad e incluso de vidas humanas. Pero ¿qué es exactamente el cambio climático? Últimos artículos Cambio climático: qué es, cómo funciona y por qué es importante Financiamiento climático: la clave para un futuro sostenible Desarrollo sostenible para un planeta cambiante Abrazar la naturaleza: soluciones al cambio climático para un futuro saludable El efecto invernadero: recuento de gases y por qué es importante Construir un camino sostenible hacia los informes ESG Las ventajas de implementar un sistema de gestión ambiental para su empresa Cargar más Suscríbase para recibir actualizaciones por correo electrónico ¡Regístrese para recibir recursos y actualizaciones sobre sostenibilidad y normas medioambientales! Website Suscribirse * ¡Ya casi está! Sólo le falta un paso para unirse a la lista de suscriptores de ISO. Confirme su suscripción haciendo clic en el correo electrónico que acabamos de enviarle. No estará registrado hasta que confirme su suscripción. Si no encuentra el correo electrónico, compruebe su carpeta de correo no deseado y/o la pestaña de promociones (si utiliza Gmail). * Boletín de noticias en inglés Para saber cómo se utilizarán sus datos, consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Cómo se utilizarán sus datos Consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Perspectivas y actualidad Perspectivas Cambio climático Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:33 |
https://pt-br.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0_eO-stakg9vLsOUo7Lt26VLQ_aYkr9Pf8ZZaLhPMiLcqEKHlcgGyJNGUNiyBkcQSC6SVtvR-ocoHfFkGBRUIIfK4kqcuSRuVlDS1_g0KFGeSi6wHVGd63HL5D3r9fcZfhU2T8Lb5znjek | Facebook Facebook Email ou telefone Senha Esqueceu a conta? Criar nova conta Você está bloqueado temporariamente Você está bloqueado temporariamente Parece que você estava usando este recurso de forma indevida. Bloqueamos temporariamente sua capacidade de usar o recurso. Back Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Français (France) Deutsch Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Configurações Registro de atividades Meta © 2026 | 2026-01-13T09:30:33 |
https://www.iso.org/es/perspectivas/opinion-de-expertos | ISO - Opinión de expertos Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Opinión de expertos Definir la buena gobernanza: un paso fundamental en el camino hacia el desarrollo sostenible En el momento actual, vivimos en un mundo lleno de peligro y potencial a partes iguales. La inteligencia artificial (IA) nos ha impulsado a una nueva era de la tecnología y ha dado lugar a preguntas acerca de qué será lo siguiente. Últimos artículos de opinión Opinion Colaboración por el clima: cómo los organismos normalizadores impulsan la gobernanza ambiental mundial Opinion Por qué la cooperación internacional en materia de IA es ahora más importante que nunca Opinion Cómo está haciendo ISO que la biodiversidad sea cuantificable Opinion El imperativo de la IA en África: ahora es el momento Opinion La crisis de la cocina de África sin acceso a la red eléctrica y las normas que pueden solventarla Opinion La biodiversidad es responsabilidad de todos Opinion Más valor, menos residuos: replantear el crecimiento en un mundo circular Cargar más Perspectivas y actualidad Actualidad Opinión de expertos Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:33 |
http://docs.buildbot.net/current/manual/configuration/properties.html | 2.5.12. Properties — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.5.1. Configuring Buildbot 2.5.2. Global Configuration 2.5.3. Change Sources and Changes 2.5.4. Changes 2.5.5. Schedulers 2.5.6. Workers 2.5.7. Builder Configuration 2.5.8. Projects 2.5.9. Codebases 2.5.10. Build Factories 2.5.11. Build Sets 2.5.12. Properties 2.5.12.1. Common Build Properties 2.5.12.2. Source Stamp Attributes 2.5.12.3. Using Properties in Steps 2.5.13. Build Steps 2.5.14. Interlocks 2.5.15. Report Generators 2.5.16. Reporters 2.5.17. Web Server 2.5.18. Change Hooks 2.5.19. Custom Services 2.5.20. DbConfig 2.5.21. Configurators 2.5.22. Manhole 2.5.23. Multimaster 2.5.24. Multiple-Codebase Builds 2.5.25. Miscellaneous Configuration 2.5.26. Testing Utilities 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.5. Configuration 2.5.12. Properties View page source 2.5.12. Properties Build properties are a generalized way to provide configuration information to build steps; see Build Properties for the conceptual overview of properties. Common Build Properties Source Stamp Attributes Using Properties in Steps Some build properties come from external sources and are set before the build begins; others are set during the build and are available for later steps. The sources for properties are: global configuration These properties apply to all builds. schedulers A scheduler can specify properties that become available to all builds it starts. changes A change can have properties attached to it, supplying extra information gathered by the change source. This is most commonly used with the sendchange command. forced builds The “Force Build” form allows users to specify properties workers A worker can pass properties on to the builds it performs. builds A build automatically sets a number of properties on itself. builders A builder can set properties on all the builds it runs. steps The steps of a build can set properties that are available to subsequent steps. In particular, source steps set the got_revision property. If the same property is supplied in multiple places, the final appearance takes precedence. For example, a property set in a builder configuration will override the one supplied by the scheduler. Properties are stored internally in JSON format, so they are limited to basic types of data: numbers, strings, lists, and dictionaries. 2.5.12.1. Common Build Properties The following build properties are set when the build is started, and are available to all steps. got_revision This property is set when a Source step checks out the source tree, and provides the revision that was actually obtained from the VC system. In general this should be the same as revision , except for non-absolute sourcestamps, where got_revision indicates what revision was current when the checkout was performed. This can be used to rebuild the same source code later. Note For some VC systems (Darcs in particular), the revision is a large string containing newlines, and is not suitable for interpolation into a filename. For multi-codebase builds (where codebase is not the default ‘’ ), this property is a dictionary, keyed by codebase. buildername This is a string that indicates which Builder the build was a part of. The combination of buildername and buildnumber uniquely identify a build. builderid This is a number that indicates which Builder the build was a part of. buildnumber Each build gets a number, scoped to the Builder (so the first build performed on any given Builder will have a build number of 0). This integer property contains the build’s number. workername This is a string which identifies which worker the build is running on. scheduler If the build was started from a scheduler, then this property will contain the name of that scheduler. builddir The absolute path of the base working directory on the worker of the current builder. For single codebase builds, where the codebase is ‘’ , the following Source Stamp Attributes are also available as properties: branch , revision , repository , and project . 2.5.12.2. Source Stamp Attributes branch revision repository project codebase For details of these attributes see Concepts . changes This attribute is a list of dictionaries representing the changes that make up this sourcestamp. 2.5.12.3. Using Properties in Steps For the most part, properties are used to alter the behavior of build steps during a build. This is done by using renderables (objects implementing the IRenderable interface) as step parameters. When the step is started, each such object is rendered using the current values of the build properties, and the resultant rendering is substituted as the actual value of the step parameter. Buildbot offers several renderable object types covering common cases. It’s also possible to create custom renderables . Note Properties are defined while a build is in progress; their values are not available when the configuration file is parsed. This can sometimes confuse newcomers to Buildbot! In particular, the following is a common error: if Property ( 'release_train' ) == 'alpha' : f . addStep ( ... ) This does not work because the value of the property is not available when the if statement is executed. However, Python will not detect this as an error - you will just never see the step added to the factory. You can use renderables in most step parameters. Please file bugs for any parameters which do not accept renderables. Property The simplest renderable is Property , which renders to the value of the property named by its argument: from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ 'echo' , 'buildername:' , util . Property ( 'buildername' )])) You can specify a default value by passing a default keyword argument: f . addStep ( steps . ShellCommand ( command = [ 'echo' , 'warnings:' , util . Property ( 'warnings' , default = 'none' )])) The default value is used when the property doesn’t exist, or when the value is something Python regards as False . The defaultWhenFalse argument can be set to False to force Buildbot to use the default argument only if the parameter is not set: f . addStep ( steps . ShellCommand ( command = [ 'echo' , 'warnings:' , util . Property ( 'warnings' , default = 'none' , defaultWhenFalse = False )])) The default value can be a renderable itself, e.g., command = util . Property ( 'command' , default = util . Property ( 'default-command' )) Interpolate Property can only be used to replace an entire argument: in the example above, it replaces an argument to echo . Often, properties need to be interpolated into strings, instead. The tool for that job is Interpolate . The more common pattern is to use Python dictionary-style string interpolation by using the %(prop:<propname>)s syntax. In this form, the property name goes in the parentheses, as above. A common mistake is to omit the trailing “s”, leading to a rather obscure error from Python (“ValueError: unsupported format character”). from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ 'make' , util . Interpolate ( 'REVISION=%(prop:got_revision)s' ), 'dist' ])) This example will result in a make command with an argument like REVISION=12098 . The syntax of dictionary-style interpolation is a selector, followed by a colon, followed by a selector specific key, optionally followed by a colon and a string indicating how to interpret the value produced by the key. The following selectors are supported. prop The key is the name of a property. src The key is a codebase and source stamp attribute, separated by a colon. Note, the syntax is %(src:<codebase>:<ssattr>)s , which differs from other selectors. kw The key refers to a keyword argument passed to Interpolate . Those keyword arguments may be ordinary values or renderables. secret The key refers to a secret provided by a provider declared in secretsProviders . worker The key refers to an info item provided by workers . The following ways of interpreting the value are available. -replacement If the key exists, substitute its value; otherwise, substitute replacement . replacement may be empty (default), %(prop:propname:-)s . ~replacement Like -replacement , but only substitutes the value of the key if it is something Python regards as True . Python considers None , 0, empty lists, and the empty string to be false, so such values will be replaced by replacement . +replacement If the key exists, substitute replacement ; otherwise, substitute an empty string. ?|sub_if_exists|sub_if_missing #?|sub_if_true|sub_if_false Ternary substitution, depending on either the key being present (with ? , similar to + ) or being True (with #? , like ~ ). Notice that there is a pipe immediately following the question mark and between the two substitution alternatives. The character that follows the question mark is used as the delimiter between the two alternatives. In the above examples, it is a pipe, but any character other than ( can be used. Note Although these are similar to shell substitutions, no other substitutions are currently supported. Example: from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ 'save-build-artifacts-script.sh' , util . Interpolate ( '-r %(prop:repository)s' ), util . Interpolate ( '-b %(src::branch)s' ), util . Interpolate ( '-d %(kw:data)s' , data = "some extra needed data" ) ])) Note We use %(src::branch)s in most examples, because codebase is empty by default. Example: from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ 'make' , util . Interpolate ( 'REVISION=%(prop:got_revision:-%(src::revision:-unknown)s)s' ), 'dist' ])) In addition, Interpolate supports using positional string interpolation. Here, %s is used as a placeholder, and the substitutions (which may be renderables) are given as subsequent arguments: f . addStep ( steps . ShellCommand ( command = [ 'echo' , util . Interpolate ( ' %d warnings and %d errors' , util . Property ( 'warnings' ), util . Property ( 'errors' )) ])) Note Like Python, you can use either positional interpolation or dictionary-style interpolation, but not both. Thus you cannot use a string like Interpolate("foo-%(src::revision)s-%s", "branch") . Renderer While Interpolate can handle many simple cases, and even some common conditionals, more complex cases are best handled with Python code. The renderer decorator creates a renderable object whose rendering is obtained by calling the decorated function when the step to which it’s passed begins. The function receives an IProperties object, which it can use to examine the values of any and all properties. For example: from buildbot.plugins import steps , util @util . renderer def makeCommand ( props ): command = [ 'make' ] cpus = props . getProperty ( 'CPUs' ) if cpus : command . extend ([ '-j' , str ( cpus + 1 )]) else : command . extend ([ '-j' , '2' ]) command . extend ([ util . Interpolate ( '%(prop:MAKETARGET)s' )]) return command f . addStep ( steps . ShellCommand ( command = makeCommand )) You can think of renderer as saying “call this function when the step starts”. Note Since 0.9.3, renderer can itself return IRenderable objects or containers containing IRenderable . Optionally, extra arguments may be passed to the rendered function at any time by calling withArgs on the renderable object. The withArgs method accepts *args and **kwargs arguments which are stored in a new renderable object which is returned. The original renderable object is not modified. Multiple withArgs calls may be chained. The passed *args and **kwargs parameters are rendered and the results are passed to the rendered function at the time it is itself rendered. For example: from buildbot.plugins import steps , util @util . renderer def makeCommand ( props , target ): command = [ 'make' ] cpus = props . getProperty ( 'CPUs' ) if cpus : command . extend ([ '-j' , str ( cpus + 1 )]) else : command . extend ([ '-j' , '2' ]) command . extend ([ target ]) return command f . addStep ( steps . ShellCommand ( command = makeCommand . withArgs ( 'mytarget' ))) Note The rendering of the renderable object may happen at unexpected times, so it is best to ensure that the passed extra arguments are not changed. Note Config errors with Renderables may not always be caught via checkconfig. Transform Transform is an alternative to renderer . While renderer is useful for creating new renderables, Transform is easier to use when you want to transform or combine the renderings of preexisting renderables. Transform takes a function and any number of positional and keyword arguments. The function must either be a callable object or a renderable producing one. When rendered, a Transform first replaces all of its arguments that are renderables with their renderings, then calls the function, passing it the positional and keyword arguments, and returns the result as its own rendering. For example, suppose my_path is a path on the worker, and you want to get it relative to the build directory. You can do it like this: import os.path from buildbot.plugins import util my_path_rel = util . Transform ( os . path . relpath , my_path , start = util . Property ( 'builddir' )) This works whether my_path is an ordinary string or a renderable. my_path_rel will be a renderable in either case, however. FlattenList If a nested list should be flattened for some renderables, FlattenList can be used. For example: from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ 'make' ], descriptionDone = util . FlattenList ([ 'make ' , [ 'done' ]]) )) descriptionDone will be set to [ 'make', 'done' ] when the ShellCommand executes. This is useful when a list-returning property is used in renderables. Note ShellCommand automatically flattens nested lists in its command argument, so there is no need to use FlattenList for it. WithProperties Warning This class is deprecated. It is an older version of Interpolate . It exists for compatibility with older configs. The simplest use of this class is with positional string interpolation. Here, %s is used as a placeholder, and property names are given as subsequent arguments: from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ "tar" , "czf" , util . WithProperties ( "build- %s - %s .tar.gz" , "branch" , "revision" ), "source" ])) If this BuildStep were used in a tree obtained from Git, it would create a tarball with a name like build-master-a7d3a333db708e786edb34b6af646edd8d4d3ad9.tar.gz . The more common pattern is to use Python dictionary-style string interpolation by using the %(propname)s syntax. In this form, the property name goes in the parentheses, as above. A common mistake is to omit the trailing “s”, leading to a rather obscure error from Python (“ValueError: unsupported format character”). from buildbot.plugins import steps , util f . addStep ( steps . ShellCommand ( command = [ 'make' , util . WithProperties ( 'REVISION= %(got_revision)s ' ), 'dist' ])) This example will result in a make command with an argument like REVISION=12098 . The dictionary-style interpolation supports a number of more advanced syntaxes in the parentheses. propname:-replacement If propname exists, substitute its value; otherwise, substitute replacement . replacement may be empty ( %(propname:-)s ) propname:~replacement Like propname:-replacement , but only substitutes the value of property propname if it is something Python regards as True . Python considers None , 0, empty lists, and the empty string to be false, so such values will be replaced by replacement . propname:+replacement If propname exists, substitute replacement ; otherwise, substitute an empty string. Although these are similar to shell substitutions, no other substitutions are currently supported, and replacement in the above cannot contain more substitutions. Note: like Python, you can use either positional interpolation or dictionary-style interpolation, not both. Thus you cannot use a string like WithProperties("foo-%(revision)s-%s", "branch") . Custom Renderables If the options described above are not sufficient, more complex substitutions can be achieved by writing custom renderables. The IRenderable interface is simple - objects must provide a getRenderingFor method. The method should take one argument - an IProperties provider - and should return the rendered value or a deferred firing with one. You can pass instances of the class anywhere other renderables are accepted. For example: import time from buildbot.interfaces import IRenderable from zope.interface import implementer @implementer ( IRenderable ) class DetermineFoo ( object ): def getRenderingFor ( self , props ): if props . hasProperty ( 'bar' ): return props [ 'bar' ] elif props . hasProperty ( 'baz' ): return props [ 'baz' ] return 'qux' ShellCommand ( command = [ 'echo' , DetermineFoo ()]) or, more practically, from buildbot.interfaces import IRenderable from zope.interface import implementer from buildbot.plugins import util @implementer ( IRenderable ) class Now ( object ): def getRenderingFor ( self , props ): return time . clock () ShellCommand ( command = [ 'make' , util . Interpolate ( 'TIME=%(kw:now)s' , now = Now ())]) This is equivalent to: from buildbot.plugins import util @util . renderer def now ( props ): return time . clock () ShellCommand ( command = [ 'make' , util . Interpolate ( 'TIME=%(kw:now)s' , now = now )]) Note that a custom renderable must be instantiated (and its constructor can take whatever arguments you like), whereas a function decorated with renderer can be used directly. URL for build Its common to need to use the URL for the build in a step. For this, you can use a special custom renderer as following: from buildbot.plugins import * ShellCommand ( command = [ 'make' , util . Interpolate ( 'BUILDURL=%(kw:url)s' , url = util . URLForBuild )]) Renderable Comparison Its common to need to make basic comparison or calculation with properties. The Property and Interpolate objects contain necessary operator overloads to make this possible. from buildbot.plugins import * ShellCommand ( command = [ 'make' ], doStepIf = Interpolate ( "worker:os_id" ) == 'ubuntu' ) In previous code, the value of the comparison can only be computed at runtime, so the result of the comparison is actually a renderable which will be computed at the start of the step. from buildbot.plugins import * ShellCommand ( command = [ 'make' ], doStepIf = Interpolate ( "worker:os_id" ) . in_ ([ 'debian' , 'ubuntu' ])) ‘in’ operator cannot be overloaded, so we add a simple in_ method to Property and Interpolate . Currently supported operators are in_ , == , != , < , <= , > , >= , + , - , * , / , // , % . Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:33 |
https://www.iso.org/es/normas/mas-comunes | ISO - Normas más comunes Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Normas Normas más comunes Discover our most widely used ISO standards – from quality and information security to environmental and occupational health. These are the standards trusted worldwide to improve performance, reduce risk and support innovation. Reference number ISO 9001:2015 © ISO 2026 International Standard ISO 9001:2015 Quality management systems — Requirements Edition 5 2015-09 ISO 9001:2015 Sistemas de gestión de calidad — Requisitos Reference number ISO/IEC 27001:2022 © ISO 2026 International Standard ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection — Information security management systems — Requirements Edition 3 2022-10 ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection — Information security management systems — Requirements Reference number ISO/IEC 42001:2023 © ISO 2026 International Standard ISO/IEC 42001:2023 Information technology — Artificial intelligence — Management system Edition 1 2023-12 ISO/IEC 42001:2023 Information technology — Artificial intelligence — Management system Other popular ISO standards Reference number ISO 45001:2018 © ISO 2026 International Standard ISO 45001:2018 Occupational health and safety management systems — Requirements with guidance for use Edition 1 2018-03 ISO 45001:2018 Sistemas de gestión de la seguridad y salud en el trabajo — Requisitos con orientación para su uso Reference number ISO 13485:2016 © ISO 2026 International Standard ISO 13485:2016 Medical devices — Quality management systems — Requirements for regulatory purposes Edition 3 2016-03 ISO 13485:2016 Medical devices — Quality management systems — Requirements for regulatory purposes Reference number ISO 14001:2015 © ISO 2026 International Standard ISO 14001:2015 Environmental management systems — Requirements with guidance for use Edition 3 2015-09 ISO 14001:2015 Sistemas de gestión ambiental — Requisitos con orientación para su uso Reference number ISO 35001:2019 © ISO 2026 International Standard ISO 35001:2019 Biorisk management for laboratories and other related organisations Edition 1 2019-11 ISO 35001:2019 Biorisk management for laboratories and other related organisations Reference number ISO 26000:2010 © ISO 2026 International Standard ISO 26000:2010 Guidance on social responsibility Edition 1 2010-11 ISO 26000:2010 Guidance on social responsibility International Standard ISO 37001:2025 Anti-bribery management systems — Requirements with guidance for use Reference number ISO 37001:2025 Edition 2 2025-02 © ISO 2026 ISO 37001:2025 Sistemas de gestión antisoborno — Requisitos con orientación para su uso Reference number ISO 50001:2018 © ISO 2026 International Standard ISO 50001:2018 Energy management systems — Requirements with guidance for use Edition 2 2018-08 ISO 50001:2018 Sistemas de gestión de la energía — Requisitos con orientación para su uso International Standard ISO 20121:2024 Event sustainability management systems — Requirements with guidance for use Reference number ISO 20121:2024 Edition 2 2024-04 © ISO 2026 ISO 20121:2024 Event sustainability management systems — Requirements with guidance for use Reference number ISO/IEC 17025:2017 © ISO 2026 International Standard ISO/IEC 17025:2017 General requirements for the competence of testing and calibration laboratories Edition 3 2017-11 ISO/IEC 17025:2017 General requirements for the competence of testing and calibration laboratories Reference number ISO 22000:2018 © ISO 2026 International Standard ISO 22000:2018 Food safety management systems — Requirements for any organization in the food chain Edition 2 2018-06 ISO 22000:2018 Food safety management systems — Requirements for any organization in the food chain Codes and references ISO 639 — Language code Describe languages in an internationally accepted way with this standard. ISO 4217 — Currency codes Avoid confusion when referring to world currencies with this standard. ISO 8601 — Date and time format ISO 8601 is the internationally accepted way to represent dates and times. ISO 3166 — Country Codes Avoid confusion when referring to countries and their subdivisions with this standard. Normas Normas más comunes Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:33 |
https://support.microsoft.com/et-ee/account-billing/enne-xboxi-v%C3%B5i-windowsi-arvuti-m%C3%BC%C3%BCmist-kinkimist-v%C3%B5i-taaskasutusse-andmist-78ee8071-c8ab-40c4-1d89-f708582062e4 | Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist - Microsofti tugiteenus Seotud teemad × Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Põhisisu juurde Microsoft Tugi Tugi Tugi Avaleht Microsoft 365 Office Tooted Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows rohkem… Seadmed Surface Arvuti tarvikud Xbox Arvutimängud HoloLens Surface Hub Riistvara garantiid Konto ja arveldamine konto Microsoft Store ja arveldamine Ressursid Mis on uut? Kogukonnafoorumid Microsoft 365 administraatorid Väikeettevõtete portaal Arendaja Haridus Teatage tehnilise toega seotud pettusest Tooteohutus Rohkem Osta Microsoft 365 Kogu Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Tugi Tarkvara Tarkvara Windowsi rakendused AI OneDrive Outlook Üleminek Skype'ilt Teamsile OneNote Microsoft Teams Arvutid ja seadmed Arvutid ja seadmed Accessories Meelelahutus Meelelahutus PC-mängud Äri Äri Microsofti turve Azure Dynamics 365 Microsoft 365 ettevõtteversioon Microsoft Industry Microsoft Power Platform Windows 365 Arendaja ja IT Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Visual Studio Marketplace Rewards Muud Muud Tasuta allalaadimised ja turve Kuva saidikaart Otsing Spikri otsing Tulemid puuduvad Loobu Logi sisse Logige sisse Microsofti kontoga Logige sisse või looge konto. Tere! Valige mõni muu konto. Teil on mitu kontot Valige konto, millega soovite sisse logida. Seotud teemad Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Rakenduskoht Microsoft account Windows 11 Windows 10 Microsofti konto andmelaud Kui plaanite Oma Windows-seadme või Xbox One’i konsool ringlusse võtta, müüa või kinkida, siis veenduge, et oleksite sellelt eemaldanud kõik isikuandmed. Windowsi seadme lähtestamine Varundage Windowsi varundus abil kogu teave, mida soovite salvestada. Pärast vajaliku teabe varundamist avage taastesätted. Valige Oma Windows-seadme rakenduses Sätted suvand Süsteem > Taaste või kasutage järgmist otseteed: Taastesätete avamine Märkus.: Windows 10 kaudu pääsete sellele juurde teenuse Update & Security > Recovery kaudu. Tehke jaotises Lähtesta see arvuti valik Alusta ja järgige siis ekraanile kuvatavaid juhiseid. Valige Arvuti lähtestamine. Valige lähtestamissuvandite tabeli suvandite hulgast ja/või sätete hulgast sobiv. Xboxi lähtestamine Sätete varundamine Konsooli lähtestamine Xboxis tehase vaikesätetele Seadme eemaldamine Microsofti kontolt Pärast seadme varundamist ja lähtestamist peaksite selle Microsoft kontolt eemaldama. Juhised Avage https://account.microsoft.com/devices , logige sisse ja otsige üles seade, mille soovite eemaldada. Teabe saamiseks selle seadme kohta valige Kuva üksikasjad . Seadme nime alt valige Rohkem toiminguid > Eemalda . Vaadake üle oma seadme üksikasjad, märkige ruut Olen valmis selle seadme eemaldama ja seejärel valige Eemalda . Seejärel saate seadme linkimise Microsofti kontoga tühistada, et see ei mõjutaks teie Microsoft Store'i seadmelimiiti. Logige sisse oma Microsofti kontoga aadressil https://account.microsoft.com/devices . Otsige üles seade, mille soovite eemaldada, ja valige Tühista linkimine . Vaadake üle seadme üksikasjad ja valige Tühista linkimine . Seotud teemad Kui saite seadme, mida pole lähtestatud, saate teha puhta installi . Kui olete kaotanud oma BitLockeri võtme, lugege artiklit BitLockeri taastevõtme otsimine . Seadme ümbernimetamise kohta leiate teavet artiklist Seadmete haldamine Microsoft Store’i jaoks . Kui teie seade on kadunud või varastatud, saate selle asukoha kindlaks teha ja kauglukustada. Selleks lugege artiklit Kaotsiläinud Windows-seadme leidmine ja lukustamine . Varastatud Xboxi kohta leiate teavet artiklist Mida teha, kui teie Xbox varastatakse . Kui muretsete oma Microsofti konto turvalisuse pärast, lugege artiklit Microsofti konto kaitsmine ja suurema turvalisuse tagamine . Kõigi teie Microsofti kontole registreeritud seadmete vaatamiseks ja haldamiseks lugege jaotist Microsofti kontoga kasutatavate seadmete haldamine. Lisateavet Windowsi arvuti taastamise meetodite kohta leiate artiklist Windowsi taastesuvandid. Kas vajate rohkem abi? Tootetoe poole pöördumine Tehnilise toe saamiseks avage Microsofti tugiteenuste poole pöördumine , sisestage oma probleem ja valige Kasutajaabi . Kui vajate endiselt abi, valige juhiste saamiseks ja parima suvandini jõudmiseks Võtke ühendust kasutajatoega . TELLIGE RSS-KANALID Kas vajate veel abi? Kas soovite rohkem valikuvariante? Tutvustus Kogukonnafoorum Kontaktteave Siin saate tutvuda tellimusega kaasnevate eelistega, sirvida koolituskursusi, õppida seadet kaitsma ja teha veel palju muud. Microsoft 365 tellimuse eelised Microsoft 365 koolitus Microsofti turbeteenus Hõlbustuskeskus Kogukonnad aitavad teil küsimusi esitada ja neile vastuseid saada, anda tagasisidet ja saada nõu rikkalike teadmistega asjatundjatelt. Nõu küsimine Microsofti kogukonnafoorumis Microsofti spetsialistide kogukonnafoorum Windows Insideri programmis osalejad Microsoft 365 Insideri programmis osalejad Leidke lahendused levinud probleemidele või võtke ühendust klienditeenindajaga. Võrgutugi Kas sellest teabest oli abi? Jah Ei Aitäh! Veel tagasisidet Microsoftile? Kas saaksite aidata meil teenust paremaks muuta? (Saatke Microsoftile tagasisidet, et saaksime aidata.) Kui rahul te keelekvaliteediga olete? Mis mõjutas teie hinnangut? Leidsin oma probleemile lahenduse Juhised olid selged Tekstist oli lihtne aru saada Tekstis pole žargooni Piltidest oli abi Tõlkekvaliteet Tekst ei vastanud minu ekraanipildile Valed juhised Liiga tehniline Pole piisavalt teavet Pole piisavalt pilte Tõlkekvaliteet Kas soovite anda veel tagasisidet? (Valikuline) Saada tagasiside Kui klõpsate nuppu Edasta, kasutatakse teie tagasisidet Microsofti toodete ja teenuste täiustamiseks. IT-administraator saab neid andmeid koguda. Privaatsusavaldus. Täname tagasiside eest! × Mis on uut? Copilot organisatsioonidele Copilot isiklikuks kasutuseks Microsoft 365 Windows 11 rakendused Microsoft Store Konto profiil Allalaadimiskeskus Tagastused Tellimuse jälgimine Ringlussevõtt Commercial Warranties Haridus Microsoft Education Haridusseadmed Microsoft Teams haridusasutustele Microsoft 365 Education Office Education Haridustöötajate koolitus ja arendus Pakkumised õpilastele ja vanematele Azure õpilastele Äri Microsofti turve Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamsi jaoks Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Ettevõte Töökohad Teave Microsofti kohta Privaatsus Microsoftis Investorid Jätkusuutlikkus Eesti (Eesti) Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Tarbijaseisundi privaatsus Võtke Microsoftiga ühendust Privaatsus Halda küpsiseid Kasutustingimused Kaubamärgid Reklaamide kohta EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:33 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-generating-http-responses.html | Arbeiten mit Anforderungen und Antworten - Amazon CloudFront Arbeiten mit Anforderungen und Antworten - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch Verwenden von Funktionen mit Origin Failover Generieren von HTTP-Antworten in Anforderungsauslösern Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern Zugriff auf den Anforderungstext über die Option „Text einschließen“ Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich. Arbeiten mit Anforderungen und Antworten Informationen zur Verwendung von Lambda@Edge-Anforderungen und -Antworten finden Sie in den folgenden Themen: Themen Verwenden von Lambda@Edge-Funktionen mit Origin Failover Generieren von HTTP-Antworten in Anforderungsauslösern Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern Zugriff auf den Anforderungstext über die Option „Text einschließen“ Verwenden von Lambda@Edge-Funktionen mit Origin Failover Sie können Lambda @Edge -Funktionen mit CloudFront Verteilungen verwenden, die Sie mit Ursprungsgruppen eingerichtet haben, z. B. für Origin-Failover, das Sie konfigurieren, um eine hohe Verfügbarkeit sicherzustellen. Um eine Lambda-Funktion mit einer Ursprungsgruppe zu verwenden, geben Sie die Funktion in einem Ursprungsanfragen- oder Ursprungsantwort-Auslöser für eine Ursprungsgruppe an, wenn Sie das Zwischenspeicher-Verhalten erstellen. Weitere Informationen finden Sie hier: Erstellen von Ursprungsgruppen: Erstellen einer Ursprungsgruppe Funktionsweise von Origin Failover mit Lambda@Edge: Verwenden von Origin Failover mit Lambda@Edge-Funktionen Generieren von HTTP-Antworten in Anforderungsauslösern Wenn Sie CloudFront eine Anfrage erhalten, können Sie eine Lambda-Funktion verwenden, um eine HTTP-Antwort zu generieren, die direkt an den Betrachter CloudFront zurückkehrt, ohne die Antwort an den Ursprung weiterzuleiten. Die Generierung von HTTP-Antworten reduziert die Auslastung des Ursprungs und reduziert in der Regel auch die Latenzzeit für den Viewer. Einige häufige Szenarien für die Generierung von HTTP-Antworten sind die folgenden: Rückgabe einer kleinen Website an den Viewer. Rückgabe eines HTTP 301- oder 302-Statuscodes, um den Benutzer auf eine andere Webseite umzuleiten. Rückgabe eines HTTP 401-Statuscodes an den Viewer, wenn sich der Benutzer nicht authentifiziert hat. Eine Lambda@Edge-Funktion kann eine HTTP-Antwort generieren, wenn die folgenden CloudFront-Ereignisse auftreten: Viewer-Anforderungsereignisse Wenn eine Funktion durch ein Viewer-Anforderungsereignis ausgelöst wird, CloudFront gibt sie die Antwort an den Betrachter zurück und speichert sie nicht im Cache. Ursprungsanforderungsereignisse Wenn eine Funktion durch ein Origin-Anforderungsereignis ausgelöst wird, CloudFront wird im Edge-Cache nach einer Antwort gesucht, die zuvor von der Funktion generiert wurde. Wenn sich die Antwort im Cache befindet, wird die Funktion nicht ausgeführt und CloudFront gibt die zwischengespeicherte Antwort an den Viewer zurück. Wenn sich die Antwort nicht im Cache befindet, wird die Funktion ausgeführt, CloudFront gibt die Antwort an den Betrachter zurück und speichert sie ebenfalls im Cache. Beispiel-Code zum Generieren von HTTP-Antworten finden Sie unter Beispielfunktionen für Lambda@Edge . Sie können auch die HTTP-Antworten in Antwortauslösern ersetzen. Weitere Informationen finden Sie unter Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern . Programmiermodell Dieser Abschnitt enthält Informationen über das Programmiermodell für die Nutzung von Lambda@Edge zum Generieren von HTTP-Antworten. Themen Antwortobjekt Fehler Pflichtfelder Antwortobjekt Die Antwort, die Sie als result -Parameter der callback -Methode zurückgeben, sollte folgenden Aufbau haben (beachten Sie, dass nur das status -Feld erforderlich ist). const response = { body: 'content', bodyEncoding: 'text' | 'base64', headers: { 'header name in lowercase': [ { key: 'header name in standard case', value: 'header value' }], ... }, status: 'HTTP status code (string)', statusDescription: 'status description' }; Das Antwortobjekt kann die folgenden Werte enthalten: body Der Text, falls vorhanden, den Sie in der generierten Antwort zurückgeben CloudFront möchten. bodyEncoding Die Kodierung für den Wert, den Sie in body festgelegt haben. Die einzigen gültigen Codierungen sind text und base64 . Wenn Sie body in das response Objekt aufnehmen, aber weglassen bodyEncoding , wird der CloudFront Hauptteil als Text behandelt. Wenn Sie bodyEncoding als base64 festlegen, der Body jedoch kein gültiges base64 ist, gibt CloudFront einen Fehler zurück. headers Header, die Sie in der generierten Antwort zurückgeben möchten CloudFront . Beachten Sie Folgendes: Die Schlüssel im headers -Objekt sind kleingeschriebene Versionen von Standard-HTTP-Header-Namen. Über diese Kleinbuchstaben-Schlüssel haben Sie Zugriff auf die Headerwerte (ohne Berücksichtigung von Groß-/Kleinschreibung). Jeder Header (z. B. headers["accept"] oder headers["host"] ) ist ein Array mit Schlüssel-Wert-Paaren. Für einen bestimmten Header enthält das Array ein Schlüssel-Wert-Paar für jeden Wert in der generierten Antwort. key (optional) ist der von Groß- und Kleinschreibung unabhängige Name des Headers, wie er in einer HTTP-Anforderung erscheint (z. B. accept oder host ). Geben Sie value als Header-Wert an. Wenn Sie den Header-Schlüsselteil des Schlüssel-Wert-Paares nicht aufnehmen, fügt Lambda@Edge automatisch einen Header-Schlüssel mit dem von Ihnen angegebenen Header-Namen ein. Unabhängig davon, wie Sie den Header-Namen formatiert haben, wird der automatisch eingefügte Header-Schlüssel mit einem großen Anfangsbuchstaben für jeden Teil formatiert, wobei die einzelnen Teile durch Bindestriche (-) getrennt werden. Beispielsweise können Sie einen Header wie den folgenden ohne Header-Schlüssel hinzufügen: 'content-type': [ { value: 'text/html;charset=UTF-8' }] In diesem Beispiel erstellt Lambda@Edge den folgenden Header-Schlüssel: Content-Type . Weitere Informationen zu Einschränkungen zur Verwendung von Headern finden Sie unter Einschränkungen für Edge-Funktionen . status Den HTTP-Statuscode . Geben Sie den Statuscode als Zeichenfolge an. CloudFront verwendet den bereitgestellten Statuscode für Folgendes: Rückgabe in der Antwort Cache im CloudFront Edge-Cache, wenn die Antwort durch eine Funktion generiert wurde, die durch ein Origin-Request-Ereignis ausgelöst wurde Loggen Sie sich ein CloudFront Zugriffsprotokolle (Standardprotokolle) Wenn der status -Wert nicht zwischen 200 und 599 liegt, gibt CloudFront einen Fehler an den Betrachter zurück. statusDescription Die Beschreibung, die CloudFront Sie zusammen mit dem HTTP-Statuscode in der Antwort zurückgeben möchten. Sie müssen keine Standardbeschreibungen verwenden (z. B. OK für einen HTTP-Statuscode 200). Fehler Es folgen mögliche Fehler für generierte HTTP-Antworten. Antwort enthält einen Body und legt 204 (No Content) als Status fest Wenn eine Funktion durch eine Viewer-Anfrage ausgelöst wird, CloudFront gibt sie dem Viewer einen HTTP 502-Statuscode (Bad Gateway) zurück, wenn beide der folgenden Bedingungen zutreffen: Der Wert von status ist 204 (No Content) Die Antwort enthält einen Wert für body Der Grund hierfür ist, dass Lambda@Edge eine optionale Einschränkung aus RFC 2616 umsetzt, die besagt, dass eine HTTP 204 -Antwort keinen Nachrichtentext zu enthalten braucht. Beschränkungen für die Größe der generierten Antwort Die maximale Größe einer durch eine Lambda-Funktion generierten Antwort hängt von dem Ereignis ab, das die Funktion ausgelöst hat: Viewer-Anfrage-Ereignisse – 40 KB Ursprungsanfrageereignisse – 1 MB Wenn die Antwort größer als die zulässige Größe ist, wird ein HTTP 502-Statuscode (Bad Gateway) an den Betrachter CloudFront zurückgegeben. Pflichtfelder Das Feld status ist ein Pflichtfeld. Alle anderen Felder sind optional. Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern Wenn eine HTTP-Antwort vom Ursprungsserver CloudFront empfangen wird und ein Origin-Response-Trigger mit dem Cache-Verhalten verknüpft ist, können Sie die HTTP-Antwort so ändern, dass sie überschreibt, was vom Ursprung zurückgegeben wurde. Einige häufige Szenarien für die Aktualisierung von HTTP-Antworten sind die folgenden: Ändern des Status, um einen HTTP 200-Statuscode festzulegen, und Erstellen statischer Body-Inhalte für die Rückgabe an den Viewer, wenn ein Ursprung einen Fehlerstatuscode (4xx oder 5xx) zurückgibt. Einen Beispiel-Code finden Sie unter Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 200 aktualisieren . Ändern des Status, um einen HTTP 301- oder HTTP 302-Statuscode festzulegen, um den Benutzer auf eine andere Website umzuleiten, wenn ein Ursprung einen Fehlerstatuscode zurückgibt (4xx oder 5xx). Einen Beispiel-Code finden Sie unter Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 302 aktualisieren . Anmerkung Die Funktion muss einen Statuswert zwischen 200 und 599 (einschließlich) zurückgeben, andernfalls CloudFront gibt sie einen Fehler an den Viewer zurück. Sie können auch die HTTP-Antworten in Viewer- und Ursprungsanfrageereignissen ersetzen. Weitere Informationen finden Sie unter Generieren von HTTP-Antworten in Anforderungsauslösern . Wenn Sie mit der HTTP-Antwort arbeiten, stellt Lambda@Edge den Textkörper, der vom Ursprungsserver zurückgegeben wird, nicht für den Ursprungsantwortauslöser bereit. Sie können einen statischen Inhaltstext erzeugen, indem Sie ihn auf den gewünschten Wert setzen, oder den Text innerhalb der Funktion entfernen, indem Sie den Wert auf leer setzen. Wenn Sie das Textkörperfeld in Ihrer Funktion nicht aktualisieren, wird der ursprüngliche Textkörper, der vom Ursprungsserver zurückgegeben wird, an den Viewer zurückgegeben. Zugriff auf den Anforderungstext über die Option „Text einschließen“ Sie können jetzt auswählen, ob Lambda@Edge den Textkörper in einer Anforderung für eine nicht schreibgeschützte HTTP-Methode (POST, PUT, DELETE etc.) weitergeben soll, sodass Sie in Ihrer Lambda-Funktion darauf zugreifen können. Sie können den Lesezugriff wählen oder angeben, dass Sie den Textkörper ersetzen möchten. Um diese Option zu aktivieren, wählen Sie Include Body (Body einbeziehen) aus, wenn Sie einen CloudFront -Auslöser für Ihre für ein Betrachteranforderungs- oder Ursprungsanforderungsereignis vorgesehene Funktion erstellen. Weitere Informationen finden Sie unter Hinzufügen von Auslösern für eine Lambda@Edge-Funktion . Mehr zur Nutzung von Include Body (Textkörper einbeziehen) mit Ihrer Funktion finden Sie unter Lambda@Edge-Ereignisstruktur . Sie können dieses Feature in den folgenden Szenarien nutzen: Verarbeitung von Webformularen (z. B. "Kontakt"-Formulare) ohne Rückgabe von Kundeneingabedaten an den Ursprungs-Server Erfassen von Web-Beacon-Daten, die von Viewer-Browsern gesendet werden, und Verarbeiten am Edge Einen Beispiel-Code finden Sie unter Beispielfunktionen für Lambda@Edge . Anmerkung Wenn der Anforderungs-Body groß ist, wird er von Lambda@Edge abgeschnitten. Ausführliche Informationen zur maximalen Größe und Kürzung finden Sie unter Einschränkungen für Anforderungstext mit der Option „Text einschließen“ . JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert. Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers. Dokumentkonventionen Ereignisstruktur Beispielfunktionen Hat Ihnen diese Seite geholfen? – Ja Vielen Dank, dass Sie uns mitgeteilt haben, dass wir gute Arbeit geleistet haben! Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, was wir richtig gemacht haben, damit wir noch besser werden? Hat Ihnen diese Seite geholfen? – Nein Vielen Dank, dass Sie uns mitgeteilt haben, dass diese Seite überarbeitet werden muss. Es tut uns Leid, dass wir Ihnen nicht weiterhelfen konnten. Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, wie wir die Dokumentation verbessern können? | 2026-01-13T09:30:33 |
https://support.microsoft.com/ja-jp/windows/microsoft-edge-%E3%81%A7-cookie-%E3%82%92%E7%AE%A1%E7%90%86%E3%81%99%E3%82%8B-%E8%A1%A8%E7%A4%BA-%E8%A8%B1%E5%8F%AF-%E3%83%96%E3%83%AD%E3%83%83%E3%82%AF-%E5%89%8A%E9%99%A4-%E4%BD%BF%E7%94%A8-168dab11-0753-043d-7c16-ede5947fc64d | Microsoft Edge で Cookie を管理する: 表示、許可、ブロック、削除、使用 - Microsoft サポート 関連トピック × Windows のセキュリティ、安全性、プライバシー 概要 セキュリティ、安全性、プライバシーの概要 Windows のセキュリティ Windows のセキュリティに関するヘルプ Windows セキュリティで安全性を維持する Xbox または Windows PC をリサイクル、売却、または譲渡する前に Windows PC からマルウェアを削除する Windows の安全性 Windows の安全性に関するヘルプ Microsoft Edge の閲覧履歴を表示および削除する Cookie の削除と管理を行う Windows を再インストールするときに貴重なコンテンツを安全に削除する 紛失した Windows デバイスを探し、ロックする Windows のプライバシー Windows のプライバシーに関するヘルプ アプリが使用する Windows のプライバシー設定 プライバシー ダッシュボードでデータを表示する メイン コンテンツへスキップ Microsoft サポート サポート サポート ホーム Microsoft 365 Office 製品 Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows さらに表示... デバイス Surface PC アクセサリ Xbox PC ゲーム HoloLens Surface Hub ハードウェアの保証 アカウントと請求 アカウント Microsoft Store と請求 リソース 新機能 コミュニティ フォーラム Microsoft 365 管理者 中小企業のポータル 開発者 教育 サポート詐欺を報告する 製品の安全性 表示数を増やす Microsoft 365 を購入 すべての Microsoft 製品 Global Microsoft 365 Teams Copilot Windows Surface Xbox セール 法人向け サポート ソフトウェア ソフトウェア Windows アプリ AI OneDrive Outlook Skype から Teams への移行 OneNote Microsoft Teams PC とデバイス PC とデバイス Xbox を購入する アクセサリ エンタメ エンタメ Xbox Game Pass Ultimate Xbox とゲーム PC ゲーム 法人向け 法人向け Microsoft Security Azure Dynamics 365 一般法人向け Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 開発者 & IT 開発者 & IT Microsoft 開発者 Microsoft Learn AI マーケットプレース アプリのサポート Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards その他 その他 Microsoft Rewards 無料ダウンロード & セキュリティ 教育 プリペイド カード ライセンス サイトマップの表示 検索 ヘルプを検索する 一致するものがありません キャンセル サインイン Microsoft アカウントでサインイン サインインまたはアカウントを作成してください。 こんにちは、 別のアカウントを選択してください。 複数のアカウントがあります サインインに使用するアカウントを選択してください。 関連トピック Windows のセキュリティ、安全性、プライバシー 概要 セキュリティ、安全性、プライバシーの概要 Windows のセキュリティ Windows のセキュリティに関するヘルプ Windows セキュリティで安全性を維持する Xbox または Windows PC をリサイクル、売却、または譲渡する前に Windows PC からマルウェアを削除する Windows の安全性 Windows の安全性に関するヘルプ Microsoft Edge の閲覧履歴を表示および削除する Cookie の削除と管理を行う Windows を再インストールするときに貴重なコンテンツを安全に削除する 紛失した Windows デバイスを探し、ロックする Windows のプライバシー Windows のプライバシーに関するヘルプ アプリが使用する Windows のプライバシー設定 プライバシー ダッシュボードでデータを表示する Microsoft Edge で Cookie を管理する: 表示、許可、ブロック、削除、使用 適用先 Windows 10 Windows 11 Microsoft Edge Cookie は、アクセスした Web サイトによってデバイスに保存される小さなデータです。 ログイン資格情報の記憶、サイトの設定、ユーザーの動作の追跡など、さまざまな目的に役立ちます。 ただし、プライバシー上の理由から Cookie を削除したり、閲覧の問題を解決したりすることもできます。 この記事では、次の方法について説明します。 すべての Cookie を表示する すべての Cookie を許可する 特定の Web サイトからの Cookie を許可する サード パーティの Cookie をブロックする [すべての Cookie をブロックする] 特定のサイトからの Cookie をブロックする すべての Cookie を削除する 特定のサイトから Cookie を削除する ブラウザーを閉じるたびに Cookie を削除する Cookie を使用してページを事前に読み込み、閲覧を高速化する すべての Cookie を表示する Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [ 設定] > [プライバシー]、[検索]、[サービス ] を選択します。 [ Cookie] を選択し、[ すべての Cookie とサイト データを表示 ] をクリックして、保存されているすべての Cookie と関連するサイト情報を表示します。 すべての Cookie を許可する クッキーを許可することで、ウェブサイトはブラウザ上のデータを保存および取得することができ、お客様の好みやログイン情報を記憶することで閲覧エクスペリエンスを向上させることができます。 Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [ 設定] > [プライバシー]、[検索]、[サービス ] を選択します。 [ Cookie] を選択し、[ サイトで Cookie データの保存と読み取りを許可する (推奨)] を有効にして、すべての Cookie を許可します。 特定のサイトからの Cookie を許可する クッキーを許可することで、ウェブサイトはブラウザ上のデータを保存および取得することができ、お客様の好みやログイン情報を記憶することで閲覧エクスペリエンスを向上させることができます。 Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [ 設定] > [プライバシー]、[検索]、[サービス ] を選択します。 [ Cookie] を選択し、[ 許可] に移動して Cookie を保存します。 サイトの URL を入力して、サイトごとに Cookie を許可するには、[サイトの 追加] を選択します。 サード パーティの Cookie をブロックする サード パーティのサイトが COOKIE を PC に保存したくない場合は、Cookie をブロックできます。 ただし、この操作を行うと、一部のページが正常に表示されなくなることがあります。また、サイトを閲覧するには Cookie を許可する必要があることを知らせるメッセージが表示されることがあります。 Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [ 設定] > [プライバシー]、[検索]、[サービス ] を選択します。 [ Cookie]\(Cookies\ ) を選択し、[ サード パーティの Cookie をブロック する] トグルを有効にします。 [すべての Cookie をブロックする] サード パーティのサイトが COOKIE を PC に保存したくない場合は、Cookie をブロックできます。 ただし、この操作を行うと、一部のページが正常に表示されなくなることがあります。また、サイトを閲覧するには Cookie を許可する必要があることを知らせるメッセージが表示されることがあります。 Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [ 設定] > [プライバシー]、[検索]、[サービス ] を選択します。 [ Cookie] を選択し 、[サイトで Cookie データの保存と読み取りを許可する (推奨)] を無効にして、すべての Cookie をブロックします。 特定のサイトからの Cookie をブロックする Microsoft Edge を使用すると、特定のサイトからの Cookie をブロックできますが、これを行うと、一部のページが正しく表示できなくなる場合や、Cookie がそのサイトの表示を許可する必要があることを通知するメッセージがサイトから届く場合があります。 特定のサイトからの Cookie をブロックするには: Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [ 設定] > [プライバシー]、[検索]、[サービス ] を選択します。 [ Cookie] を選択し、[ Cookie の保存と読み取りが許可されていません] に 移動します。 サイト の URL を入力してサイトごとに Cookie をブロックするには、[サイトの 追加] を選択します。 すべての Cookie を削除する Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [設定] > [プライバシー、検索、サービス] を選択します。 [ 閲覧データの消去 ] を選択し、[ 今すぐ閲覧データ を消去する ] の横にある [クリアする内容を選択する] を選択します。 [時間の範囲] で、時間の範囲を選択します。 [Cookie およびその他のサイト データ] を選択し、 [今すぐクリア] を選択します。 注: または、 Ctrl キー を押しながら Shift キーを押しながら DELETE キー を押し、手順 4 と 5 に進んで Cookie を削除することもできます。 これで、選択した時間範囲のすべての Cookie とその他のサイト データが削除されます。 これにより、ほとんどのサイトからサインアウトされます。 特定のサイトから Cookie を削除する Edge ブラウザーを開き、[ 設定など] を選択 > [設定] > [プライバシー]、[検索]、[サービス ] 。 [ Cookie] を選択し、[ すべての Cookie とサイト データを表示 する] をクリックし、Cookie を削除するサイトを検索します。 Cookie を削除するサイトの右側にある下矢印 を選択し、 [削除] を選択します。 選択したサイトの Cookie が削除されるようになりました。 Cookie を削除するサイトに対して、この手順を繰り返します。 ブラウザーを閉じるたびに Cookie を削除する Edge ブラウザーを開き、[ 設定など] を選択 > [設定] > [プライバシー]、[検索]、[サービス] の順に 選択します。 [ 閲覧データの消去 ] を選択し、 ブラウザーを閉じるたびにクリアする内容を選択 します。 [Cookie およびその他のサイト データ] トグルをオンにします。 この機能を有効にすると、Edge ブラウザーを閉じるたびに、すべての Cookie やその他のサイト データが削除されます。 これにより、ほとんどのサイトからサインアウトされます。 Cookie を使用してページを事前に読み込み、閲覧を高速化する Edge ブラウザーを開き ブラウザー ウィンドウの右上隅にある [設定など] を選択します。 [設定] > [プライバシー、検索、サービス] を選択します。 [Cookie] を 選択し、[ ページの事前読み込み] トグルを有効にして、閲覧と検索を高速化します。 RSS フィードを購読する ヘルプを表示 その他のオプションが必要ですか? ディスカバー コミュニティ お問い合わせ サブスクリプションの特典の参照、トレーニング コースの閲覧、デバイスのセキュリティ保護方法などについて説明します。 Microsoft 365 サブスクリプションの特典 Microsoft 365 のトレーニング Microsoft Security アクセシビリティ センター コミュニティは、質問をしたり質問の答えを得たり、フィードバックを提供したり、豊富な知識を持つ専門家の意見を聞いたりするのに役立ちます。 Microsoft コミュニティに問い合わせる Microsoft 技術コミュニティ Windows Insiders Microsoft 365 Insiders 一般的な問題の解決策を見つけるか、サポート エージェントからサポートを受けます。 オンライン サポート この情報は役に立ちましたか? はい いいえ ありがとうございます。Microsoft へのフィードバックがさらにありますか? 品質向上にご協力いただけますか? (助けになれるように、Microsoft にフィードバックを送ります。) 言語の品質にどの程度満足していますか? どのような要因がお客様の操作性に影響しましたか? 問題は解決した 指示がわかりやすかった わかりやすかった 専門用語が使用されていなかった 画像が役に立った 翻訳品質 画面が一致しなかった 指示が正しくない 技術的すぎる 情報が十分ではない 画像が不足していた 翻訳品質 その他のフィードバックはありますか? (省略可能) フィードバックを送信 [送信] を押すと、Microsoft の製品とサービスの改善にフィードバックが使用されます。 IT 管理者はこのデータを収集できます。 プライバシーに関する声明。 フィードバックをいただき、ありがとうございます。 × 最新情報 Surface Pro Surface Laptop Surface Laptop Studio 2 組織用 Copilot 個人用 Copilot Windows での AI Microsoft 製品を見る Windows 11 アプリ Microsoft Store アカウント プロファイル ダウンロード センター Microsoft Store サポート 返品・返金 ご注文履歴 Microsoft Store をお選びいただく理由 教育 Microsoft Education 教育機関向けデバイス Microsoft Teams for Education Microsoft 365 Education Office Education 教育者向けトレーニングおよび開発 学生および保護者向けキャンペーン 学生向け Azure ビジネス Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 開発者 & IT Microsoft 開発者 Microsoft Learn AI マーケットプレース アプリのサポート Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 会社 採用情報 会社のニュース マイクロソフトにおけるプライバシー 投資家 アクセシビリティ 持続可能性 日本語 (日本) プライバシーに関する選択のオプトアウト アイコン プライバシーに関する選択 プライバシーに関する選択のオプトアウト アイコン プライバシーに関する選択 コンシューマーの正常性のプライバシー Microsoft に問い合わせ プライバシー 特定商取引法に基づく表示 Cookie の管理 使用条件 商標 広告について © Microsoft 2026 | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/configuration/services/index.html | 2.5.19. Custom Services — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.5.1. Configuring Buildbot 2.5.2. Global Configuration 2.5.3. Change Sources and Changes 2.5.4. Changes 2.5.5. Schedulers 2.5.6. Workers 2.5.7. Builder Configuration 2.5.8. Projects 2.5.9. Codebases 2.5.10. Build Factories 2.5.11. Build Sets 2.5.12. Properties 2.5.13. Build Steps 2.5.14. Interlocks 2.5.15. Report Generators 2.5.16. Reporters 2.5.17. Web Server 2.5.18. Change Hooks 2.5.19. Custom Services 2.5.19.1. FailingBuildsetCanceller 2.5.19.2. OldBuildCanceller 2.5.20. DbConfig 2.5.21. Configurators 2.5.22. Manhole 2.5.23. Multimaster 2.5.24. Multiple-Codebase Builds 2.5.25. Miscellaneous Configuration 2.5.26. Testing Utilities 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.5. Configuration 2.5.19. Custom Services View page source 2.5.19. Custom Services Custom services are stateful components of Buildbot that can be added to the services key of the Buildbot config dictionary. The following is the services that are meant to be used without advanced knowledge of Buildbot. FailingBuildsetCanceller OldBuildCanceller More complex services are described in the developer section of the Buildbot manual. They are meant to be used by advanced users of Buildbot. Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/configuration/reporters/index.html | 2.5.16. Reporters — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.5.1. Configuring Buildbot 2.5.2. Global Configuration 2.5.3. Change Sources and Changes 2.5.4. Changes 2.5.5. Schedulers 2.5.6. Workers 2.5.7. Builder Configuration 2.5.8. Projects 2.5.9. Codebases 2.5.10. Build Factories 2.5.11. Build Sets 2.5.12. Properties 2.5.13. Build Steps 2.5.14. Interlocks 2.5.15. Report Generators 2.5.16. Reporters 2.5.16.1. ReporterBase 2.5.16.2. BitbucketServerCoreAPIStatusPush 2.5.16.3. BitbucketServerPRCommentPush 2.5.16.4. BitbucketServerStatusPush 2.5.16.5. BitbucketStatusPush 2.5.16.6. GerritStatusPush 2.5.16.7. GerritVerifyStatusPush 2.5.16.8. GitHubCommentPush 2.5.16.9. GitHubStatusPush 2.5.16.10. GitLabStatusPush 2.5.16.11. HttpStatusPush 2.5.16.12. IRC Bot 2.5.16.13. MailNotifier 2.5.16.14. PushjetNotifier 2.5.16.15. PushoverNotifier 2.5.16.16. Telegram Bot 2.5.16.17. ZulipStatusPush 2.5.17. Web Server 2.5.18. Change Hooks 2.5.19. Custom Services 2.5.20. DbConfig 2.5.21. Configurators 2.5.22. Manhole 2.5.23. Multimaster 2.5.24. Multiple-Codebase Builds 2.5.25. Miscellaneous Configuration 2.5.26. Testing Utilities 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.5. Configuration 2.5.16. Reporters View page source 2.5.16. Reporters The Buildmaster has a variety of ways to present build status to various users. Each such delivery method is a Reporter Target object in the configuration’s services list. To add reporter targets, you just append more objects to this list: c [ 'services' ] = [] m = reporters . MailNotifier ( fromaddr = "buildbot@localhost" , extraRecipients = [ "builds@lists.example.com" ], sendToInterestedUsers = False ) c [ 'services' ] . append ( m ) c [ 'services' ] . append ( reporters . irc . IRC ( host = "irc.example.com" , nick = "bb" , channels = [{ "channel" : "#example1" }, { "channel" : "#example2" , "password" : "somesecretpassword" }])) Most reporter objects take a tags= argument, which can contain a list of tag names. In this case, the reporters will only show status for Builders that contain the named tags. Note Implementation Note Each of these objects should be a service.BuildbotService which will be attached to the BuildMaster object when the configuration is processed. The following reporters are available: BitbucketServerCoreAPIStatusPush BitbucketServerPRCommentPush BitbucketServerStatusPush BitbucketStatusPush GerritStatusPush GerritVerifyStatusPush GitHubCommentPush GitHubStatusPush GitLabStatusPush HttpStatusPush IRC MailNotifier PushjetNotifier PushoverNotifier TelegramBot ZulipStatusPush Most of the report generators derive from ReporterBase which implements basic reporter management functionality. Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://support.microsoft.com/cs-cz/microsoft-edge/microsoft-edge-data-o-proch%C3%A1zen%C3%AD-a-ochrana-soukrom%C3%AD-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Microsoft Edge, data o procházení a ochrana soukromí - Podpora Microsoftu Přeskočit na hlavní obsah Microsoft Podpora Podpora Podpora Domů Microsoft 365 Office Produkty Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows a další... Zařízení Surface Počítačové příslušenství Xbox Hraní počítačových her HoloLens Surface Hub Záruky na hardware Účet a fakturace Klient Microsoft Store & fakturace Prostředky Co je nového Komunitní fóra Správci Microsoft 365 Upozornění pro malé firmy Pro vývojáře Vzdělávání Nahlásit podvod při poskytování technické podpory Bezpečnost produktů Více Koupit Microsoft 365 Vše od Microsoftu Global Microsoft 365 Teams Copilot Windows Surface Xbox Nabídky Podpora Software Software Aplikace pro Windows Umělá inteligence OneDrive Outlook Přechod ze Skypu na Teams OneNote Microsoft Teams Počítače a zařízení Počítače a zařízení Koupit Xbox Příslušenství Zábava Zábava Xbox Game Pass Ultimate Konzole Xbox a hry Hry pro PC Nabídky pro firmy Nabídky pro firmy Microsoft Security Azure Dynamics 365 Microsoft 365 pro firmy Microsoft Industry Microsoft Power Platform Windows 365 Vývojáři a IT Vývojáři a IT Microsoft pro vývojáře Microsoft Learn Podpora aplikací s umělou inteligenci v obchodě Marketplace Odborná komunita Microsoft Microsoft Marketplace Visual Studio Marketplace Rewards Další Další Zdarma ke stažení a zabezpečení Vzdělávání Dárkové karty Zobrazit mapu stránek Hledat Hledat nápovědu Žádné výsledky Zrušit Přihlásit se Přihlásit se pomocí účtu Microsoft Přihlaste se nebo si vytvořte účet. Dobrý den, Vyberte jiný účet. Máte více účtů. Zvolte účet, pomocí kterého se chcete přihlásit. Microsoft Edge, data o procházení a ochrana soukromí Platí pro Privacy Microsoft Edge Windows 10 Windows 11 Microsoft Edge vám pomůže procházet, vyhledávat, nakupovat online a další možnosti. Microsoft Edge stejně jako všechny moderní prohlížeče umožňuje shromažďovat a ukládat konkrétní data na vašem zařízení, jako jsou například soubory cookie, a umožňuje vám zasílat nám informace, jako je historie procházení, abychom mohli poskytovat co nejbohatší, nejrychlejší a nejvíce přizpůsobené prostředí a možnosti. Kdykoli shromažďujeme data, chceme mít jistotu, že je to pro vás ta správná volba. Někteří lidé mají obavy, pokud jde o shromažďování jejich historie procházení webu. Proto vám říkáme, jaká data jsou uložená na vašem zařízení nebo která shromažďujeme. Umožňujeme vám řídit, jaká data se shromažďují. Doporučujeme, abyste si prošli další informace o ochraně osobních údajů v prohlížeči Microsoft Edge v našem Prohlášení o ochraně osobních údajů . Jaká data shromažďujeme nebo ukládáme a proč Společnost Microsoft používá ke zdokonalování svých produktů a služeb diagnostická data. Tato data používáme k lepšímu pochopení toho, jak naše produkty fungují a kde jsou potřeba určitá vylepšení. Prohlížeč Microsoft Edge shromažďuje sadu nezbytných diagnostických dat, která zajišťují aby byl prohlížeč zabezpečený, aktualizovaný a fungoval předvídatelným způsobem. Společnost Microsoft věří minimalizaci shromažďování informací a chová se podle toho. Snažíme se shromáždit pouze informace, které potřebujeme, a ukládat je pouze po dobu, po jakou je potřeba k poskytování služby nebo k analýze. Kromě toho můžete sami určit, jestli se budou nepovinná diagnostická data spojená s vaším zařízením sdílet se společností Microsoft za účelem řešení produktových problémů a vylepšování produktů a služeb společnosti Microsoft. Při používání funkcí a služeb v aplikaci Microsoft Edge se diagnostická data o tom, jak tyto funkce používáte, odesílají do Microsoftu. Prohlížeč Microsoft Edge ukládá na vašem zařízení vaši historii procházení, což jsou informace o webových stránkách, které navštívíte. V závislosti na vašem nastavení je tato historie procházení odesílána do Microsoftu. To nám pomáhá hledat a opravovat problémy a zlepšovat naše produkty a služby pro všechny uživatele. Shromažďování nepovinných diagnostických dat můžete spravovat v prohlížeči tak, že vyberete Nastavení a další možnosti > Nastavení > Ochrana osobních údajů, vyhledávání a služby > Ochrana osobních údajů a zapnutím nebo vypnutím možnosti Odesílat volitelná diagnostická data za účelem vylepšení produktů Microsoftu . To zahrnuje data z testování nových prostředí. K dokončení změn tohoto nastavení restartujte aplikaci Microsoft Edge. Zapnutím těchto nastavení povolíte sdílení nepovinných diagnostických dat z jiných aplikací (například aplikací pro streamování videa, které hostují webovou platformu prohlížeče Microsoft Edge ke streamování tohoto videa) používajících prohlížeč Microsoft Edge se společností Microsoft. Webová platforma prohlížeče Microsoft Edge bude společnosti Microsoft odesílat informace o tom, jak používáte webovou platformu a jaké stránky v aplikaci navštěvujete. Toto shromažďování informací určují vaše nastavení nepovinných diagnostických dat v části Ochrana osobních údajů, vyhledávání a služby v prohlížeči Microsoft Edge. Ve Windows 10 jsou tato nastavení určena nastavením diagnostických dat systému Windows. Pokud chcete změnit nastavení diagnostických dat, vyberte Spustit > Nastavení > Ochrana osobních údajů > Diagnostika & zpětnou vazbu . Od 6. března 2024 se diagnostická data Microsoft Edge shromažďují odděleně od diagnostických dat Windows na zařízeních Windows 10 (verze 22H2 a novější) a Windows 11 (verze 23H2 a novější) v Evropském hospodářském prostoru. Pro tyto verze Windows a na všech ostatních platformách můžete změnit nastavení v Aplikaci Microsoft Edge tak, že vyberete Nastavení a další možnosti > Nastavení > Ochrana osobních údajů, vyhledávání a služby . V některých případech může nastavení diagnostických dat spravovat vaše organizace. Když něco hledáte, může Microsoft Edge poskytovat návrhy, co hledáte. Pokud chcete tuto funkci zapnout, vyberte Nastavení a další možnosti > Nastavení > Ochrana osobních údajů, vyhledávání a služby > Vyhledávání a propojená prostředí > panelu Adresa a hledání > Návrhy a filtry hledání a zapněte možnost Zobrazovat návrhy hledání a webů pomocí zadaných znaků . Když začnete psát, informace, které zadáte na panelu Adresa, se odesílají výchozímu zprostředkovateli hledání, abyste měli k dispozici okamžité návrhy hledání a webů. Když používáte procházení InPrivate nebo režim hosta , microsoft Edge shromažďuje určité informace o tom, jak používáte prohlížeč, v závislosti na nastavení diagnostických dat Windows nebo nastavení ochrany osobních údajů v aplikaci Microsoft Edge, ale automatické návrhy jsou vypnuté a informace o webech, které navštívíte, se neshromažďují. Když zavřete všechna okna InPrivate, odstraní Microsoft Edge vaši historii procházení, soubory cookie a data webů a také hesla, adresy a údaje formulářů. Novou relaci InPrivate můžete spustit tak, že na počítači vyberete Nastavení a další možnosti . Na mobilním zařízení vyberte Karty . Microsoft Edge také nabízí funkce, které vám i vašemu obsahu pomáhají zajistit bezpečnost online. Filtr SmartScreen v programu Windows Defender automaticky blokuje weby a stahování obsahu, které jsou hlášeny jako škodlivé. Filtr SmartScreen v programu Windows Defender porovnává adresu navštívené webové stránky se seznamem webových adres uložených na vašem zařízení, o kterých se Microsoft domnívá, že jsou legitimní. Adresy, které nejsou v seznamu vašeho zařízení, a adresy souborů, které stahujete, se budou odesílat a Microsoft kontrolovat v často aktualizovaném seznamu webových stránek a souborů ke stažení, které byly nahlášeny Microsoft jako nebezpečné nebo podezřelé. K urychlení únavných úkolů, jako je vyplňování formulářů a zadávání hesel, může Microsoft Edge tyto informace ukládat a pomáhat vám. Pokud se rozhodnete tyto funkce používat, bude Microsoft Edge ukládat tyto informace na vašem zařízení. Pokud jste zapnuli synchronizaci pro vyplňování formulářů, jako jsou adresy nebo hesla, budou tyto informace odeslány do cloudu Microsoftu a uloženy s vaším účtem Microsoft, aby se synchronizovaly ve všech vašich přihlášených verzích Microsoft Edge. Tato data můžete spravovat v Části Nastavení a další > Nastavení > Profily > Synchronizovat . Aby bylo možné integrovat vaše prostředí procházení s dalšími aktivitami, které na svém zařízení děláte, sdílí Microsoft Edge vaši historii procházení se systémem Microsoft Windows prostřednictvím svého indexeru. Tyto informace se ukládají místně na zařízení. Zahrnuje adresy URL, kategorii, ve které může být adresa URL relevantní, například "nejnavštěvovanější", "nedávno navštívená" nebo "nedávno uzavřená", a také relativní četnost nebo aktuálnost v rámci každé kategorie. Weby, které navštívíte v režimu InPrivate, nebudou sdíleny. Tyto informace jsou pak dostupné pro jiné aplikace v zařízení, jako je nabídka Start nebo hlavní panel. Tuto funkci můžete spravovat tak, že vyberete Nastavení a další možnosti > Nastavení > Profily a zapnete nebo vypnete Sdílet údaje o procházení s dalšími funkcemi Windows . Pokud je vypnutá, odstraní se všechna dříve sdílená data. Z důvodu ochrany určitého obsahu videí a hudby před kopírováním ukládají některé streamovací weby do vašeho zařízení data technologie DRM (Správa digitálních práv) včetně jedinečného identifikátoru (ID) a licencí k médiím. Když pak na některý z těchto webů přejdete, načte informace DRM pro ověření toho, že máte oprávnění obsah používat. Microsoft Edge také ukládá soubory cookie, což jsou malé soubory, které se umísťují do vašeho zařízení při procházení webu. Mnoho webů používá soubory cookie k ukládání informací o vašich preferencích a nastaveních, jako je například uložení položek ve vašem nákupním košíku, abyste je nemuseli přidávat při každé návštěvě. Některé weby soubory cookie používají ke shromažďování informací o vaší online aktivitě, aby vám mohly nabízet reklamu na základě vašich zájmů. Microsoft Edge nabízí možnost mazat soubory cookie a zabránit webům v jejich dalším ukládání. Microsoft Edge bude webům zasílat žádosti Do Not Track (Nesledovat), pokud je zapnuté nastavení Posílat žádosti Do Not Track (Nesledovat) . Toto nastavení je k dispozici v části Nastavení a další > Nastavení > Ochrana osobních údajů, vyhledávání a služby > Ochrana osobních údajů > Odesílat žádosti "Nesledovat". Weby ale můžou sledovat vaše aktivity, i po odeslání žádosti DNT (Nesledovat). Vymazání dat shromážděných nebo uložených v prohlížeči Microsoft Edge Vymazání údajů o procházení uložených na vašem zařízení, jako jsou uložená hesla nebo soubory cookie: V aplikaci Microsoft Edge vyberte Nastavení a další > Nastavení > Ochrana osobních údajů, vyhledávání a služby > Vymazat údaje o procházení . Vyberte Zvolit, co se má vymazat vedle možnosti Vymazat údaje o procházení. V části Časový rozsah zvolte časové období. Zaškrtněte políčko vedle každého datového typu, který chcete vymazat, a pak vyberte Vymazat. Pokud chcete, můžete vybrat Zvolit, co se má vymazat při každém zavření prohlížeče a zvolit, které datové typy se mají vymazat. Další informace o tom, co se odstraní u jednotlivých položek historie prohlížeče . Vymazání historie procházení shromážděné společností Microsoft: Pokud si chcete prohlédnout historii procházení přidruženou k vašemu účtu, přihlaste se ke svému účtu na stránce account.microsoft.com . Kromě toho máte také možnost vymazat v Řídicím panelu ochrany osobních údajů vaše data o procházení, která shromáždila společnost Microsoft. Pokud chcete odstranit historii procházení a další diagnostická data přidružená k vašemu Windows 10 zařízení, vyberte Spustit > Nastavení > Ochrana osobních údajů > Diagnostika & zpětnou vazbu a pak v části Odstranit diagnostická data vyberte Odstranit . Vymazání historie procházení sdílené s dalšími funkcemi Microsoftu na místním zařízení: V aplikaci Microsoft Edge vyberte Nastavení a další možnosti > Nastavení > Profily . Vyberte Sdílet data o procházení s dalšími funkcemi Systému Windows . Přepněte toto nastavení do polohy Vypnuto . Správa nastavení ochrany osobních údajů v aplikaci Microsoft Edge Pokud chcete zkontrolovat a přizpůsobit nastavení ochrany osobních údajů, vyberte Nastavení a další > Nastavení > Ochrana osobních údajů, vyhledávání a služby . > ochrana osobních údajů. Další informace o ochraně soukromí v prohlížeči Microsoft Edge si můžete přečíst v Zprávě o ochraně osobních údajů Microsoft Edge . PŘIHLÁSIT SE K ODBĚRU INFORMAČNÍCH KANÁLŮ RSS Potřebujete další pomoc? Chcete další možnosti? Zjišťování Komunita Kontaktujte nás Prozkoumejte výhody předplatného, projděte si školicí kurzy, zjistěte, jak zabezpečit své zařízení a mnohem více. Výhody předplatného Microsoft 365 Školení k Microsoft 365 Zabezpečení od Microsoftu Centrum přístupnosti Komunity vám pomohou klást otázky a odpovídat na ně, poskytovat zpětnou vazbu a vyslechnout odborníky s bohatými znalostmi. Zeptejte se v komunitě Microsoftu Technická komunita Microsoftu Účastníci programu Windows Insider Účastníci programu Microsoft 365 Insider Najděte si řešení běžných problémů nebo získejte pomoc od agenta podpory. Online podpora Byly tyto informace užitečné? Ano Ne Děkujeme! Máte nějakou další zpětnou vazbu pro Microsoft? Můžete nám pomoct službu zlepšit? (Pošlete Microsoftu svůj názor, abychom vám mohli pomoct.) Jak jste spokojeni s kvalitou jazyka? Co ovlivnilo váš názor? Vyřešilo to můj problém Jasné pokyny Snadný postup Bez žargonu Obrázky pomohly Kvalita překladu Neodpovídalo to mé obrazovce Nesprávné pokyny Příliš technické Nedostatek informací Nedostatek obrázků Kvalita překladu Máte další zpětnou vazbu? (Nepovinné) Odeslat názor Po stisknutí tlačítka pro odeslání se vaše zpětná vazba použije k vylepšování produktů a služeb Microsoftu. Váš správce IT bude moci tato data shromažďovat. Prohlášení o zásadách ochrany osobních údajů. Děkujeme vám za zpětnou vazbu. × Co je nového Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot pro organizace Copilot pro osobní používání Microsoft 365 Prohlédnout produkty Microsoft Microsoft Store Profil účtu Centrum stahování Podpora pro Microsoft Store Vrácení Sledování objednávky Recyklace Commercial Warranties Vzdělávání Microsoft Education Zařízení pro vzdělávání Microsoft Teams pro vzdělávání Microsoft 365 Education Office Education Vzdělávání a rozvoj pedagogů Akce pro studenty a rodiče Azure pro studenty Firmy Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Vývojáři a IT Microsoft pro vývojáře Microsoft Learn Podpora aplikací s umělou inteligenci v obchodě Marketplace Odborná komunita Microsoft Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Společnost Kariéra Novinky u společnosti Microsoft a ochrana osobních údajů Investoři Udržitelnost Čeština (Česko) Ikona nesouhlasu s volbami ochrany osobních údajů Vaše volby ochrany osobních údajů Ikona nesouhlasu s volbami ochrany osobních údajů Vaše volby ochrany osobních údajů Ochrana osobních údajů spotřebitele ve zdravotnictví Kontaktovat Microsoft Ochrana osobních údajů Spravovat soubory cookie Podmínky používání Ochranné známky O našich reklamách EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://www.iso.org/es/contents/data/sdg/SDG02.html | ISO - Zero Hunger Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito ODS 2 Zero Hunger Objetivos de Desarrollo Sostenible ODS 01 - No Poverty ODS 02 - Zero Hunger ODS 03 - Good Health and Well-being ODS 04 - Quality Education ODS 05 - Gender Equality ODS 06 - Clean Water and Sanitation ODS 07 - Affordable and Clean Energy ODS 08 - Decent Work and Economic Growth ODS 09 - Industry, Innovation and Infrastructure ODS 10 - Reduced Inequalities ODS 11 - Sustainable Cities and Communities ODS 12 - Responsible Consumption and Production ODS 13 - Climate Action ODS 14 - Life Below Water ODS 15 - Life on Land ODS 16 - Peace, Justice and Strong Institutions ODS 17 - Partnerships for the Goals Goal 2: Zero Hunger End hunger, achieve food security and improved nutrition and promote sustainable agriculture Sustainable Development Goal 2 (SDG 2) aims to end hunger, achieve food security and improved nutrition, and promote sustainable agriculture. This goal is crucial for ensuring the well-being of all people and the sustainability of our planet. At ISO, we are committed to supporting SDG 2 through our standards, which provide frameworks and solutions that enhance food safety, promote sustainable agriculture, and improve nutrition. How ISO Standards Support SDG 2 ISO standards play a vital role in supporting SDG 2 by addressing key aspects of food security, nutrition, and sustainable agriculture. Our standards help ensure that food is safe, nutritious, and of high quality, while also promoting sustainable agricultural practices. Here are some of the relevant standards: ISO 22000: Food safety management systems — Requirements for any organization in the food chain Provides a framework for effectively managing food safety risks and ensuring the safety of food products throughout the food chain. Helps organizations implement a comprehensive food safety management system, contributing to improved food security and consumer health. ISO 14001: Environmental management systems — Requirements with guidance for use While not exclusively focused on agriculture, this standard helps agricultural organizations manage their environmental responsibilities. Supports sustainable farming practices by providing a framework for reducing environmental impacts, conserving resources, and improving overall sustainability in agricultural production. Take Action: Implement ISO Standards to Support SDG 2 Interested in learning how your organization can contribute to ending hunger and promoting sustainable agriculture through the implementation of ISO standards? Download our comprehensive guide to understand the role of ISO standards in achieving SDG 2 and other global goals. Together, we can work towards a world free from hunger and with sustainable food systems for all. ISO and food ISO's solutions for ensuring quality and safety in the food industry are the subject of this brochure which provides a concise overview of International Standards available and how they can help. Normas ODS Objetivo 2: Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://co.linkedin.com/company/visma | Visma | LinkedIn Pasar al contenido principal LinkedIn Artículos Personas Learning Empleos Juegos Iniciar sesión Unirte gratis Visma Desarrollo de software Empowering businesses with software that simplifies and automates complex processes. Ver empleos Seguir Ver los 5582 empleados Denunciar esta empresa Sobre nosotros Visma is a leading provider of mission-critical business software, with revenue of € 2.8 billion in 2024 and 2.2 million customers across Europe and Latin America. By simplifying and automating the work of SMBs and the public sector, we help unleash the power of digitalization and AI across our societies and economies. Sitio web http://www.visma.com Enlace externo para Visma Sector Desarrollo de software Tamaño de la empresa Más de 10.001 empleados Sede Oslo Tipo De financiación privada Fundación 1996 Especialidades Software, ERP, Payroll, HRM, Procurement, accounting y eGovernance Productos No hay contenido anterior Severa, Software de automatización de servicios profesionales (PSA) Severa Software de automatización de servicios profesionales (PSA) Visma Sign, Software de firma electrónica Visma Sign Software de firma electrónica No hay contenido siguiente Ubicaciones Principal Karenslyst Allé 56 Oslo, NO-0277, NO Cómo llegar Chile, CL Cómo llegar Lindhagensgatan 94 112 18 Stockholm Stockholm, 112 18, SE Cómo llegar Keskuskatu 3 HELSINKI, Helsinki FI-00100, FI Cómo llegar Amsterdam, NL Cómo llegar Belgium, BE Cómo llegar Ireland, IE Cómo llegar Spain, ES Cómo llegar Slovakia, SK Cómo llegar Portugal, PT Cómo llegar France, FR Cómo llegar Romania, RO Cómo llegar Latvia, LV Cómo llegar Finland, FI Cómo llegar England, GB Cómo llegar Hungary, HU Cómo llegar Poland, PL Cómo llegar Brazil, BR Cómo llegar Italy, IT Cómo llegar Argentina, AR Cómo llegar Austria, AT Cómo llegar Croatia, HR Cómo llegar Mexico, MX Cómo llegar Columbia, CO Cómo llegar Denmark, DK Cómo llegar Germany, DE Cómo llegar Mostrar más ubicaciones Mostrar menos ubicaciones Empleados en Visma Jarmo Annala Markku Siikala Marko Suomi Sauli Karhu Ver todos los empleados Actualizaciones Visma 131.979 seguidores 22 h Denunciar esta publicación 🚀 Why is the right leadership so important when scaling a company? At Visma, we’ve learned that growth is about talent development. And talent development is all about strong leadership. Strong leaders build trust and create teams that can move quickly without losing alignment. 👇 Read more about how Visma invests in leadership development and cross-company networks to help our companies scale effectively. And how founders and business builders can take a similar approach. 27 Recomendar Comentar Compartir Visma 131.979 seguidores 4 días Editado Denunciar esta publicación “Growth isn’t luck – it’s about creating the right conditions for success.” 🚀 In our latest blog post, Visma’s Chief Growth Officer, Ari-Pekka Salovaara , shares what really fuels Visma’s continued growth: 180+ companies learning from each other, the entrepreneurial freedom to experiment, and a relentless focus on what drives results. From the SMB Olympics to AI-powered innovation - Ari-Pekka explains how Visma keeps its entrepreneurial spirit alive - and what founders should focus on to scale sustainably in an evolving SMB landscape. Read the full story - https://lnkd.in/dY6-J2AC 48 Recomendar Comentar Compartir Visma 131.979 seguidores 1 semana Denunciar esta publicación ✨ 2026 starts with action, not promises. Across Visma, AI is moving from experiments to everyday impact — embedded in products, operations, and engineering to create value where it matters most. What’s next? We’re just getting started. 👉 In our latest press release, T. Alexander Lystad , CTO at Visma, shares how we’re enabling AI deployment at scale across our business units. https://lnkd.in/dP3rjJbp 94 Recomendar Comentar Compartir Visma 131.979 seguidores 2 semanas Denunciar esta publicación 💫 As we wrap up another exciting year, we want to thank our customers, partners, entrepreneurs, employees and communities across Europe and Latin America for being part of our journey. We're so proud to support millions of people and businesses with technology that makes work smarter, simpler and more meaningful. None of this would be possible without the incredible talent and entrepreneurial spirit across our network. 🌍 From all of us at Visma, Merry Christmas and Happy Holidays! ✨ 243 1 comentario Recomendar Comentar Compartir Visma 131.979 seguidores 3 semanas Denunciar esta publicación Leading the way in ERP, CRM & HRM🔝 Our largest Danish company, e-conomic , has been ranked #1 in Computerworld Danmark ’s Top 100 in the ERP, CRM & HRM category – a recognition of the team’s dedication to building solutions that truly make a difference for businesses in Denmark🤝. Computerworld’s Top 100 is an annual ranking that has, since 1999, identified the financially strongest and best-run IT companies in Denmark⚙️📈 As e-conomic ’s Managing Director, Karina Wellendorph , says: “We are in a period focused on long-term stability, quality, and security. We work hard to create solutions that our customers find relevant.” Several other Danish Visma companies are also featured in the Top 100 ranking, highlighting the strength of our portfolio🙌👉 Visma Enterprise Danmark , DataLøn , Dinero , ZeBon ApS , efacto , Intempus Timeregistrering , TIMEmSYSTEM ApS , Acubiz , and Visma Public Technologies. Together, these companies showcase what makes Visma unique globally: locally rooted businesses with entrepreneurial drive and a relentless focus on customer value. With Visma behind them, each company combines local expertise, entrepreneurial drive, and shared knowledge to maximize value for customers worldwide🌍 Explore what it means to become a Visma company 👉 https://lnkd.in/dyYc_nJw #ChampionsOfBusinessSoftware 215 2 comentarios Recomendar Comentar Compartir Visma 131.979 seguidores 3 semanas Denunciar esta publicación Accounting is no longer about reporting. It’s about advising. 📊 In our latest blog article, Joris Joppe , Managing Director at Visionplanner , outlines six practical steps for accounting teams to embrace AI with confidence: from mindset shifts and AI copilots to new pricing models and trusted insights. The future of accounting is already here. Are you ready to step into it? Read 6 steps to embrace AI in accounting on Visma’s blog 💻 , or take a deeper dive by listening to Joris’ appearance on the Voice of Visma podcast. 🎧 🔗 Links in the comments ⤵️ … más 28 2 comentarios Recomendar Comentar Compartir Visma 131.979 seguidores 3 semanas Denunciar esta publicación 🚀 From freelance growth hacker to Managing Director of BuchhaltungsButler . Maxin Schneider ’s journey is a powerful example of how curiosity, learning by doing, and a growth mindset can flourish in the right environment. Throughout her journey, Visma’s trust in people, belief in potential, and long-term support for development have played a defining role. In this new episode of Voice of Visma, Maxin shares how being part of Visma, opens up to a network of companies, where knowledge, challenges, and experiences are actively shared, and has helped her grow as a leader and entrepreneur. When leadership is backed by trust and collective insight, growth becomes a shared effort. 👉 Watch the full episode here - https://lnkd.in/gfiP9sZs … más Voice of Visma - Maxin Schneider 75 2 comentarios Recomendar Comentar Compartir Visma 131.979 seguidores 1 mes Denunciar esta publicación 🤖 What skills will define successful software companies in the age of AI? At Visma, we’ve learned that scaling in this new era isn’t just about using AI tools. It’s about building the right capabilities across every team, from developers to leaders. 👇 Here you can read about 3 skill areas that have helped Visma’s companies grow and innovate in an AI-driven industry. 104 Recomendar Comentar Compartir Visma 131.979 seguidores 1 mes Editado Denunciar esta publicación Visma reaffirmed as one of Europe’s 2026 Diversity Leaders. 🙌 We’re proud to share that Visma has once again been recognised by the Financial Times as one of Europe’s Diversity Leaders for 2026. Across our 180+ companies, diversity, inclusion, innovation, and entrepreneurship are part of our DNA, and this recognition shows that our colleagues truly feel Visma is a place where everyone belongs. 🤝💛 To celebrate, we’re sharing a short moment featuring entrepreneur and Managing Director Thea Boje Windfeldt , who talks about how individuality is embraced in Visma’s culture. Here’s to building a workplace where everyone can be themselves and thrive. #Diversity #Inclusion #LifeatVisma #Innovation #Entrepreneurship … más 84 3 comentarios Recomendar Comentar Compartir Visma 131.979 seguidores 1 mes Denunciar esta publicación 💡 What is Visma’s AI strategy? As an owner of 180+ tech companies, our AI focus is clear: creating real value for businesses and their people. With innovation happening across so many companies, the strength of our portfolio lies in how we share it. Every experiment, breakthrough and lesson learned makes the entire group stronger. We sat down with our CTO, T. Alexander Lystad , and AI Director, Jacob Nyman , to explore how Visma approaches AI. From building agentic products that do the work, to leveraging data, to always putting trust first. 🔗 Find the link to the full article in the comments section. ⤵️ 164 3 comentarios Recomendar Comentar Compartir Únete para ver lo que te estás perdiendo Encuentra a personas que conoces en Visma Consulta empleos recomendados para ti Ve todas las actualizaciones, noticias y artículos Unirse ahora Páginas asociadas Xubio Desarrollo de software Buenos Aires, Buenos Aires Autonomous City Visma Latam HR Servicios y consultoría de TI Buenos Aires, Vicente Lopez Visma Enterprise Danmark Servicios y consultoría de TI Visma Tech Lietuva Servicios y consultoría de TI Vilnius, Vilnius Calipso Desarrollo de software Visma Enterprise Servicios y tecnologías de la información Oslo, Oslo BlueVi Desarrollo de software Nieuwegein, Utrecht SureSync Servicios y consultoría de TI Rijswijk, Zuid-Holland Visma Tech Portugal Servicios y consultoría de TI Horizon.lv Servicios y tecnologías de la información Laudus Desarrollo de software Providencia, Región Metropolitana de Santiago Contagram Desarrollo de software CABA, Buenos Aires eAccounting Servicios y tecnologías de la información Oslo, NORWAY Visma Net Sverige Servicios y tecnologías de la información Visma UX Servicios de diseño 0277 Oslo, Oslo Seiva – Visma Advantage Servicios y tecnologías de la información Stockholm, Stockholm County Control Edge Programas económicos Malmö l Stockholm l Göteborg, Skåne County Mostrar más páginas asociadas Mostrar menos páginas asociadas Páginas similares Visma Latam HR Servicios y consultoría de TI Buenos Aires, Vicente Lopez Conta Azul Servicios financieros Joinville, SC Visma Enterprise Danmark Servicios y consultoría de TI Accountable Servicios financieros Brussels, Brussels Lara AI Desarrollo de software Talana Servicios de recursos humanos Las Condes, Santiago Metropolitan Region e-conomic Desarrollo de software Fortnox AB Desarrollo de software Rindegastos Servicios y consultoría de TI Las Condes, Región Metropolitana de Santiago Spiris | Visma Servicios y consultoría de TI Växjö, Kronoberg County Mostrar más páginas similares Mostrar menos páginas similares Buscar empleos Empleos de Analista 15.600 empleos abiertos Empleos de Director de proyecto 1849 empleos abiertos Empleos de Ingeniero 13.208 empleos abiertos Empleos de Desarrollador 6863 empleos abiertos Empleos de Director de ventas 2771 empleos abiertos Empleos de Ingeniero de software 11.074 empleos abiertos Empleos de Analista de datos 11.991 empleos abiertos Empleos de Director 6682 empleos abiertos Empleos de Analista de contabilidad 5435 empleos abiertos Empleos de Ejecutivo de cuentas 858 empleos abiertos Empleos de Controlador 411 empleos abiertos Empleos de Jefe de marketing 1176 empleos abiertos Empleos de Jefe de operaciones 502 empleos abiertos Empleos de Presidente 25 empleos abiertos Empleos de Desarrollador web 2407 empleos abiertos Empleos de Analista financiero 4031 empleos abiertos Empleos de Analista administrativo 4146 empleos abiertos Empleos de Desarrollador de sistemas 3463 empleos abiertos Empleos de Maestro 430 empleos abiertos Empleos de Ingeniero de sistemas 7435 empleos abiertos Ver más empleos como este Ver menos empleos como este Financiación Visma 6 rondas en total Última ronda Mercado secundario 10 oct 2021 Enlace externo a Crunchbase para la última ronda de financiación Ver más información en Crunchbase Más búsquedas Más búsquedas Empleos de Ingeniero Empleos de Desarrollador Empleos de Director de ventas Empleos de Director de proyecto Empleos de Ingeniero de software Empleos de Analista Empleos de Director Empleos de Jefe de marketing Empleos de Jefe de ventas Empleos de Jefe de operaciones Empleos de Ingeniero industrial Empleos de Ingeniero de pruebas Empleos de Director de operaciones Empleos de Arquitecto de soluciones Empleos de Desarrollo web Empleos de Ingeniero de proyecto Empleos de Desarrollador web Empleos de Ejecutivo de cuentas Empleos de Analista de marketing Empleos de Analista de datos Empleos de Director de arte Empleos de Presidente Empleos de Jefe de producto Empleos de Jefe de recursos humanos Empleos de Vicepresidente Empleos de Ingeniero de producto Empleos de Controlador Empleos de Desarrollador de aplicaciones Empleos de Investigador Empleos de Director financiero Empleos de Director de finanzas Empleos de Analista de TI Empleos de Director de marketing Empleos de Asistente de marketing Empleos de Analista de sistema Empleos de Analista financiero Empleos de Analista de inversiones Empleos de Tesorero Empleos de Maestro Empleos de Jefe de comunicaciones Empleos de Jefe de finanzas Empleos de Analista de riesgos Empleos de Desarrollador de sistemas Empleos de Ejecutivo de marketing Empleos de Analista de operaciones Empleos de Gerente de finanzas Empleos de Auditor Empleos de Analista comercial Empleos de Ingeniero de aplicaciones Empleos de Arquitecto LinkedIn © 2026 Acerca de Accesibilidad Condiciones de uso Política de privacidad Política de cookies Política de copyright Política de marca Controles de invitados Pautas comunitarias العربية (árabe) বাংলা (bengalí) Čeština (checo) Dansk (danés) Deutsch (alemán) Ελληνικά (griego) English (inglés) Español (Spanish) لاررل (persa) Suomi (finlandés) Français (francés) हिंदी (hindi) Magyar (húngaro) Bahasa Indonesia (indonesio) Italiano (italiano) עברית (hebreo) 日本語 (japonés) 한국어 (coreano) मराठी (marati) Bahasa Malaysia (malayo) Nederlands (neerlandés) Norsk (noruego) ਪੰਜਾਬੀ (punyabí) Polski (polaco) Português (portugués) Română (rumano) Русский (ruso) Svenska (sueco) తెలుగు (telugu) ภาษาไทย (tailandés) Tagalog (tagalo) Türkçe (turco) Українська (ucraniano) Tiếng Việt (vietnamita) 简体中文 (chino simplificado) 正體中文 (chino tradicional) Idioma Aceptar y unirse a LinkedIn Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso , la Política de privacidad y la Política de cookies de LinkedIn. Inicia sesión para ver a quién conoces en Visma Iniciar sesión ¡Hola de nuevo! Email o teléfono Contraseña Mostrar ¿Has olvidado tu contraseña? Iniciar sesión o Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso , la Política de privacidad y la Política de cookies de LinkedIn. ¿Estás empezando a usar LinkedIn? Únete ahora o ¿Estás empezando a usar LinkedIn? Únete ahora Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso , la Política de privacidad y la Política de cookies de LinkedIn. | 2026-01-13T09:30:34 |
https://aws.amazon.com/ko/waf/ | Web Application Firewall - 웹 API 보호 - AWS WAF - AWS 메인 콘텐츠로 건너뛰기 Filter: 모두 English 문의하기 AWS Marketplace 지원 내 계정 검색 Filter: 모두 콘솔 로그인 계정 생성 AWS Web Application Firewall 개요 기능 요금 시작하기 리소스 더 많은 제품 › 보안, ID 및 규정 준수 › AWS WAF AWS 프리 티어를 통해 매월 1천만 건의 일반 봇 컨트롤 요청 제공 → AWS WAF 일반적인 익스플로잇으로부터 웹 애플리케이션 보호 AWS WAF 시작하기 AWS WAF의 이점 관리형 규칙으로 시간 단축 관리형 규칙으로 시간을 단축하여 애플리케이션을 구축하는 데 더 많은 시간을 할애할 수 있습니다. 봇 모니터링, 차단 또는 속도 제한 흔하고 널리 퍼진 봇을 보다 쉽게 모니터링하거나, 차단하거나 속도 제한할 수 있습니다. 보안 구성 단계 감소 보안 배포 구성의 복잡성과 단계를 최대 80%까지 줄이는 통합 인터페이스로 복잡한 보안 구성을 가속화합니다. 중앙 집중화되고 유용한 가시성 포괄적인 단일 인터페이스는 핵심 보안 기능과 전문화된 파트너 보호 기능을 결합하여, 보안과 관련한 가시성과 제어 능력을 개선합니다. 이 통합 접근 방식은 보안 데이터에서 유용한 인사이트를 도출하여 운영상의 마찰을 없애고 위험 대응을 가속화합니다. 보안 태세 강화 사전 구성된 보호 팩은 AWS의 보안 전문성을 활용하여 특정 산업 분야와 워크로드 유형(예: API, PHP 애플리케이션, 웹 서비스)에 적합한 즉각적인 보호 템플릿을 제공합니다. 이러한 템플릿은 수준 높은 배포 전문성을 갖추지 못한 고객이라도 최신 기술을 활용하여 보안을 보장할 수 있도록 지속적으로 최적화됩니다. 전반적인 보안 태세를 강화하기 위한 지속적인 보안 권장 사항을 얻으세요. AWS WAF를 사용해야 하는 이유는 무엇인가요? AWS WAF를 사용하면 SQL 인젝션 또는 크로스 사이트 스크립팅(XSS)과 같은 일반적인 공격 패턴을 차단하는 보안 규칙을 생성할 수 있습니다. 재생 사용 사례 웹 트래픽 필터링 IP 주소, HTTP 헤더 및 본문, 사용자 지정 URI와 같은 조건을 기준으로 웹 요청을 필터링하는 규칙을 생성합니다. 규칙 생성에 대해 자세히 알아보기 계정 탈취 사기 방지 침해된 자격 증명을 사용한 사용자 계정 무단 액세스를 방지하기 위해 애플리케이션의 로그인 페이지를 모니터링합니다. 사기 방지에 대해 자세히 알아보기 자동 레이어 7 DDoS 차단 애플리케이션 레이어(레이어 7)의 분산 서비스 거부(DDoS) 이벤트를 지속적으로 모니터링하고 몇 초 만에 자동으로 해결하도록 설계되었습니다. 신속한 보안 구현 고객의 니즈에 맞추어 사전 구성된 보안 기본 설정을 활성화하는 단일 페이지 인터페이스를 통한 간소화된 안내형 온보딩 설정 기능을 사용하여 리스크 없이 새 애플리케이션을 실행할 수 있습니다. 보안 태세 강화 전문가가 엄선한 규칙 팩, 통합 가시성, 지속적인 권장 사항을 통해, 보안 태세를 최적화할 수 있는 즉각적인 보호 환경을 제공합니다. AWS WAF 시작하기 AWS WAF 시작하기 AWS WAF 살펴보기 전문가에게 문의 문의처 AWS 계정 생성 알아보기 AWS란 무엇인가요? 클라우드 컴퓨팅이란 무엇인가요? 에이전틱 AI란 무엇인가요? 클라우드 컴퓨팅 개념 허브 AWS 클라우드 보안 새로운 소식 블로그 보도 자료 리소스 시작하기 교육 AWS Trust Center AWS Solutions Library 아키텍처 센터 제품 및 기술 관련 FAQ 애널리스트 보고서 AWS 파트너 개발자 빌더 센터 SDK 및 도구 AWS에서의 .NET AWS에서의 Python AWS에서의 Java AWS 상의 PHP AWS 상의 JavaScript 도움말 AWS에 문의 지원 티켓 제출 AWS re:Post 지식 센터 AWS Support 개요 전문가의 도움 받기 AWS 접근성 법적 고지 English 맨 위로 이동 Amazon은 기회 균등을 보장하는 기업입니다(소수/여성/장애/재향 군인/성 정체성/성적 지향/나이). x facebook linkedin instagram twitch youtube podcasts email 개인정보 처리방침 사이트 이용 약관 쿠키 기본 설정 © 2026, Amazon Web Services, Inc. 또는 자회사. All rights reserved. | 2026-01-13T09:30:34 |
https://id-id.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fawscommunity-asean%252Fcountermeasure-against-cve-2021-44228-with-aws-waf-4n3d%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026 | 2026-01-13T09:30:34 |
https://hackmd.io/changelog?utm_source=blog&utm_medium=Changelog-article#2025-09-23 | The HackMD Blog: Changelog Blog Product Company Changelog Education Sign in Sign in Get HackMD free Changelog Stay up to date on everything we ship. Sep 23, 2025 Improved Tag Management Organize your notes faster than ever. You can now create, rename, and delete tags directly from the Overview sidebar. Select multiple notes to add or remove tags in a single action, streamlining how you categorize knowledge. Sep 4, 2025 Profile Overhaul: Pin Notes, Categories & Connections We’ve completely overhauled profiles. Showcase your best work by pinning notes, organize content with categories, and add your social links (Email, Telegram, Discord, X). Improved sharing helps your knowledge reach a wider audience. Aug 5, 2025 Cite Paragraphs, Stay Connected Highlight great ideas and give credit easily. With Paragraph Citation , just paste a paragraph link and choose Citation to add a quote and an automatic footnote with the source. When others cite your note, you can discover who’s building on your work through citation cards . It’s a simple way to connect thoughts and help knowledge spread and grow. Jul 8, 2025 Use Guided Comments to Spark Better Feedback Comments are great—but sometimes visitors just need a little prompt. With Guided Comments, you can add a custom prompt and quick-reply options to spark better feedback. When someone clicks your avatar, they’ll see your prompt and can jump right into the conversation—no pressure, just a gentle invitation to engage. 1 2 3 11 Build together with the ultimate Markdown editor. Learning Features Tutorial book Resources Blog Changelog Enterprise Pricing Company About Press Kit Trust Center Terms of use Privacy policy English 中文 日本語 © 2026 HackMD. All Rights Reserved. | 2026-01-13T09:30:34 |
https://www.php.net/session-regenerate-id | PHP: session_regenerate_id - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_register_shutdown » « session_name PHP Manual Function Reference Session Extensions Sessions Session Functions Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_regenerate_id (PHP 4 >= 4.3.2, PHP 5, PHP 7, PHP 8) session_regenerate_id — Update the current session id with a newly generated one Description session_regenerate_id ( bool $delete_old_session = false ): bool session_regenerate_id() will replace the current session id with a new one, and keep the current session information. When session.use_trans_sid is enabled, output must be started after session_regenerate_id() call. Otherwise, old session ID is used. Warning Currently, session_regenerate_id does not handle an unstable network well, e.g. Mobile and WiFi network. Therefore, you may experience a lost session by calling session_regenerate_id. You should not destroy old session data immediately, but should use destroy time-stamp and control access to old session ID. Otherwise, concurrent access to page may result in inconsistent state, or you may have lost session, or it may cause client (browser) side race condition and may create many session ID needlessly. Immediate session data deletion disables session hijack attack detection and prevention also. Parameters delete_old_session Whether to delete the old associated session file or not. You should not delete old session if you need to avoid races caused by deletion or detect/avoid session hijack attacks. Return Values Returns true on success or false on failure. Examples Example #1 A session_regenerate_id() example <?php // NOTE: This code is not fully working code, but an example! session_start (); // Check destroyed time-stamp if (isset( $_SESSION [ 'destroyed' ]) && $_SESSION [ 'destroyed' ] < time () - 300 ) { // Should not happen usually. This could be attack or due to unstable network. // Remove all authentication status of this users session. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } $old_sessionid = session_id (); // Set destroyed timestamp $_SESSION [ 'destroyed' ] = time (); // session_regenerate_id() saves old session data // Simply calling session_regenerate_id() may result in lost session, etc. // See next example. session_regenerate_id (); // New session does not need destroyed timestamp unset( $_SESSION [ 'destroyed' ]); $new_sessionid = session_id (); echo "Old Session: $old_sessionid <br />" ; echo "New Session: $new_sessionid <br />" ; print_r ( $_SESSION ); ?> Current session module does not handle unstable network well. You should manage session ID to avoid lost session by session_regenerate_id. Example #2 Avoiding lost session by session_regenerate_id() <?php // NOTE: This code is not fully working code, but an example! // my_session_start() and my_session_regenerate_id() avoid lost sessions by // unstable network. In addition, this code may prevent exploiting stolen // session by attackers. function my_session_start () { session_start (); if (isset( $_SESSION [ 'destroyed' ])) { if ( $_SESSION [ 'destroyed' ] < time ()- 300 ) { // Should not happen usually. This could be attack or due to unstable network. // Remove all authentication status of this users session. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } if (isset( $_SESSION [ 'new_session_id' ])) { // Not fully expired yet. Could be lost cookie by unstable network. // Try again to set proper session ID cookie. // NOTE: Do not try to set session ID again if you would like to remove // authentication flag. session_commit (); session_id ( $_SESSION [ 'new_session_id' ]); // New session ID should exist session_start (); return; } } } function my_session_regenerate_id () { // New session ID is required to set proper session ID // when session ID is not set due to unstable network. $new_session_id = session_create_id (); $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit (); // Start session with new session ID session_id ( $new_session_id ); ini_set ( 'session.use_strict_mode' , 0 ); session_start (); ini_set ( 'session.use_strict_mode' , 1 ); // New session does not need them unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> See Also session_id() - Get and/or set the current session id session_create_id() - Create new session id session_start() - Start new or resume existing session session_destroy() - Destroys all data registered to a session session_reset() - Re-initialize session array with original values session_name() - Get and/or set the current session name Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 22 notes up down 42 tedivm at tedivm dot com ¶ 9 years ago I wrote the current top voted comment on this and wanted to add something. The existing code from my previous comment generates it's nonces in an insecure way- <?php $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); ?> Since "microtime" is predictable it makes brute forcing the nonce much easier. A better option would be something that utilizes randomness, such as- <?php bin2hex ( openssl_random_pseudo_bytes ( 32 )) ?> up down 42 tedivm at tedivm dot com ¶ 17 years ago I wrote the following code for a project I'm working on- it attempts to resolve the regenerate issue, as well as deal with a couple of other session related things. I tried to make it a little more generic and usable (for instance, in the full version it throws different types of exceptions for the different types of session issues), so hopefully someone might find it useful. <?php function regenerateSession ( $reload = false ) { // This token is used by forms to prevent cross site forgery attempts if(!isset( $_SESSION [ 'nonce' ]) || $reload ) $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); if(!isset( $_SESSION [ 'IPaddress' ]) || $reload ) $_SESSION [ 'IPaddress' ] = $_SERVER [ 'REMOTE_ADDR' ]; if(!isset( $_SESSION [ 'userAgent' ]) || $reload ) $_SESSION [ 'userAgent' ] = $_SERVER [ 'HTTP_USER_AGENT' ]; //$_SESSION['user_id'] = $this->user->getId(); // Set current session to expire in 1 minute $_SESSION [ 'OBSOLETE' ] = true ; $_SESSION [ 'EXPIRES' ] = time () + 60 ; // Create new session without destroying the old one session_regenerate_id ( false ); // Grab current session ID and close both sessions to allow other scripts to use them $newSession = session_id (); session_write_close (); // Set session ID to the new one, and start it back up again session_id ( $newSession ); session_start (); // Don't want this one to expire unset( $_SESSION [ 'OBSOLETE' ]); unset( $_SESSION [ 'EXPIRES' ]); } function checkSession () { try{ if( $_SESSION [ 'OBSOLETE' ] && ( $_SESSION [ 'EXPIRES' ] < time ())) throw new Exception ( 'Attempt to use expired session.' ); if(! is_numeric ( $_SESSION [ 'user_id' ])) throw new Exception ( 'No session started.' ); if( $_SESSION [ 'IPaddress' ] != $_SERVER [ 'REMOTE_ADDR' ]) throw new Exception ( 'IP Address mixmatch (possible session hijacking attempt).' ); if( $_SESSION [ 'userAgent' ] != $_SERVER [ 'HTTP_USER_AGENT' ]) throw new Exception ( 'Useragent mixmatch (possible session hijacking attempt).' ); if(! $this -> loadUser ( $_SESSION [ 'user_id' ])) throw new Exception ( 'Attempted to log in user that does not exist with ID: ' . $_SESSION [ 'user_id' ]); if(! $_SESSION [ 'OBSOLETE' ] && mt_rand ( 1 , 100 ) == 1 ) { $this -> regenerateSession (); } return true ; }catch( Exception $e ){ return false ; } } ?> up down 3 Rumour ¶ 2 years ago The code example provided of my_session_regenerate_id() DOES NOT work and DESTROYS all session variables. Plus the second ini_set gives an error. The code for regenerating (only that part, the rest seems fine) should simply be this: <?php function my_session_regenerate_id () { $new_session_id = session_create_id (); // backup session variables $keepSession = $_SESSION ; // add info for users with bad connection not receiving the new session id $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit () ; // Start session with new session ID ini_set ( 'session.use_strict_mode' , 0 ); session_id ( $new_session_id ); session_start (); $_SESSION = $keepSession ; } ?> up down 13 ei dot rik dot ops dot tad at gmail dot com ¶ 9 years ago In PHP 5.6 (and probably older versions), session_regenerate_id(true) do not trigger a read() call to the session handler for the new session id. In PHP 7, read() is triggered during session_regenerate_id(true). Nice to know when working with custom session handlers. up down 8 gr at gr5 dot org ¶ 14 years ago If you are trying to maintain 2 active sessions don't use session_regenerate_id(). Especially if the first session is closed and it's time to open the second. Because the session id is cached you also have to explicitly set it the second time. <?php session_name ( 'PHPSESSID' ); // redundant - here for clarity session_start (); // ...do stuff session_write_close (); // now switch to session 2... session_name ( 'PHPSESSID_2' ); if (isset( $_COOKIE [ 'phpsessid_2' ])) session_id ( $_COOKIE [ 'phpsessid_2' ]); // not doing this will simply reopen the first session again else session_id ( sha1 ( mt_rand ()); // dont use session_regenerate_id() here. Not creating a new id will create two cookies with same session id and same session variables session_start (); // ... do stuff with session 2 session_write_close (); ?> up down 13 ross at kndr dot org ¶ 21 years ago In a previous note, php at 5mm de describes how to prevent session hijacking by ensuring that the session id provided matches the HTTP_USER_AGENT and REMOTE_ADDR fields that were present when the session id was first issued. It should be noted that HTTP_USER_AGENT is supplied by the client, and so can be easily modified by a malicious user. Also, the client IP addresses can be spoofed, although that's a bit more difficult. Care should be taken when relying on the session for authentication. up down 4 babel at nosqamplease sympatico ca ¶ 21 years ago To add to php at 5mm de's comments: If the session is held over https, it's even better to save the client's cert or ssl session id instead of the hostname or ip, as it's proxy-transparent and more secure. up down 10 spmtrap at yahoo dot com ¶ 13 years ago `session_regenerate_id` sends a new cookie but doesn't overwrite the value stored in `$_COOKIE`. After calling `session_destroy`, the open session ID is discarded, so simply restarting the session with `session_start` (as done in Ben Johnson's code) will re-open the original, though now empty, session for the current request (subsequent requests will use the new session ID). Instead of `session_destroy`+`session_start`, use the `$delete_old_session` parameter to `session_regenerate_id` to delete the previous session data. <?php session_start (); /* Create a new session, deleting the previous session data. */ session_regenerate_id ( TRUE ); /* erase data carried over from previous session */ $_SESSION =array(); ?> To start a new session and leave the old untouched, simply leave out the argument to `session_regenerate_id`. up down 6 php at cny dot de ¶ 21 years ago Also note that REMOTE_ADDR may change on every request if the user comes through a proxy farm. Most AOL-users do. up down 2 k-gun !! mail ¶ 9 years ago Document example is wrong with usage of "session.use_strict_mode" according to RFC (says: "warning error for session_id() when use_strice_mode=1" on https://wiki.php.net/rfc/strict_sessions ). So, this directive affects "session_id()" not "session_start()". So usage must be like this; <?php // first set ini ini_set ( 'session.use_strict_mode' , '0' ); // and session_id ( $sid ); // then // maybe run this: ini_restore('session.use_strict_mode'); // then go on... ?> Refs (ctrl+f & use_strict_mode); https://wiki.php.net/rfc/strict_sessions https://wiki.php.net/rfc/session-create-id http://php.net/manual/en/function.session-id.php#119997 up down 3 madsen at sjovedyr.dk ¶ 22 years ago I had problems with a proxy changing a visitors session_id-cookie, so he'd get a LOT of errors when visiting my site. I handled the bogus session-id's like this. (Note: It only works in versions > 4.3.2.) <?php // Start a session and suppress error-messages. @ session_start (); // Catch bogus session-id's. if (! preg_match ( "/^[0-9a-z]*$/i" , session_id ())) { // Output a warning about the messed up session-id. $error -> handleError ( "WARN" , "Your session id is messed up, you might not be able to use some features on this site." ); // Generate a fresh session-id. session_regenerate_id (); } // Site contents. ?> Hope someone can use it. up down 1 Nicolas dot Chachereau at Infomaniak dot ch ¶ 20 years ago Session_destroy() does not only destroy the data associated with the current session_id (i.e. the file if you use the default session save handler), but also the session itself: if you call session_destroy() and then session_regenerate_id(), it will return false, and session_id() won't return anything. In order to manipulate a session after destroying it, you need to restart it. So in fact, the code mentionned by chris won't work. If you want to destroy the file associated with the old session_id, try the following: <?php session_start (); $old_sessid = session_id (); session_regenerate_id (); $new_sessid = session_id (); session_id ( $old_sessid ); session_destroy (); //If you don't copy the $_SESSION array, you won't be able to use the data associated with the old session id. $old_session = $_SESSION ; session_id ( $new_sessid ); session_start (); $_SESSION = $old_session ; //... ?> Note: this technique will send 3 Set-Cookie headers (one on each session_start() and one on session_regenerate_id()). I don't think this is a problem, but if it appears to be one, you could either leave it alone and wait for the garbage collector to catch the file associated with the old session, or try to delete the file with unlink(). up down 1 soapergem at gmail dot com ¶ 17 years ago This can be a very dangerous function if you're not careful about how you handle things, because even though it generates a whole new set of session data, it keeps the old data "open" until the script terminates, locking out any other scripts trying to run concurrently with the old session id. Recently I came across a situation where I wanted to explicitly pass in a session ID, copy the data from that session into a *new* session, and then continue operating under that new session, thereby allowing other scripts to use the old one concurrently. But I quickly found that these "other scripts" would not execute until the first script finished--even though it had already started a new session--because it kept the old session open. So if you're trying to copy over session data to a new session to free up the old session for continued, concurrent use, here's some code to ensure nobody's feet get stepped on: <?php // get session id of an existing session $sid = $_GET [ 'sid' ]; // start the old session to retrieve $_SESSION data session_id ( $sid ); session_start (); // start a new session; this copies the $_SESSION data over session_regenerate_id (); // hang on to the new session id $sid = session_id (); // close the old and new sessions session_write_close (); // re-open the new session session_id ( $sid ); session_start (); /* main code here */ ?> This could probably be encapsulated into a function with one parameter as well to save space if it was a repeated thing. up down 0 primenetworkzx at gmail dot com ¶ 17 years ago If you are storing your session data in a database you have to manually update the session_id in the database. The session_set_save_handler() will not do it for you. function UpdateSessID() { $old_sess_id = session_id(); session_regenerate_id(false); $new_sess_id = session_id(); $query = "UPDATE `session_table` SET `session_id` = '$new_sess_id' WHERE session_id = '$old_sess_id'"; mysql_query($query); } Be sure to set session_regenerate_id() to FALSE since it's not really necessary to delete the whole record from MySQL and add it again. That's unnecessary overhead. Only changing the id matters. up down 0 dyer85 at gmail dot com ¶ 20 years ago There could be a potential problem with elger at NOSPAM dot yellowbee dot nl's a few posts below. In the code, was used the REQUEST_URI server variable, which, in some cases might already contain the query string. Therefore, always apending '?whatever=foo' would occasionally cause the script to malfunction. I suggest using PHP_SELF, which will not contain the query string after the file. up down -2 mikebranttx at gmail dot com ¶ 8 years ago Note that in current PHP 7.2 nightly builds example #2 above will not work as shown. You will get following error upon trying to turn strict mode back on after session_start(): "ini_set(): A session is active. You cannot change the session module's ini settings at this time" I suppose this means that for any session where you perform session ID regeneration or session ID forwarding (from a session for which a recent session ID regeneration was performed to the new session ID). That you will just have to live with strict mode being disabled for the remainder of that active session. I don't know that this is really a security concern so long as you are following a single-session per request design (i.e. you are not working with multiple concurrent sessions). up down -2 chris at knowledge dot tee-vee ¶ 20 years ago licp - no, session_regenerate_id() does not destroy any saved session data. elger, I prefer the following order [code] // populate $_SESSION with any previously saved session data for the current session_id session_start(); ... // delete any saved data associated with current session_id, $_SESSION is not changed session_destroy(); // change session_id, $_SESSION not altered session_regenerate_id(); ... // save any $_SESSION data under the current session_id session_close(); [/code] up down -1 antomsa at hotmail dot it ¶ 4 years ago <?php function my_session_regenerate_id () { ... session_start (); ... unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Within my_session_regenerate_id(), unset($_SESSION['destroyed']) and unset($_SESSION['new_session_id']) are useless because session_start() will open an empty session. They would be needed if built-in session_regenerate_id() was called. up down -4 kgm_india at yahoo dot co dot in ¶ 12 years ago as far as I have understood reading this online notes, session_name() is the name which is identified as session a through the cookies or http links. session_id is like a transaction within a session_name() and one session_name may have many session_id each session_id has the corresponding data stored. session_id are used in read and write callback under a session_name whatever it is, first call the session_name(), then call session_id () and then call start_session() start_session will open the session_name, then check the session_id called before and use it in the read or write call back for storing or retrieving data calling start_session() without session_name or session_id will use the default session_name and the default session_id in that order I hope if the order is followed there should not be any problems. do not call session_name or session_id after start_session(), if you are specific on using them. thank you for others note. up down -5 raido dot aasoja at gmail dot com ¶ 15 years ago A note on lost sessions and trying to fix it with session_regenerate_id: Make sure that you're not trying to push SimpleXML object to the session. It just won't go without first converting it to array. :) up down -3 sopel ¶ 20 years ago for php 5.1> user probably worth visiting is http://ilia.ws/archives/47-session_regenerate_id-Improvement.html up down -4 Alamin ¶ 7 years ago In the second example provided by php.net, should it call my_session_start inside the session regenerate method instead of directly calling session_start? I think it is an error. ＋ add a note Session Functions session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://pt-br.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2keGOX2gxggubPvbD2U4v7iuDC9S3X2Lk7QEf_zG6UCPFlqRgkB8gDW-EZJfw1fiHskSqvBHeZQITabHORPi6bmhZQB9HgmigfedLFjaYt-gvk5RTqrih_kcyIODnVVuMY0a6Vs1-agSJ_ | Facebook Facebook Email ou telefone Senha Esqueceu a conta? Criar nova conta Você está bloqueado temporariamente Você está bloqueado temporariamente Parece que você estava usando este recurso de forma indevida. Bloqueamos temporariamente sua capacidade de usar o recurso. Back Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Français (France) Deutsch Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Configurações Registro de atividades Meta © 2026 | 2026-01-13T09:30:34 |
https://www.iso.org/es/perspectivas/lista-filtrada-inteligencia-artificial | ISO - Inteligencia artificial Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Inteligencia artificial Inteligencia artificial: qué es, cómo funciona y por qué es importante Para quienes no están familiarizados con la informática, puede resultar abrumador intentar comprender las múltiples facetas de la inteligencia artificial y sus implicaciones. En este artículo, esclarecemos qué es la inteligencia artificial, cómo funciona, la diferencia entre aprendizaje automático, aprendizaje … Últimos artículos La base de las redes neuronales: desentrañamos el código Desvelamos los secretos del procesamiento del lenguaje natural Construir una IA responsable: cómo gestionar el debate ético sobre la IA ¿Qué es la inteligencia artificial (IA)? Aprendizaje automático (AA): todo lo que hay que saber Aprendizaje profundo: los mecanismos de la magia Inteligencia artificial: qué es, cómo funciona y por qué es importante Cargar más Suscríbase para recibir actualizaciones por correo electrónico ¡Manténgase al día sobre la inteligencia artificial y las normas relacionadas! Website Suscribirse * ¡Ya casi está! Sólo le falta un paso para unirse a la lista de suscriptores de ISO. Confirme su suscripción haciendo clic en el correo electrónico que acabamos de enviarle. No estará registrado hasta que confirme su suscripción. Si no encuentra el correo electrónico, compruebe su carpeta de correo no deseado y/o la pestaña de promociones (si utiliza Gmail). * Boletín de noticias en inglés Para saber cómo se utilizarán sus datos, consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Cómo se utilizarán sus datos Consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Perspectivas y actualidad Perspectivas Inteligencia artificial Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://www.php.net/manual/fr/function.session-regenerate-id.php | PHP: session_regenerate_id - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_register_shutdown » « session_name Manuel PHP Référence des fonctions Extensions sur les Sessions Sessions Fonctions Session Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_regenerate_id (PHP 4 >= 4.3.2, PHP 5, PHP 7, PHP 8) session_regenerate_id — Remplace l'identifiant de session courant par un nouveau Description session_regenerate_id ( bool $delete_old_session = false ): bool session_regenerate_id() va remplacer l'identifiant de session courant par un nouveau, généré automatiquement, tout en conservant les valeurs de session. Lorsque l'option session.use_trans_sid est active, la sortie pour affichage doit commencer après l'appel à la fonction session_regenerate_id() . Sinon, l'ancien ID de session sera utilisé. Avertissement Actuellement, session_regenerate_id ne gère pas bien un réseau instable. Par ex. réseau mobile et WiFi. Par conséquent, vous pouvez rencontrer une perte de session en appelant session_regenerate_id. Vous ne devez pas détruire les anciennes données de session immédiatement, mais devez utiliser l'horodatage de destruction et contrôler l'accès à l'ancien ID de session. Sinon, l'accès simultané à la page peut entraîner un état incohérent, ou vous avez peut-être perdu la session, ou il peut provoquer un accès concurrent côté client (navigateur) et peut créer de nombreux ID de session inutilement. La suppression immédiate de données de session désactive également la détection et la prévention d'attaque de détournement de session. Liste de paramètres delete_old_session Si l'on doit effacer l'ancien fichier de session associé ou pas. Vous ne devez pas supprimer l'ancienne session si vous avez besoin d'éviter les accès concurrents causés par la suppression ou de détecter/éviter les attaques de détournement de session. Valeurs de retour Cette fonction retourne true en cas de succès ou false si une erreur survient. Exemples Exemple #1 Exemple avec session_regenerate_id() <?php // Note: ce code ne fonctionne pas complètement, c'est un exemple! session_start (); // Vérifier l'horodatage de destruction if (isset( $_SESSION [ 'destroyed' ]) && $_SESSION [ 'destroyed' ] < time () - 300 ) { // Ne devrait pas se produire habituellement. Cela pourrait être une attaque // ou en raison d'un réseau instable. Supprimez tout l'état d'authentification // de cette session utilisateurs. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } $old_sessionid = session_id (); // Définir l'horodatage de déstruction $_SESSION [ 'destroyed' ] = time (); // session_regenerate_id () enregistre les anciennes données de session // Il suffit d'appeler session_regenerate_id() peut entraîner la perte de session, etc. // Voir l'exemple suivant. session_regenerate_id (); // La nouvelle session n'a pas besoin du timestamp de destruction unset( $_SESSION [ 'destroyed' ]); $new_sessionid = session_id (); echo "Ancienne Session: $old_sessionid <br />" ; echo "Nouvelle Session: $new_sessionid <br />" ; print_r ( $_SESSION ); ?> Le module de session actuel ne gère pas bien le réseau instable. Vous devez gérer l'ID de session pour éviter la perte de session par session_regenerate_id. Exemple #2 Eviter la perte de session par session_regenerate_id() <?php // Note: ce code ne fonctionne pas complètement, c'est un exemple! // my_session_start() et my_session_regenerate_id() évitent les sessions perdues // par le réseau instable. En outre, ce code peut empêcher l'exploitation de // session volée par les attaquants. function my_session_start () { session_start (); if (isset( $_SESSION [ 'destroyed' ])) { if ( $_SESSION [ 'destroyed' ] < time ()- 300 ) { // Ne devrait pas se produire habituellement. Cela pourrait être une // attaque ou en raison d'un réseau instable. Supprimez tout l'état // d'authentification de cette session utilisateurs. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } if (isset( $_SESSION [ 'new_session_id' ])) { // Pas encore complètement expiré. Pourrait être perdu cookie par réseau instable. // Essayez à nouveau de définir le cookie d'ID de session approprié. // Remarque: n'essayez pas de redéfinir l'ID de session si vous // souhaitez supprimer l'état d'authentification. session_commit (); session_id ( $_SESSION [ 'new_session_id' ]); // Nouvel ID de session doit exister session_start (); return; } } } function my_session_regenerate_id () { // Le nouvel ID de session est requis pour définir l'ID de session approprié // lorsque l'ID de session n'est pas défini en raison d'un réseau instable. $new_session_id = session_create_id (); $_SESSION [ 'new_session_id' ] = $new_session_id ; // Définie le timestamp de destruction $_SESSION [ 'destroyed' ] = time (); // Ecrit et ferme la session courante session_commit (); // Démarre la session avec un nouvel ID session_id ( $new_session_id ); ini_set ( 'session.use_strict_mode' , 0 ); session_start (); ini_set ( 'session.use_strict_mode' , 1 ); // La nouvelle session n'en a pas besoin unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Voir aussi session_id() - Lit et/ou modifie l'identifiant courant de session session_create_id() - Créer un nouvel ID de session session_start() - Démarre une nouvelle session ou reprend une session existante session_destroy() - Détruit une session session_reset() - Réinitialise le tableau de session avec les valeurs originales session_name() - Lit et/ou modifie le nom de la session Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 22 notes up down 42 tedivm at tedivm dot com ¶ 9 years ago I wrote the current top voted comment on this and wanted to add something. The existing code from my previous comment generates it's nonces in an insecure way- <?php $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); ?> Since "microtime" is predictable it makes brute forcing the nonce much easier. A better option would be something that utilizes randomness, such as- <?php bin2hex ( openssl_random_pseudo_bytes ( 32 )) ?> up down 42 tedivm at tedivm dot com ¶ 17 years ago I wrote the following code for a project I'm working on- it attempts to resolve the regenerate issue, as well as deal with a couple of other session related things. I tried to make it a little more generic and usable (for instance, in the full version it throws different types of exceptions for the different types of session issues), so hopefully someone might find it useful. <?php function regenerateSession ( $reload = false ) { // This token is used by forms to prevent cross site forgery attempts if(!isset( $_SESSION [ 'nonce' ]) || $reload ) $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); if(!isset( $_SESSION [ 'IPaddress' ]) || $reload ) $_SESSION [ 'IPaddress' ] = $_SERVER [ 'REMOTE_ADDR' ]; if(!isset( $_SESSION [ 'userAgent' ]) || $reload ) $_SESSION [ 'userAgent' ] = $_SERVER [ 'HTTP_USER_AGENT' ]; //$_SESSION['user_id'] = $this->user->getId(); // Set current session to expire in 1 minute $_SESSION [ 'OBSOLETE' ] = true ; $_SESSION [ 'EXPIRES' ] = time () + 60 ; // Create new session without destroying the old one session_regenerate_id ( false ); // Grab current session ID and close both sessions to allow other scripts to use them $newSession = session_id (); session_write_close (); // Set session ID to the new one, and start it back up again session_id ( $newSession ); session_start (); // Don't want this one to expire unset( $_SESSION [ 'OBSOLETE' ]); unset( $_SESSION [ 'EXPIRES' ]); } function checkSession () { try{ if( $_SESSION [ 'OBSOLETE' ] && ( $_SESSION [ 'EXPIRES' ] < time ())) throw new Exception ( 'Attempt to use expired session.' ); if(! is_numeric ( $_SESSION [ 'user_id' ])) throw new Exception ( 'No session started.' ); if( $_SESSION [ 'IPaddress' ] != $_SERVER [ 'REMOTE_ADDR' ]) throw new Exception ( 'IP Address mixmatch (possible session hijacking attempt).' ); if( $_SESSION [ 'userAgent' ] != $_SERVER [ 'HTTP_USER_AGENT' ]) throw new Exception ( 'Useragent mixmatch (possible session hijacking attempt).' ); if(! $this -> loadUser ( $_SESSION [ 'user_id' ])) throw new Exception ( 'Attempted to log in user that does not exist with ID: ' . $_SESSION [ 'user_id' ]); if(! $_SESSION [ 'OBSOLETE' ] && mt_rand ( 1 , 100 ) == 1 ) { $this -> regenerateSession (); } return true ; }catch( Exception $e ){ return false ; } } ?> up down 3 Rumour ¶ 2 years ago The code example provided of my_session_regenerate_id() DOES NOT work and DESTROYS all session variables. Plus the second ini_set gives an error. The code for regenerating (only that part, the rest seems fine) should simply be this: <?php function my_session_regenerate_id () { $new_session_id = session_create_id (); // backup session variables $keepSession = $_SESSION ; // add info for users with bad connection not receiving the new session id $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit () ; // Start session with new session ID ini_set ( 'session.use_strict_mode' , 0 ); session_id ( $new_session_id ); session_start (); $_SESSION = $keepSession ; } ?> up down 13 ei dot rik dot ops dot tad at gmail dot com ¶ 9 years ago In PHP 5.6 (and probably older versions), session_regenerate_id(true) do not trigger a read() call to the session handler for the new session id. In PHP 7, read() is triggered during session_regenerate_id(true). Nice to know when working with custom session handlers. up down 8 gr at gr5 dot org ¶ 14 years ago If you are trying to maintain 2 active sessions don't use session_regenerate_id(). Especially if the first session is closed and it's time to open the second. Because the session id is cached you also have to explicitly set it the second time. <?php session_name ( 'PHPSESSID' ); // redundant - here for clarity session_start (); // ...do stuff session_write_close (); // now switch to session 2... session_name ( 'PHPSESSID_2' ); if (isset( $_COOKIE [ 'phpsessid_2' ])) session_id ( $_COOKIE [ 'phpsessid_2' ]); // not doing this will simply reopen the first session again else session_id ( sha1 ( mt_rand ()); // dont use session_regenerate_id() here. Not creating a new id will create two cookies with same session id and same session variables session_start (); // ... do stuff with session 2 session_write_close (); ?> up down 13 ross at kndr dot org ¶ 21 years ago In a previous note, php at 5mm de describes how to prevent session hijacking by ensuring that the session id provided matches the HTTP_USER_AGENT and REMOTE_ADDR fields that were present when the session id was first issued. It should be noted that HTTP_USER_AGENT is supplied by the client, and so can be easily modified by a malicious user. Also, the client IP addresses can be spoofed, although that's a bit more difficult. Care should be taken when relying on the session for authentication. up down 4 babel at nosqamplease sympatico ca ¶ 21 years ago To add to php at 5mm de's comments: If the session is held over https, it's even better to save the client's cert or ssl session id instead of the hostname or ip, as it's proxy-transparent and more secure. up down 10 spmtrap at yahoo dot com ¶ 13 years ago `session_regenerate_id` sends a new cookie but doesn't overwrite the value stored in `$_COOKIE`. After calling `session_destroy`, the open session ID is discarded, so simply restarting the session with `session_start` (as done in Ben Johnson's code) will re-open the original, though now empty, session for the current request (subsequent requests will use the new session ID). Instead of `session_destroy`+`session_start`, use the `$delete_old_session` parameter to `session_regenerate_id` to delete the previous session data. <?php session_start (); /* Create a new session, deleting the previous session data. */ session_regenerate_id ( TRUE ); /* erase data carried over from previous session */ $_SESSION =array(); ?> To start a new session and leave the old untouched, simply leave out the argument to `session_regenerate_id`. up down 6 php at cny dot de ¶ 21 years ago Also note that REMOTE_ADDR may change on every request if the user comes through a proxy farm. Most AOL-users do. up down 2 k-gun !! mail ¶ 9 years ago Document example is wrong with usage of "session.use_strict_mode" according to RFC (says: "warning error for session_id() when use_strice_mode=1" on https://wiki.php.net/rfc/strict_sessions ). So, this directive affects "session_id()" not "session_start()". So usage must be like this; <?php // first set ini ini_set ( 'session.use_strict_mode' , '0' ); // and session_id ( $sid ); // then // maybe run this: ini_restore('session.use_strict_mode'); // then go on... ?> Refs (ctrl+f & use_strict_mode); https://wiki.php.net/rfc/strict_sessions https://wiki.php.net/rfc/session-create-id http://php.net/manual/en/function.session-id.php#119997 up down 3 madsen at sjovedyr.dk ¶ 22 years ago I had problems with a proxy changing a visitors session_id-cookie, so he'd get a LOT of errors when visiting my site. I handled the bogus session-id's like this. (Note: It only works in versions > 4.3.2.) <?php // Start a session and suppress error-messages. @ session_start (); // Catch bogus session-id's. if (! preg_match ( "/^[0-9a-z]*$/i" , session_id ())) { // Output a warning about the messed up session-id. $error -> handleError ( "WARN" , "Your session id is messed up, you might not be able to use some features on this site." ); // Generate a fresh session-id. session_regenerate_id (); } // Site contents. ?> Hope someone can use it. up down 1 Nicolas dot Chachereau at Infomaniak dot ch ¶ 20 years ago Session_destroy() does not only destroy the data associated with the current session_id (i.e. the file if you use the default session save handler), but also the session itself: if you call session_destroy() and then session_regenerate_id(), it will return false, and session_id() won't return anything. In order to manipulate a session after destroying it, you need to restart it. So in fact, the code mentionned by chris won't work. If you want to destroy the file associated with the old session_id, try the following: <?php session_start (); $old_sessid = session_id (); session_regenerate_id (); $new_sessid = session_id (); session_id ( $old_sessid ); session_destroy (); //If you don't copy the $_SESSION array, you won't be able to use the data associated with the old session id. $old_session = $_SESSION ; session_id ( $new_sessid ); session_start (); $_SESSION = $old_session ; //... ?> Note: this technique will send 3 Set-Cookie headers (one on each session_start() and one on session_regenerate_id()). I don't think this is a problem, but if it appears to be one, you could either leave it alone and wait for the garbage collector to catch the file associated with the old session, or try to delete the file with unlink(). up down 1 soapergem at gmail dot com ¶ 17 years ago This can be a very dangerous function if you're not careful about how you handle things, because even though it generates a whole new set of session data, it keeps the old data "open" until the script terminates, locking out any other scripts trying to run concurrently with the old session id. Recently I came across a situation where I wanted to explicitly pass in a session ID, copy the data from that session into a *new* session, and then continue operating under that new session, thereby allowing other scripts to use the old one concurrently. But I quickly found that these "other scripts" would not execute until the first script finished--even though it had already started a new session--because it kept the old session open. So if you're trying to copy over session data to a new session to free up the old session for continued, concurrent use, here's some code to ensure nobody's feet get stepped on: <?php // get session id of an existing session $sid = $_GET [ 'sid' ]; // start the old session to retrieve $_SESSION data session_id ( $sid ); session_start (); // start a new session; this copies the $_SESSION data over session_regenerate_id (); // hang on to the new session id $sid = session_id (); // close the old and new sessions session_write_close (); // re-open the new session session_id ( $sid ); session_start (); /* main code here */ ?> This could probably be encapsulated into a function with one parameter as well to save space if it was a repeated thing. up down 0 primenetworkzx at gmail dot com ¶ 17 years ago If you are storing your session data in a database you have to manually update the session_id in the database. The session_set_save_handler() will not do it for you. function UpdateSessID() { $old_sess_id = session_id(); session_regenerate_id(false); $new_sess_id = session_id(); $query = "UPDATE `session_table` SET `session_id` = '$new_sess_id' WHERE session_id = '$old_sess_id'"; mysql_query($query); } Be sure to set session_regenerate_id() to FALSE since it's not really necessary to delete the whole record from MySQL and add it again. That's unnecessary overhead. Only changing the id matters. up down 0 dyer85 at gmail dot com ¶ 20 years ago There could be a potential problem with elger at NOSPAM dot yellowbee dot nl's a few posts below. In the code, was used the REQUEST_URI server variable, which, in some cases might already contain the query string. Therefore, always apending '?whatever=foo' would occasionally cause the script to malfunction. I suggest using PHP_SELF, which will not contain the query string after the file. up down -2 mikebranttx at gmail dot com ¶ 8 years ago Note that in current PHP 7.2 nightly builds example #2 above will not work as shown. You will get following error upon trying to turn strict mode back on after session_start(): "ini_set(): A session is active. You cannot change the session module's ini settings at this time" I suppose this means that for any session where you perform session ID regeneration or session ID forwarding (from a session for which a recent session ID regeneration was performed to the new session ID). That you will just have to live with strict mode being disabled for the remainder of that active session. I don't know that this is really a security concern so long as you are following a single-session per request design (i.e. you are not working with multiple concurrent sessions). up down -2 chris at knowledge dot tee-vee ¶ 20 years ago licp - no, session_regenerate_id() does not destroy any saved session data. elger, I prefer the following order [code] // populate $_SESSION with any previously saved session data for the current session_id session_start(); ... // delete any saved data associated with current session_id, $_SESSION is not changed session_destroy(); // change session_id, $_SESSION not altered session_regenerate_id(); ... // save any $_SESSION data under the current session_id session_close(); [/code] up down -1 antomsa at hotmail dot it ¶ 4 years ago <?php function my_session_regenerate_id () { ... session_start (); ... unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Within my_session_regenerate_id(), unset($_SESSION['destroyed']) and unset($_SESSION['new_session_id']) are useless because session_start() will open an empty session. They would be needed if built-in session_regenerate_id() was called. up down -4 kgm_india at yahoo dot co dot in ¶ 12 years ago as far as I have understood reading this online notes, session_name() is the name which is identified as session a through the cookies or http links. session_id is like a transaction within a session_name() and one session_name may have many session_id each session_id has the corresponding data stored. session_id are used in read and write callback under a session_name whatever it is, first call the session_name(), then call session_id () and then call start_session() start_session will open the session_name, then check the session_id called before and use it in the read or write call back for storing or retrieving data calling start_session() without session_name or session_id will use the default session_name and the default session_id in that order I hope if the order is followed there should not be any problems. do not call session_name or session_id after start_session(), if you are specific on using them. thank you for others note. up down -5 raido dot aasoja at gmail dot com ¶ 15 years ago A note on lost sessions and trying to fix it with session_regenerate_id: Make sure that you're not trying to push SimpleXML object to the session. It just won't go without first converting it to array. :) up down -3 sopel ¶ 20 years ago for php 5.1> user probably worth visiting is http://ilia.ws/archives/47-session_regenerate_id-Improvement.html up down -4 Alamin ¶ 7 years ago In the second example provided by php.net, should it call my_session_start inside the session regenerate method instead of directly calling session_start? I think it is an error. ＋ add a note Fonctions Session session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-permissions.html | Set up IAM permissions and roles for Lambda@Edge - Amazon CloudFront Set up IAM permissions and roles for Lambda@Edge - Amazon CloudFront Documentation Amazon CloudFront Developer Guide IAM permissions required to associate Lambda@Edge functions with CloudFront distributions Function execution role for service principals Service-linked roles for Lambda@Edge Set up IAM permissions and roles for Lambda@Edge To configure Lambda@Edge, you must have the following IAM permissions and roles for AWS Lambda: IAM permissions – These permissions allow you to create your Lambda function and associate it with your CloudFront distribution. A Lambda function execution role (IAM role) – The Lambda service principals assume this role to execute your function. Service-linked roles for Lambda@Edge – The service-linked roles allow specific AWS services to replicate Lambda functions to AWS Regions and to enable CloudWatch to use CloudFront log files. IAM permissions required to associate Lambda@Edge functions with CloudFront distributions In addition to the IAM permissions that you need for Lambda, you need the following permissions to associate Lambda functions with CloudFront distributions: lambda:GetFunction – Grants permission to get configuration information for your Lambda function and a presigned URL to download a .zip file that contains the function. lambda:EnableReplication* – Grants permission to the resource policy so that the Lambda replication service can get the function code and configuration. lambda:DisableReplication* – Grants permission to the resource policy so that the Lambda replication service can delete the function. Important You must add the asterisk ( * ) at the end of the lambda:EnableReplication * and lambda:DisableReplication * actions. For the resource, specify the ARN of the function version that you want to execute when a CloudFront event occurs, such as the following example: arn:aws:lambda:us-east-1:123456789012:function: TestFunction :2 iam:CreateServiceLinkedRole – Grants permission to create a service-linked role that Lambda@Edge uses to replicate Lambda functions in CloudFront. After you configure Lambda@Edge for the first time, the service-linked role is automatically created for you. You don't need to add this permission to other distributions that use Lambda@Edge. cloudfront:UpdateDistribution or cloudfront:CreateDistribution – Grants permission to update or create a distribution. For more information, see the following topics: Identity and Access Management for Amazon CloudFront Lambda resource access permissions in the AWS Lambda Developer Guide Function execution role for service principals You must create an IAM role that the lambda.amazonaws.com and edgelambda.amazonaws.com service principals can assume when they execute your function. Tip When you create your function in the Lambda console, you can choose to create a new execution role by using an AWS policy template. This step automatically adds the required Lambda@Edge permissions to execute your function. See Step 5 in the Tutorial: Creating a simple Lambda@Edge function . For more information about creating an IAM role manually, see Creating roles and attaching policies (console) in the IAM User Guide . Example: Role trust policy You can add this role under the Trust Relationship tab in the IAM console. Don't add this policy under the Permissions tab. JSON { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "lambda.amazonaws.com", "edgelambda.amazonaws.com" ] }, "Action": "sts:AssumeRole" } ] } For more information about the permissions that you need to grant to the execution role, see Lambda resource access permissions in the AWS Lambda Developer Guide . Notes By default, whenever a CloudFront event triggers a Lambda function, data is written to CloudWatch Logs. If you want to use these logs, the execution role needs permission to write data to CloudWatch Logs. You can use the predefined AWSLambdaBasicExecutionRole to grant permission to the execution role. For more information about CloudWatch Logs, see Edge function logs . If your Lambda function code accesses other AWS resources, such as reading an object from an S3 bucket, the execution role needs permission to perform that action. Service-linked roles for Lambda@Edge Lambda@Edge uses IAM service-linked roles . A service-linked role is a unique type of IAM role that is linked directly to a service. Service-linked roles are predefined by the service and include all of the permissions that the service requires to call other AWS services on your behalf. Lambda@Edge uses the following IAM service-linked roles: AWSServiceRoleForLambdaReplicator – Lambda@Edge uses this role to allow Lambda@Edge to replicate functions to AWS Regions. When you first add a Lambda@Edge trigger in CloudFront, a role named AWSServiceRoleForLambdaReplicator is created automatically to allow Lambda@Edge to replicate functions to AWS Regions. This role is required to use Lambda@Edge functions. The ARN for the AWSServiceRoleForLambdaReplicator role looks like the following example: arn:aws:iam::123456789012:role/aws-service-role/replicator.lambda.amazonaws.com/AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger – CloudFront uses this role to push log files into CloudWatch. You can use log files to debug Lambda@Edge validation errors. The AWSServiceRoleForCloudFrontLogger role is created automatically when you add Lambda@Edge function association to allow CloudFront to push Lambda@Edge error log files to CloudWatch. The ARN for the AWSServiceRoleForCloudFrontLogger role looks like this: arn:aws:iam::account_number:role/aws-service-role/logger.cloudfront.amazonaws.com/AWSServiceRoleForCloudFrontLogger A service-linked role makes setting up and using Lambda@Edge easier because you don’t have to manually add the necessary permissions. Lambda@Edge defines the permissions of its service-linked roles, and only Lambda@Edge can assume the roles. The defined permissions include the trust policy and the permissions policy. You can't attach the permissions policy to any other IAM entity. You must remove any associated CloudFront or Lambda@Edge resources before you can delete a service-linked role. This helps protect your Lambda@Edge resources so that you don't remove a service-linked role that is still required to access active resources. For more information about service-linked roles, see Service-linked roles for CloudFront . Service-linked role permissions for Lambda@Edge Lambda@Edge uses two service-linked roles, named AWSServiceRoleForLambdaReplicator and AWSServiceRoleForCloudFrontLogger . The following sections describe the permissions for each of these roles. Contents Service-linked role permissions for Lambda replicator Service-linked role permissions for CloudFront logger Service-linked role permissions for Lambda replicator This service-linked role allows Lambda to replicate Lambda@Edge functions to AWS Regions. The AWSServiceRoleForLambdaReplicator service-linked role trusts the replicator.lambda.amazonaws.com service to assume the role. The role permissions policy allows Lambda@Edge to complete the following actions on the specified resources: lambda:CreateFunction on arn:aws:lambda:*:*:function:* lambda:DeleteFunction on arn:aws:lambda:*:*:function:* lambda:DisableReplication on arn:aws:lambda:*:*:function:* iam:PassRole on all AWS resources cloudfront:ListDistributionsByLambdaFunction on all AWS resources Service-linked role permissions for CloudFront logger This service-linked role allows CloudFront to push log files into CloudWatch so that you can debug Lambda@Edge validation errors. The AWSServiceRoleForCloudFrontLogger service-linked role trusts the logger.cloudfront.amazonaws.com service to assume the role. The role permissions policy allows Lambda@Edge to complete the following actions on the specified arn:aws:logs:*:*:log-group:/aws/cloudfront/* resource: logs:CreateLogGroup logs:CreateLogStream logs:PutLogEvents You must configure permissions to allow an IAM entity (such as a user, group, or role) to delete the Lambda@Edge service-linked roles. For more information, see Service-linked role permissions in the IAM User Guide . Creating service-linked roles for Lambda@Edge You don’t typically manually create the service-linked roles for Lambda@Edge. The service creates the roles for you automatically in the following scenarios: When you first create a trigger, the service creates the AWSServiceRoleForLambdaReplicator role (if it doesn’t already exist). This role allows Lambda to replicate Lambda@Edge functions to AWS Regions. If you delete the service-linked role, the role will be created again when you add a new trigger for Lambda@Edge in a distribution. When you update or create a CloudFront distribution that has a Lambda@Edge association, the service creates the AWSServiceRoleForCloudFrontLogger role (if the role doesn’t already exist). This role allows CloudFront to push your log files to CloudWatch. If you delete the service-linked role, the role will be created again when you update or create a CloudFront distribution that has a Lambda@Edge association. To manually create these service-linked roles, you can run the following AWS Command Line Interface (AWS CLI) commands: To create the AWSServiceRoleForLambdaReplicator role Run the following command. aws iam create-service-linked-role --aws-service-name replicator.lambda.amazonaws.com To create the AWSServiceRoleForCloudFrontLogger role Run the following command. aws iam create-service-linked-role --aws-service-name logger.cloudfront.amazonaws.com Editing Lambda@Edge service-linked roles Lambda@Edge doesn't allow you to edit the AWSServiceRoleForLambdaReplicator or AWSServiceRoleForCloudFrontLogger service-linked roles. After the service has created a service-linked role, you can't change the name of the role because various entities might reference the role. However, you can use IAM to edit the role description. For more information, see Editing a service-linked role in the IAM User Guide . Supported AWS Regions for Lambda@Edge service-linked roles CloudFront supports using service-linked roles for Lambda@Edge in the following AWS Regions: US East (N. Virginia) – us-east-1 US East (Ohio) – us-east-2 US West (N. California) – us-west-1 US West (Oregon) – us-west-2 Asia Pacific (Mumbai) – ap-south-1 Asia Pacific (Seoul) – ap-northeast-2 Asia Pacific (Singapore) – ap-southeast-1 Asia Pacific (Sydney) – ap-southeast-2 Asia Pacific (Tokyo) – ap-northeast-1 Europe (Frankfurt) – eu-central-1 Europe (Ireland) – eu-west-1 Europe (London) – eu-west-2 South America (São Paulo) – sa-east-1 Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Tutorial: Basic Lambda@Edge function Write and create a Lambda@Edge function Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
https://pt-br.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0ODBxi9Ky_q5Zd-o4dYpnmHyfX6cU94o0TSebfXayTVSpJVZhsLNiaEOYJD4tF5NyHmlhcHvBZpujDEdp7WEIct_OsB2vtYxvgex9BobCz0QD-I7CT9qU5M2_9NMDpfEnKNwsIMtWszByH | Facebook Facebook Email ou telefone Senha Esqueceu a conta? Criar nova conta Você está bloqueado temporariamente Você está bloqueado temporariamente Parece que você estava usando este recurso de forma indevida. Bloqueamos temporariamente sua capacidade de usar o recurso. Back Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Français (France) Deutsch Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Configurações Registro de atividades Meta © 2026 | 2026-01-13T09:30:34 |
https://ja-jp.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fawscommunity-asean%252Fcountermeasure-against-cve-2021-44228-with-aws-waf-4n3d%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook メールアドレスまたは電話番号 パスワード アカウントを忘れた場合 新しいアカウントを作成 機能の一時停止 機能の一時停止 この機能の使用ペースが早過ぎるため、機能の使用が一時的にブロックされました。 Back 日本語 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) Português (Brasil) Français (France) Deutsch アカウント登録 ログイン Messenger Facebook Lite 動画 Meta Pay Metaストア Meta Quest Ray-Ban Meta Meta AI Meta AIのコンテンツをもっと見る Instagram Threads 投票情報センター プライバシーポリシー プライバシーセンター Facebookについて 広告を作成 ページを作成 開発者 採用情報 Cookie AdChoices 規約 ヘルプ 連絡先のアップロードと非ユーザー 設定 アクティビティログ Meta © 2026 | 2026-01-13T09:30:34 |
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1KY84hKm_-by-YRr4vpnWKQpQpwSlqcHtHuJaVKw1bW8wItTohGpLUCnyGOFaKEl24B0RlP8zqhkc8lgjUOBrHeD_3-x2x1wAeaDTMaMg12_UywdHBUwoulr3RtwamghKKTr5Z0_NPtXeL | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/docs/index.html | About — LLVM 18.1.8 documentation Navigation index next | LLVM Home | Documentation » About Documentation Getting Started/Tutorials User Guides Reference Getting Involved Contributing to LLVM Submitting Bug Reports Mailing Lists IRC Meetups and Social Events Additional Links FAQ Glossary Publications Github Repository This Page Show Source Quick search About ¶ Warning If you are using a released version of LLVM, see the download page to find your documentation. The LLVM compiler infrastructure supports a wide range of projects, from industrial strength compilers to specialized JIT applications to small research projects. Similarly, documentation is broken down into several high-level groupings targeted at different audiences: LLVM Design & Overview ¶ Several introductory papers and presentations. Introduction to the LLVM Compiler Presentation providing a users introduction to LLVM. Intro to LLVM A chapter from the book “The Architecture of Open Source Applications” that describes high-level design decisions that shaped LLVM. LLVM: A Compilation Framework for Lifelong Program Analysis & Transformation Design overview. LLVM: An Infrastructure for Multi-Stage Optimization More details (quite old now). Documentation ¶ Getting Started, How-tos, Developer Guides, and Tutorials. Getting Started/Tutorials For those new to the LLVM system. User Guides User guides and How-tos. Reference LLVM and API reference documentation. Discourse Migration Guide Guide for users to migrate to Discourse Community ¶ LLVM welcomes contributions of all kinds. To learn more, see the following articles: Getting Involved Development Process Forums & Mailing Lists Meetups and social events Community wide proposals Reporting a security issue How to report a security issue? Indices and tables ¶ Index Search Page Navigation index next | LLVM Home | Documentation » About © Copyright 2003-2024, LLVM Project. Last updated on 2024-06-19. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://hackmd.io/changelog?utm_source=blog&utm_medium=Changelog-article#2025-07-08 | The HackMD Blog: Changelog Blog Product Company Changelog Education Sign in Sign in Get HackMD free Changelog Stay up to date on everything we ship. Sep 23, 2025 Improved Tag Management Organize your notes faster than ever. You can now create, rename, and delete tags directly from the Overview sidebar. Select multiple notes to add or remove tags in a single action, streamlining how you categorize knowledge. Sep 4, 2025 Profile Overhaul: Pin Notes, Categories & Connections We’ve completely overhauled profiles. Showcase your best work by pinning notes, organize content with categories, and add your social links (Email, Telegram, Discord, X). Improved sharing helps your knowledge reach a wider audience. Aug 5, 2025 Cite Paragraphs, Stay Connected Highlight great ideas and give credit easily. With Paragraph Citation , just paste a paragraph link and choose Citation to add a quote and an automatic footnote with the source. When others cite your note, you can discover who’s building on your work through citation cards . It’s a simple way to connect thoughts and help knowledge spread and grow. Jul 8, 2025 Use Guided Comments to Spark Better Feedback Comments are great—but sometimes visitors just need a little prompt. With Guided Comments, you can add a custom prompt and quick-reply options to spark better feedback. When someone clicks your avatar, they’ll see your prompt and can jump right into the conversation—no pressure, just a gentle invitation to engage. 1 2 3 11 Build together with the ultimate Markdown editor. Learning Features Tutorial book Resources Blog Changelog Enterprise Pricing Company About Press Kit Trust Center Terms of use Privacy policy English 中文 日本語 © 2026 HackMD. All Rights Reserved. | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/configuration/buildfactories.html | 2.5.10. Build Factories — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.5.1. Configuring Buildbot 2.5.2. Global Configuration 2.5.3. Change Sources and Changes 2.5.4. Changes 2.5.5. Schedulers 2.5.6. Workers 2.5.7. Builder Configuration 2.5.8. Projects 2.5.9. Codebases 2.5.10. Build Factories 2.5.10.1. Defining a Build Factory 2.5.10.2. Dynamic Build Factories 2.5.10.3. Predefined Build Factories 2.5.11. Build Sets 2.5.12. Properties 2.5.13. Build Steps 2.5.14. Interlocks 2.5.15. Report Generators 2.5.16. Reporters 2.5.17. Web Server 2.5.18. Change Hooks 2.5.19. Custom Services 2.5.20. DbConfig 2.5.21. Configurators 2.5.22. Manhole 2.5.23. Multimaster 2.5.24. Multiple-Codebase Builds 2.5.25. Miscellaneous Configuration 2.5.26. Testing Utilities 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.5. Configuration 2.5.10. Build Factories View page source 2.5.10. Build Factories Each Builder is equipped with a build factory , which defines the steps used to perform a particular type of build. This factory is created in the configuration file, and attached to a Builder through the factory element of its dictionary. The steps used by these builds are defined in the next section, Build Steps . Note Build factories are used with builders, and are not added directly to the buildmaster configuration dictionary. Defining a Build Factory Dynamic Build Factories Predefined Build Factories 2.5.10.1. Defining a Build Factory A BuildFactory defines the steps that every build will follow. Think of it as a glorified script. For example, a build factory which consists of an SVN checkout followed by a make build would be configured as follows: from buildbot.plugins import util , steps f = util . BuildFactory () f . addStep ( steps . SVN ( repourl = "http://.." , mode = "incremental" )) f . addStep ( steps . Compile ( command = [ "make" , "build" ])) This factory would then be attached to one builder (or several, if desired): c [ 'builders' ] . append ( BuilderConfig ( name = 'quick' , workernames = [ 'bot1' , 'bot2' ], factory = f )) It is also possible to pass a list of steps into the BuildFactory when it is created. Using addStep is usually simpler, but there are cases where it is more convenient to create the list of steps ahead of time, perhaps using some Python tricks to generate the steps. from buildbot.plugins import steps , util all_steps = [ steps . CVS ( cvsroot = CVSROOT , cvsmodule = "project" , mode = "update" ), steps . Compile ( command = [ "make" , "build" ]), ] f = util . BuildFactory ( all_steps ) Finally, you can also add a sequence of steps all at once: f . addSteps ( all_steps ) Attributes The following attributes can be set on a build factory after it is created, e.g., f = util . BuildFactory () f . useProgress = False useProgress (defaults to True ): if True , the buildmaster keeps track of how long each step takes, so it can provide estimates of how long future builds will take. If builds are not expected to take a consistent amount of time (such as incremental builds in which a random set of files are recompiled or tested each time), this should be set to False to inhibit progress-tracking. workdir (defaults to ‘build’): workdir given to every build step created by this factory as default. The workdir can be overridden in a build step definition. The workdir can be renderable. The attribute will be used for constructing the workdir (worker base + builder builddir + workdir). 2.5.10.2. Dynamic Build Factories In some cases you may not know what commands to run until after you checkout the source tree. For those cases, you can dynamically add steps during a build from other steps. The Build object provides 2 functions to do this: addStepsAfterCurrentStep(self, step_factories) This adds the steps after the step that is currently executing. addStepsAfterLastStep(self, step_factories) This adds the steps onto the end of the build. Both functions only accept as an argument a list of steps to add to the build. For example, let’s say you have a script checked in into your source tree called build.sh. When this script is called with the argument --list-stages it outputs a newline separated list of stage names. This can be used to generate at runtime a step for each stage in the build. Each stage is then run in this example using ./build.sh --run-stage <stage name> . from buildbot.plugins import util , steps from buildbot.process import buildstep , logobserver from twisted.internet import defer class GenerateStagesCommand ( buildstep . ShellMixin , steps . BuildStep ): def __init__ ( self , ** kwargs ): kwargs = self . setupShellMixin ( kwargs ) super () . __init__ ( ** kwargs ) self . observer = logobserver . BufferLogObserver () self . addLogObserver ( 'stdio' , self . observer ) def extract_stages ( self , stdout ): stages = [] for line in stdout . split ( ' \n ' ): stage = str ( line . strip ()) if stage : stages . append ( stage ) return stages @defer . inlineCallbacks def run ( self ): # run './build.sh --list-stages' to generate the list of stages cmd = yield self . makeRemoteShellCommand () yield self . runCommand ( cmd ) # if the command passes extract the list of stages result = cmd . results () if result == util . SUCCESS : # create a ShellCommand for each stage and add them to the build self . build . addStepsAfterCurrentStep ([ steps . ShellCommand ( name = stage , command = [ "./build.sh" , "--run-stage" , stage ]) for stage in self . extract_stages ( self . observer . getStdout ()) ]) return result f = util . BuildFactory () f . addStep ( steps . Git ( repourl = repourl )) f . addStep ( GenerateStagesCommand ( name = "Generate build stages" , command = [ "./build.sh" , "--list-stages" ], haltOnFailure = True )) 2.5.10.3. Predefined Build Factories Buildbot includes a few predefined build factories that perform common build sequences. In practice, these are rarely used, as every site has slightly different requirements, but the source for these factories may provide examples for implementation of those requirements. GNUAutoconf class buildbot.process.factory. GNUAutoconf GNU Autoconf is a software portability tool, intended to make it possible to write programs in C (and other languages) which will run on a variety of UNIX-like systems. Most GNU software is built using autoconf. It is frequently used in combination with GNU automake. These tools both encourage a build process which usually looks like this: % CONFIG_ENV = foo ./configure --with-flags % make all % make check # make install (except, of course, from Buildbot, which always skips the make install part). The Buildbot’s buildbot.process.factory.GNUAutoconf factory is designed to build projects which use GNU autoconf and/or automake. The configuration environment variables, the configure flags, and command lines used for the compile and test are all configurable, in general the default values will be suitable. Example: f = util . GNUAutoconf ( source = source . SVN ( repourl = URL , mode = "copy" ), flags = [ "--disable-nls" ]) Required Arguments: source This argument must be a step specification tuple that provides a BuildStep to generate the source tree. Optional Arguments: configure The command used to configure the tree. Defaults to ./configure . Accepts either a string or a list of shell argv elements. configureEnv The environment used for the initial configuration step. This accepts a dictionary which will be merged into the worker’s normal environment. This is commonly used to provide things like CFLAGS="-O2 -g" (to turn off debug symbols during the compile). Defaults to an empty dictionary. configureFlags A list of flags to be appended to the argument list of the configure command. This is commonly used to enable or disable specific features of the autoconf-controlled package, like ["--without-x"] to disable windowing support. Defaults to an empty list. reconf use autoreconf to generate the ./configure file, set to True to use a buildbot default autoreconf command, or define the command for the ShellCommand. compile this is a shell command or list of argv values which is used to actually compile the tree. It defaults to make all . If set to None , the compile step is skipped. test this is a shell command or list of argv values which is used to run the tree’s self-tests. It defaults to make check . If set to None, the test step is skipped. distcheck this is a shell command or list of argv values which is used to run the packaging test. It defaults to make distcheck . If set to None, the test step is skipped. BasicBuildFactory class buildbot.process.factory. BasicBuildFactory This is a subclass of GNUAutoconf which assumes the source is in CVS, and uses mode='full' and method='clobber' to always build from a clean working copy. QuickBuildFactory class buildbot.process.factory. QuickBuildFactory The QuickBuildFactory class is a subclass of GNUAutoconf which assumes the source is in CVS, and uses mode='incremental' to get incremental updates. The difference between a full build and a quick build is that quick builds are generally done incrementally, starting with the tree where the previous build was performed. That simply means that the source-checkout step should be given a mode='incremental' flag, to do the source update in-place. In addition to that, this class sets the useProgress flag to False . Incremental builds will (or at least the ought to) compile as few files as necessary, so they will take an unpredictable amount of time to run. Therefore it would be misleading to claim to predict how long the build will take. This class is probably not of use to new projects. BasicSVN class buildbot.process.factory. BasicSVN This class is similar to QuickBuildFactory , but uses SVN instead of CVS. CPAN class buildbot.process.factory. CPAN Most Perl modules available from the CPAN archive use the MakeMaker module to provide configuration, build, and test services. The standard build routine for these modules looks like: % perl Makefile.PL % make % make test # make install (except again Buildbot skips the install step) Buildbot provides a CPAN factory to compile and test these projects. Arguments: source (required): A step specification tuple, like that used by GNUAutoconf . perl A string which specifies the perl executable to use. Defaults to just perl . Distutils Deprecated since version 4.0. class buildbot.process.factory. Distutils Most Python modules use the distutils package to provide configuration and build services. The standard build process looks like: % python ./setup.py build % python ./setup.py install Unfortunately, although Python provides a standard unit-test framework named unittest , to the best of my knowledge, distutils does not provide a standardized target to run such unit tests. (Please let me know if I’m wrong, and I will update this factory.) The Distutils factory provides support for running the build part of this process. It accepts the same source= parameter as the other build factories. Arguments: source (required): A step specification tuple, like that used by GNUAutoconf . python A string which specifies the python executable to use. Defaults to just python . test Provides a shell command which runs unit tests. This accepts either a string or a list. The default value is None , which disables the test step (since there is no common default command to run unit tests in distutils modules). Trial class buildbot.process.factory. Trial Twisted provides a unit test tool named trial which provides a few improvements over Python’s built-in unittest module. Many Python projects which use Twisted for their networking or application services also use trial for their unit tests. These modules are usually built and tested with something like the following: % python ./setup.py build % PYTHONPATH = build/lib.linux-i686-2.3 trial -v PROJECTNAME.test % python ./setup.py install Unfortunately, the build/lib directory into which the built/copied .py files are placed is actually architecture-dependent, and I do not yet know of a simple way to calculate its value. For many projects it is sufficient to import their libraries in place from the tree’s base directory ( PYTHONPATH=. ). In addition, the PROJECTNAME value where the test files are located is project-dependent: it is usually just the project’s top-level library directory, as common practice suggests the unit test files are put in the test sub-module. This value cannot be guessed, the Trial class must be told where to find the test files. The Trial class provides support for building and testing projects which use distutils and trial. If the test module name is specified, trial will be invoked. The library path used for testing can also be set. One advantage of trial is that the Buildbot happens to know how to parse trial output, letting it identify which tests passed and which ones failed. The Buildbot can then provide fine-grained reports about how many tests have failed, when individual tests fail when they had been passing previously, etc. Another feature of trial is that you can give it a series of source .py files, and it will search them for special test-case-name tags that indicate which test cases provide coverage for that file. Trial can then run just the appropriate tests. This is useful for quick builds, where you want to only run the test cases that cover the changed functionality. Arguments: testpath Provides a directory to add to PYTHONPATH when running the unit tests, if tests are being run. Defaults to . to include the project files in-place. The generated build library is frequently architecture-dependent, but may simply be build/lib for pure-Python modules. python Which Python executable to use. This list will form the start of the argv array that will launch trial. If you use this, you should set trial to an explicit path (like /usr/bin/trial or ./bin/trial ). The parameter defaults to None , which leaves it out entirely (running trial args instead of python ./bin/trial args ). Likely values are ['python'] , ['python2.2'] , or ['python', '-Wall'] . trial Provides the name of the trial command. It is occasionally useful to use an alternate executable, such as trial2.2 which might run the tests under an older version of Python. Defaults to trial . trialMode A list of arguments to pass to trial, specifically to set the reporting mode. This defaults to ['--reporter=bwverbose'] , which only works for Twisted-2.1.0 and later. trialArgs A list of arguments to pass to trial, available to turn on any extra flags you like. Defaults to [] . tests Provides a module name or names which contain the unit tests for this project. Accepts a string, typically PROJECTNAME .test , or a list of strings. Defaults to None , indicating that no tests should be run. You must either set this or testChanges . testChanges If True , ignore the tests parameter and instead ask the Build for all the files that make up the Changes going into this build. Pass these filenames to trial and ask it to look for test-case-name tags, running just the tests necessary to cover the changes. recurse If True , tells Trial (with the --recurse argument) to look in all subdirectories for additional test cases. reactor which reactor to use, like ‘gtk’ or ‘java’. If not provided, the Twisted’s usual platform-dependent default is used. randomly If True , tells Trial (with the --random=0 argument) to run the test cases in random order, which sometimes catches subtle inter-test dependency bugs. Defaults to False . The step can also take any of the ShellCommand arguments, e.g., haltOnFailure . Unless one of tests or testChanges are set, the step will generate an exception. Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://www.iso.org/es/contents/data/standard/07/11/71164.html | ISO 30415:2021 - Human resource management — Diversity and inclusion Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Reference number ISO 30415:2021 © ISO 2026 International Standard ISO 30415:2021 Human resource management — Diversity and inclusion Edition 1 2021-05 Preview ISO 30415:2021 71164 ISO 30415:2021 Human resource management — Diversity and inclusion No disponible en español Publicado (Edición 1, 2021) ISO 30415:2021 ISO 30415:2021 71164 Idioma Inglés Francés Formato PDF + ePub Papel PDF + ePub Papel CHF 196 Añadir al carrito * Gastos de envío no incluidos Convertir Franco suizo (CHF) a tu moneda Resumen This document provides guidance on D&I for organizations, including their governance body, leaders, workforce and recognized representatives, and other stakeholders. It is intended to be scalable to the needs of all types of organizations in different sectors, whether in public, private, government or non-governmental organizations (NGO), regardless of size, type, activity, industry or sector, growth phase, external influences and country-specific requirements. This document presents fundamental prerequisites for D&I, associated accountabilities and responsibilities, recommended actions, suggested measures and potential outcomes. It recognizes that each organization is different and that decision makers need to determine the most appropriate approach to embedding D&I in their organization, based on the organization’s context and any disruptive challenges that emerge. This document does not address the specific aspects of relations with labour unions or work councils, or country-specific compliance, legal requirements or litigation. Informaciones generales Estado : Publicado Fecha de publicación : 2021-05 Etapa : Norma Internacional publicada [ 60.60 ] Edición : 1 Número de páginas : 42 Comité Técnico : ISO/TC 260 ICS : 03.100.30 RSS actualizaciones Ciclo de vida Ahora Publicado ISO 30415:2021 Etapa: 60.60 00 Preliminar 10 Propuesta 10.99 2016-08-23 Nuevo proyecto aprobado 20 Preparación 20.00 2016-08-23 Nuevo proyecto registrado en el programa de trabajo TC/SC 30 Comité 30.00 2019-03-11 Borrador de comité (CD) registrado 30.20 2019-03-12 Estudio de CD iniciado 30.60 2019-05-08 Cierre del periodo de observaciones 30.99 2019-09-17 CD aprobado para su registro como DIS 40 Consulta 40.00 2019-09-25 DIS registrado 40.20 2019-11-27 Voto sobre el DIS iniciado: 12 semanas 40.60 2020-02-20 Cierre de la votación 40.99 2020-03-24 Informe completo distribuido: DIS aprobado para su registro como FDIS 50 Aprobación 50.00 2020-12-07 Texto final recibido o FDIS registrado para su aprobación formal 50.20 2021-01-27 Envío de la prueba a la secretaría o inicio de la votación del FDIS: 8 semanas 50.60 2021-03-25 Cierre de la votación. Prueba devuelta por la secretaría 60 Publicación 60.00 2021-03-25 Norma Internacional en proceso de publicación 60.60 2021-05-04 Norma Internacional publicada 90 Revisión 90.20 Norma Internacional en proceso de revisión sistemática 90.60 Cierre de la revisión 90.92 Norma Internacional para revisar 90.93 Norma Internacional confirmada 90.99 Retirada de la Norma Internacional propuesta por TC o SC 95 Retirada 95.99 Retirada de la Norma Internacional Esta norma contribuye a los siguientes Objetivos de Desarrollo Sostenible 10 Reduced Inequalities 8 Decent Work and Economic Growth 5 Gender Equality ¿Tiene alguna duda? Consulte nuestras Ayuda y asistencia Tienda Tienda ICS 03 03.100 03.100.30 ISO 30415:2021 Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fawscommunity-asean%252Fcountermeasure-against-cve-2021-44228-with-aws-waf-4n3d%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-how-it-works.html | Mise en route des fonctions Lambda@Edge (console) - Amazon CloudFront Mise en route des fonctions Lambda@Edge (console) - Amazon CloudFront Documentation Amazon CloudFront Guide du développeur Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Mise en route des fonctions Lambda@Edge (console) Avec Lambda @Edge, vous pouvez utiliser des CloudFront déclencheurs pour appeler une fonction Lambda. Lorsque vous associez une CloudFront distribution à une fonction Lambda, CloudFront intercepte les demandes et les réponses à des emplacements CloudFront périphériques et exécute la fonction. Les fonctions Lambda peuvent améliorer la sécurité ou personnaliser des informations à proximité de vos utilisateurs, afin d’améliorer les performances. La liste suivante fournit un aperçu de base de la création et de l'utilisation de fonctions Lambda avec. CloudFront Présentation : Création et utilisation de fonctions Lambda avec CloudFront Créez une fonction Lambda dans la région USA Est (Virginie du Nord). Enregistrez et publiez une version numérotée de la fonction. Si vous souhaitez modifier la fonction, vous devez modifier la version $LATEST de la fonction dans la région USA Est (Virginie du Nord). Ensuite, avant de le configurer pour qu'il fonctionne CloudFront, vous publiez une nouvelle version numérotée. Associez la fonction à une CloudFront distribution et à un comportement de cache. Spécifiez ensuite un ou plusieurs CloudFront événements ( déclencheurs ) à l'origine de l'exécution de la fonction. Par exemple, vous pouvez créer un déclencheur pour que la fonction s'exécute lorsqu'elle CloudFront reçoit une demande d'un utilisateur. Lorsque vous créez un déclencheur, Lambda crée des réplicas de la fonction dans les emplacements AWS à travers le monde. Astuce Pour plus d'informations, consultez les sections Création et mise à jour de fonctions , structure d'événement et ajout de CloudFront déclencheurs . Vous pouvez également trouver d'autres idées et obtenir des exemples de code dans Exemples de fonctions Lambda@Edge . Pour un step-by-step didacticiel, consultez la rubrique suivante : Rubriques Didacticiel : création d’une fonction Lambda@Edge basique (console) JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Comment utiliser Lambda@Edge Didacticiel : fonction Lambda@Edge basique Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:30:34 |
https://matplotlib.org/gallery/lines_bars_and_markers/scatter_star_poly.html#main-content | Marker examples — Matplotlib 3.10.8 documentation Skip to main content Back to top Ctrl + K Plot types User guide Tutorials Examples Reference Contribute Releases Gitter Discourse GitHub Twitter Plot types User guide Tutorials Examples Reference Contribute Releases Gitter Discourse GitHub Twitter Section Navigation Lines, bars and markers Infinite lines Bar chart with individual bar colors Bar chart with labels Stacked bar chart Grouped bar chart with labels Horizontal bar chart Broken horizontal bars CapStyle Plotting categorical variables Plotting the coherence of two signals Cross spectral density (CSD) Curve with error band Errorbar limit selection Errorbar subsampling EventCollection Demo Eventplot demo Filled polygon fill_between with transparency Fill the area between two lines Fill the area between two vertical lines Bar chart with gradients Hat graph Discrete distribution as horizontal bar chart JoinStyle Dashed line style configuration Lines with a ticked patheffect Linestyles Marker reference Markevery Demo Plotting masked and NaN values Multicolored lines Mapping marker properties to multivariate data Power spectral density (PSD) Scatter Demo2 Scatter plot with histograms Scatter plot with masked values Marker examples Scatter plot with a legend Line plot Shade regions defined by a logical mask using fill_between Spectrum representations Stackplots and streamgraphs Stairs Demo Stem plot Step Demo Timeline with lines, dates, and text hlines and vlines Cross- and auto-correlation Images, contours and fields Affine transform of an image Wind barbs Barcode Interactive adjustment of colormap range Colormap normalizations Colormap normalizations SymLogNorm Contour corner mask Contour Demo Contour image Contour Label Demo Contourf demo Contourf hatching Contourf and log color scale Contouring the solution space of optimizations BboxImage Demo Figimage Demo Annotated heatmap Image resampling Clipping images with patches Many ways to plot images Image with masked values Image nonuniform Blend transparency with color in 2D images Modifying the coordinate formatter Interpolations for imshow Contour plot of irregularly spaced data Layer images with alpha blending Visualize matrices with matshow Multiple images with one colorbar pcolor images pcolormesh grids and shading pcolormesh Streamplot QuadMesh Demo Advanced quiver and quiverkey functions Quiver Simple Demo Shading example Spectrogram Spy Demos Tricontour Demo Tricontour Smooth Delaunay Tricontour Smooth User Trigradient Demo Triinterp Demo Tripcolor Demo Triplot Demo Watermark image Subplots, axes and figures Align labels and titles Programmatically control subplot adjustment Axes box aspect Axes Demo Controlling view limits using margins and sticky_edges Axes properties Axes zoom effect Draw regions that span an Axes Equal axis aspect ratio Axis label position Broken axis Custom Figure subclasses Resize Axes with constrained layout Resize Axes with tight layout Different scales on the same Axes Figure size in different units Figure labels: suptitle, supxlabel, supylabel Adjacent subplots Geographic Projections Combine two subplots using subplots and GridSpec GridSpec with variable sizes and spacing Gridspec for multi-column/row subplot layouts Nested Gridspecs Inverted axis Manage multiple figures in pyplot Secondary Axis Share axis limits and views Shared axis Figure subfigures Multiple subplots subplot2grid Subplots spacings and margins Create multiple subplots using plt.subplots Plots with different scales Zoom region inset Axes Statistics Artist customization in box plots Box plots with custom fill colors Boxplots Box plot vs. violin plot comparison Separate calculation and plotting of boxplots Plot a confidence ellipse of a two-dimensional dataset Violin plot customization Errorbar function Different ways of specifying error bars Including upper and lower limits in error bars Create boxes from error bars using PatchCollection Hexagonal binned plot Histograms Bihistogram Cumulative distributions Demo of the histogram function's different histtype settings The histogram (hist) function with multiple data sets Histogram bins, density, and weight Multiple histograms side by side Time Series Histogram Violin plot basics Pie and polar charts Pie charts Bar of pie Nested pie charts A pie and a donut with labels Bar chart on polar axis Polar plot Error bar rendering on polar axis Polar legend Scatter plot on polar axis Text, labels and annotations Accented text Align y-labels Scale invariant angle label Angle annotations on bracket arrows Annotate transform Annotating a plot Annotate plots Annotate polar plots Arrow Demo Auto-wrap text Compose custom legends Date tick labels AnnotationBbox demo Using a text as a Path Text rotation mode The difference between \dfrac and \frac Format ticks using engineering notation Annotation arrow style reference Styling text boxes Figure legend demo Configure the font family Using ttf font files Font table Fonts demo (object-oriented style) Fonts demo (keyword arguments) Labelling subplots Legend using pre-defined labels Legend Demo Artist within an artist Convert texts to images Mathtext Mathematical expressions Math fontfamily Multiline Placing text boxes Concatenate text objects with different properties STIX Fonts Render math equations using TeX Text alignment Text properties Controlling style of text and labels using a dictionary Text rotation angle in data coordinates Title positioning Unicode minus Usetex text baseline Usetex font effects Text watermark Color Color Demo Color by y-value Colors in the default property cycle Named color sequences Colorbar Colormap reference Create a colormap from a list of colors Selecting individual colors from a colormap List of named colors Ways to set a color's alpha value Shapes and collections Arrow guide Reference for Matplotlib artists Line, Poly and RegularPoly Collection with autoscaling Compound path Dolphins Mmh Donuts!!! Ellipse with orientation arrow demo Ellipse Collection Ellipse Demo Drawing fancy boxes Hatch demo Hatch style reference Plot multiple lines using a LineCollection Circles, Wedges and Polygons PathPatch object Bezier curve Scatter plot Style sheets Bayesian Methods for Hackers style sheet Dark background style sheet FiveThirtyEight style sheet ggplot style sheet Grayscale style sheet Petroff10 style sheet Solarized Light stylesheet Style sheets reference Module - pyplot Simple plot Text and mathtext using pyplot Multiple lines using pyplot Two subplots using pyplot Module - axes_grid1 Anchored Direction Arrow Axes divider Demo Axes Grid Axes Grid2 HBoxDivider and VBoxDivider demo Show RGB channels using RGBAxes Colorbar with AxesDivider Control the position and size of a colorbar with Inset Axes Per-row or per-column colorbars Axes with a fixed physical size ImageGrid cells with a fixed aspect ratio Inset locator demo Inset locator demo 2 Make room for ylabel using axes_grid Parasite Simple Parasite Simple2 Align histogram to scatter plot using locatable Axes Simple Anchored Artists Simple Axes Divider 1 Simple axes divider 3 Simple ImageGrid Simple ImageGrid 2 Simple Axisline4 Module - axisartist Axis Direction axis_direction demo Axis line styles Curvilinear grid demo Demo CurveLinear Grid2 floating_axes features floating_axis demo Parasite Axes demo Parasite axis demo Ticklabel alignment Ticklabel direction Simple axis direction Simple axis tick label and tick directions Simple axis pad Custom spines with axisartist Simple Axisline Simple Axisline3 Showcase Anatomy of a figure Firefox Integral as the area under a curve Shaded & power normalized rendering Pan/zoom events of overlapping axes Stock prices over 32 years XKCD Animation Decay Animated histogram pyplot animation The Bayes update The double pendulum problem Animated image using a precomputed list of images Frame grabbing Multiple Axes animation Pause and resume an animation Rain simulation Animated 3D random walk Animated line plot Animated scatter saved as GIF Oscilloscope Matplotlib unchained Event handling Close event Mouse move and click events Cross-hair cursor Data browser Figure/Axes enter and leave events Interactive functions Scroll event Keypress event Lasso Demo Legend picking Looking glass Path editor Pick event demo Pick event demo 2 Polygon editor Pong Resampling Data Timers Trifinder Event Demo Viewlims Zoom modifies other Axes Miscellaneous Anchored Artists Identify whether artists intersect Manual Contour Coords Report Custom projection Customize Rc AGG filter Ribbon box Add lines directly to a figure Fill spiral Findobj Demo Font indexing Font properties Building histograms using Rectangles and PolyCollections Hyperlinks Image thumbnail Plotting with keywords Matplotlib logo Multipage PDF Multiprocessing Packed-bubble chart Patheffect Demo Print image to stdout Rasterization for vector graphics Set and get properties Apply SVG filter to a line SVG filter pie Table Demo TickedStroke patheffect transforms.offset_copy Zorder Demo 3D plotting Plot 2D data on 3D plot Demo of 3D bar charts Clip the data to the axes view limits Create 2D bar graphs in different planes 3D box surface plot Plot contour (level) curves in 3D Plot contour (level) curves in 3D using the extend3d option Project contour profiles onto a graph Filled contours Project filled contour onto a graph Custom hillshading in a 3D surface plot 3D errorbars Fill between 3D lines Fill under 3D line graphs Create 3D histogram of 2D data 2D images in 3D Intersecting planes Parametric curve Lorenz attractor 2D and 3D Axes in same figure Automatic text offsetting Draw flat objects in 3D plot Generate 3D polygons 3D plot projection types 3D quiver plot Rotating a 3D plot 3D scatterplot 3D stem 3D plots as subplots 3D surface (colormap) 3D surface (solid color) 3D surface (checkerboard) 3D surface with polar coordinates Text annotations in 3D Triangular 3D contour plot Triangular 3D filled contour plot Triangular 3D surfaces More triangular 3D surfaces Primary 3D view planes 3D voxel / volumetric plot 3D voxel plot of the NumPy logo 3D voxel / volumetric plot with RGB colors 3D voxel / volumetric plot with cylindrical coordinates 3D wireframe plot Animate a 3D wireframe plot 3D wireframe plots in one direction Scales Scales overview Asinh scale Loglog aspect Custom scale Log scale Logit scale Exploring normalizations Symlog scale Specialty plots Hillshading Anscombe's quartet Hinton diagrams Ishikawa Diagram Left ventricle bullseye MRI with EEG Radar chart (aka spider or star chart) The Sankey class Long chain of connections using Sankey Rankine power cycle SkewT-logP diagram: using transforms and custom projections Topographic hillshading Spines Spines Spine placement Dropped spines Multiple y-axis with Spines Centered spines with arrows Ticks Align tick labels Automatically setting tick positions Center labels between ticks Colorbar Tick Labelling Custom Ticker Format date ticks using ConciseDateFormatter Date Demo Convert Placing date ticks using recurrence rules Date tick locators and formatters Custom tick formatter for time series Date precision and epochs Dollar ticks SI prefixed offsets and natural order of magnitudes Fig Axes Customize Simple Major and minor ticks Multilevel (nested) ticks The default tick formatter Tick formatters Tick locators Set default y-axis tick labels on the right Setting tick labels from a list of values Move x-axis tick labels to the top Rotated tick labels Fixing too many ticks Units Annotation with units Artist tests Bar demo with units Group barchart with units Basic units Ellipse with units Evans test Radian ticks Inches and centimeters Unit handling Embedding Matplotlib in graphical user interfaces CanvasAgg demo Embed in GTK3 with a navigation toolbar Embed in GTK3 Embed in GTK4 with a navigation toolbar Embed in GTK4 Embed in Qt Embed in Tk Embed in wx #2 Embed in wx #3 Embed in wx #4 Embed in wx #5 Embedding WebAgg Fourier Demo WX GTK3 spreadsheet GTK4 spreadsheet Display mathtext in WX Matplotlib with Glade 3 mplcvd -- an example of figure hook pyplot with GTK3 pyplot with GTK4 SVG Histogram SVG Tooltip Tool Manager Embed in a web application server (Flask) Add a cursor in WX Widgets Annotated cursor Buttons Check buttons Cursor Lasso Selector Menu Mouse Cursor Multicursor Select indices from a collection using polygon selector Polygon Selector Radio Buttons Image scaling using a RangeSlider Rectangle and ellipse selectors Slider Snap sliders to discrete values Span Selector Textbox Userdemo Nested GridSpecs Simple Legend01 Simple Legend02 Examples Lines, bars and markers Marker examples Note Go to the end to download the full example code. Marker examples # Example with different ways to specify markers. See also the matplotlib.markers documentation for a list of all markers and Marker reference for more information on configuring markers. import matplotlib.pyplot as plt import numpy as np # Fixing random state for reproducibility np . random . seed ( 19680801 ) x = np . random . rand ( 10 ) y = np . random . rand ( 10 ) z = np . sqrt ( x ** 2 + y ** 2 ) fig , axs = plt . subplots ( 2 , 3 , sharex = True , sharey = True , layout = "constrained" ) # Matplotlib marker symbol axs [ 0 , 0 ] . scatter ( x , y , s = 80 , c = z , marker = ">" ) axs [ 0 , 0 ] . set_title ( "marker='>'" ) # marker from TeX: passing a TeX symbol name enclosed in $-signs axs [ 0 , 1 ] . scatter ( x , y , s = 80 , c = z , marker = r "$\clubsuit$" ) axs [ 0 , 1 ] . set_title ( r "marker=r'\$\clubsuit\$'" ) # marker from path: passing a custom path of N vertices as a (N, 2) array-like verts = [[ - 1 , - 1 ], [ 1 , - 1 ], [ 1 , 1 ], [ - 1 , - 1 ]] axs [ 0 , 2 ] . scatter ( x , y , s = 80 , c = z , marker = verts ) axs [ 0 , 2 ] . set_title ( "marker=verts" ) # regular pentagon marker axs [ 1 , 0 ] . scatter ( x , y , s = 80 , c = z , marker = ( 5 , 0 )) axs [ 1 , 0 ] . set_title ( "marker=(5, 0)" ) # regular 5-pointed star marker axs [ 1 , 1 ] . scatter ( x , y , s = 80 , c = z , marker = ( 5 , 1 )) axs [ 1 , 1 ] . set_title ( "marker=(5, 1)" ) # regular 5-pointed asterisk marker axs [ 1 , 2 ] . scatter ( x , y , s = 80 , c = z , marker = ( 5 , 2 )) axs [ 1 , 2 ] . set_title ( "marker=(5, 2)" ) plt . show () ', marker=r'\$\clubsuit\$', marker=verts, marker=(5, 0), marker=(5, 1), marker=(5, 2)" class = "sphx-glr-single-img"/> Tags: component: marker level: beginner Total running time of the script: (0 minutes 2.466 seconds) Download Jupyter notebook: scatter_star_poly.ipynb Download Python source code: scatter_star_poly.py Download zipped: scatter_star_poly.zip Gallery generated by Sphinx-Gallery so the DOM is not blocked --> © Copyright 2002–2012 John Hunter, Darren Dale, Eric Firing, Michael Droettboom and the Matplotlib development team; 2012–2025 The Matplotlib development team. Created using Sphinx 8.2.3. Built from v3.10.8-7-g1957ba3918. Built with the PyData Sphinx Theme 0.15.4. | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0ODBxi9Ky_q5Zd-o4dYpnmHyfX6cU94o0TSebfXayTVSpJVZhsLNiaEOYJD4tF5NyHmlhcHvBZpujDEdp7WEIct_OsB2vtYxvgex9BobCz0QD-I7CT9qU5M2_9NMDpfEnKNwsIMtWszByH | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fawscommunity-asean%252Fcountermeasure-against-cve-2021-44228-with-aws-waf-4n3d%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/cmdline.html#cmdline-stop%20(worker) | 2.7. Command-line Tool — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.7.1. buildbot 2.7.1.1. Administrator Tools 2.7.1.2. Developer Tools 2.7.1.3. Other Tools 2.7.1.4. .buildbot config directory 2.7.2. buildbot-worker 2.7.2.1. create-worker 2.7.2.2. start 2.7.2.3. restart 2.7.2.4. stop 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.7. Command-line Tool View page source 2.7. Command-line Tool This section describes command-line tools available after buildbot installation. The two main command-line tools are buildbot and buildbot-worker . The former handles a Buildbot master and the former handles a Buildbot worker. Every command-line tool has a list of global options and a set of commands which have their own options. One can run these tools in the following way: buildbot [global options] command [command options] buildbot-worker [global options] command [command options] The buildbot command is used on the master, while buildbot-worker is used on the worker. Global options are the same for both tools which perform the following actions: --help Print general help about available commands and global options and exit. All subsequent arguments are ignored. --verbose Set verbose output. --version Print current buildbot version and exit. All subsequent arguments are ignored. You can get help on any command by specifying --help as a command option: buildbot command --help You can also use manual pages for buildbot and buildbot-worker for quick reference on command-line options. The remainder of this section describes each buildbot command. See Command Line Index for a full list. 2.7.1. buildbot The buildbot command-line tool can be used to start or stop a buildmaster or buildbot, and to interact with a running buildmaster. Some of its subcommands are intended for buildmaster admins, while some are for developers who are editing the code that the buildbot is monitoring. 2.7.1.1. Administrator Tools The following buildbot sub-commands are intended for buildmaster administrators: create-master buildbot create-master -r {BASEDIR} This creates a new directory and populates it with files that allow it to be used as a buildmaster’s base directory. You will usually want to use the option -r option to create a relocatable buildbot.tac . This allows you to move the master directory without editing this file. upgrade-master buildbot upgrade-master {BASEDIR} This upgrades a previously created buildmaster’s base directory for a new version of buildbot master source code. This will copy the web server static files, and potentially upgrade the db. start buildbot start [--nodaemon] {BASEDIR} This starts a buildmaster which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. Additionally, the user can set the environment variable START_TIMEOUT to specify the amount of time the script waits for the master to start until it declares the operation as failure. restart buildbot restart [--nodaemon] {BASEDIR} Restart the buildmaster. This is equivalent to stop followed by start The option –nodaemon option has the same meaning as for start . stop buildbot stop {BASEDIR} This terminates the daemon (either buildmaster or worker) running in the given directory. The --clean option shuts down the buildmaster cleanly. With --no-wait option buildbot stop command will send buildmaster shutdown signal and will immediately exit, not waiting for complete buildmaster shutdown. sighup buildbot sighup {BASEDIR} This sends a SIGHUP to the buildmaster running in the given directory, which causes it to re-read its master.cfg file. checkconfig buildbot checkconfig {BASEDIR|CONFIG_FILE} This checks if the buildmaster configuration is well-formed and contains no deprecated or invalid elements. If no arguments are used or the base directory is passed as the argument the config file specified in buildbot.tac is checked. If the argument is the path to a config file then it will be checked without using the buildbot.tac file. cleanupdb buildbot cleanupdb {BASEDIR|CONFIG_FILE} [-q] This command is frontend for various database maintenance jobs: optimiselogs: This optimization groups logs into bigger chunks to apply higher level of compression. This script runs for as long as it takes to finish the job including the time needed to check master.cfg file. copy-db buildbot copy-db {DESTINATION_URL} {BASEDIR} [-q] This command copies all buildbot data from source database configured in the buildbot configuration file to the destination database. The URL of the destination database is specified on the command line. The destination database may have different type from the source database. The destination database must be empty. The script will initialize it in the same way as if a new Buildbot installation was created. Source database must be already upgraded to the current Buildbot version by the buildbot upgrade-master command. 2.7.1.2. Developer Tools These tools are provided for use by the developers who are working on the code that the buildbot is monitoring. try This lets a developer to ask the question What would happen if I committed this patch right now? . It runs the unit test suite (across multiple build platforms) on the developer’s current code, allowing them to make sure they will not break the tree when they finally commit their changes. The buildbot try command is meant to be run from within a developer’s local tree, and starts by figuring out the base revision of that tree (what revision was current the last time the tree was updated), and a patch that can be applied to that revision of the tree to make it match the developer’s copy. This (revision, patch) pair is then sent to the buildmaster, which runs a build with that SourceStamp . If you want, the tool will emit status messages as the builds run, and will not terminate until the first failure has been detected (or the last success). There is an alternate form which accepts a pre-made patch file (typically the output of a command like svn diff ). This --diff form does not require a local tree to run from. See try –diff concerning the --diff command option. For this command to work, several pieces must be in place: the Try_Jobdir or : Try_Userpass , as well as some client-side configuration. Locating the master The try command needs to be told how to connect to the try scheduler, and must know which of the authentication approaches described above is in use by the buildmaster. You specify the approach by using --connect=ssh or --connect=pb (or try_connect = 'ssh' or try_connect = 'pb' in .buildbot/options ). For the PB approach, the command must be given a option –master argument (in the form HOST : PORT ) that points to TCP port that you picked in the Try_Userpass scheduler. It also takes a option –username and option –passwd pair of arguments that match one of the entries in the buildmaster’s userpass list. These arguments can also be provided as try_master , try_username , and try_password entries in the .buildbot/options file. For the SSH approach, the command must be given option –host and option –username , to get to the buildmaster host. It must also be given option –jobdir , which points to the inlet directory configured above. The jobdir can be relative to the user’s home directory, but most of the time you will use an explicit path like ~buildbot/project/trydir . These arguments can be provided in .buildbot/options as try_host , try_username , try_password , and try_jobdir . If you need to use something different from the default ssh command for connecting to the remote system, you can use –ssh command line option or try_ssh in the configuration file. The SSH approach also provides a option –buildbotbin argument to allow specification of the buildbot binary to run on the buildmaster. This is useful in the case where buildbot is installed in a virtualenv on the buildmaster host, or in other circumstances where the buildbot command is not on the path of the user given by option –username . The option –buildbotbin argument can be provided in .buildbot/options as try_buildbotbin The following command line arguments are deprecated, but retained for backward compatibility: --tryhost is replaced by option –host --trydir is replaced by option –jobdir --master is replaced by option –masterstatus Likewise, the following .buildbot/options file entries are deprecated, but retained for backward compatibility: try_dir is replaced by try_jobdir masterstatus is replaced by try_masterstatus Waiting for results If you provide the option –wait option (or try_wait = True in .buildbot/options ), the buildbot try command will wait until your changes have either been proven good or bad before exiting. Unless you use the option –quiet option (or try_quiet=True ), it will emit a progress message every 60 seconds until the builds have completed. The SSH connection method does not support waiting for results. Choosing the Builders A trial build is performed on multiple Builders at the same time, and the developer gets to choose which Builders are used (limited to a set selected by the buildmaster admin with the TryScheduler ’s builderNames= argument). The set you choose will depend upon what your goals are: if you are concerned about cross-platform compatibility, you should use multiple Builders, one from each platform of interest. You might use just one builder if that platform has libraries or other facilities that allow better test coverage than what you can accomplish on your own machine, or faster test runs. The set of Builders to use can be specified with multiple option –builder arguments on the command line. It can also be specified with a single try_builders option in .buildbot/options that uses a list of strings to specify all the Builder names: try_builders = [ "full-OSX" , "full-win32" , "full-linux" ] If you are using the PB approach, you can get the names of the builders that are configured for the try scheduler using the get-builder-names argument: buildbot try --get-builder-names --connect = pb --master = ... --username = ... --passwd = ... Specifying the VC system The try command also needs to know how to take the developer’s current tree and extract the (revision, patch) source-stamp pair. Each VC system uses a different process, so you start by telling the try command which VC system you are using, with an argument like option –vc=cvs or option –vc=git . This can also be provided as try_vc in .buildbot/options . The following names are recognized: bzr cvs darcs hg git mtn p4 svn Finding the top of the tree Some VC systems (notably CVS and SVN) track each directory more-or-less independently, which means the try command needs to move up to the top of the project tree before it will be able to construct a proper full-tree patch. To accomplish this, the try command will crawl up through the parent directories until it finds a marker file. The default name for this marker file is .buildbot-top , so when you are using CVS or SVN you should touch .buildbot-top from the top of your tree before running buildbot try . Alternatively, you can use a filename like ChangeLog or README , since many projects put one of these files in their top-most directory (and nowhere else). To set this filename, use --topfile=ChangeLog , or set it in the options file with try_topfile = 'ChangeLog' . You can also manually set the top of the tree with --topdir=~/trees/mytree , or try_topdir = '~/trees/mytree' . If you use try_topdir , in a .buildbot/options file, you will need a separate options file for each tree you use, so it may be more convenient to use the try_topfile approach instead. Other VC systems which work on full projects instead of individual directories (Darcs, Mercurial, Git, Monotone) do not require try to know the top directory, so the option –try-topfile and option –try-topdir arguments will be ignored. If the try command cannot find the top directory, it will abort with an error message. The following command line arguments are deprecated, but retained for backward compatibility: --try-topdir is replaced by option –topdir --try-topfile is replaced by option –topfile Determining the branch name Some VC systems record the branch information in a way that try can locate it. For the others, if you are using something other than the default branch, you will have to tell the buildbot which branch your tree is using. You can do this with either the option –branch argument, or a try_branch entry in the .buildbot/options file. Determining the revision and patch Each VC system has a separate approach for determining the tree’s base revision and computing a patch. CVS try pretends that the tree is up to date. It converts the current time into a option -D time specification, uses it as the base revision, and computes the diff between the upstream tree as of that point in time versus the current contents. This works, more or less, but requires that the local clock be in reasonably good sync with the repository. SVN try does a svn status -u to find the latest repository revision number (emitted on the last line in the Status against revision: NN message). It then performs an svn diff -r NN to find out how your tree differs from the repository version, and sends the resulting patch to the buildmaster. If your tree is not up to date, this will result in the try tree being created with the latest revision, then backwards patches applied to bring it back to the version you actually checked out (plus your actual code changes), but this will still result in the correct tree being used for the build. bzr try does a bzr revision-info to find the base revision, then a bzr diff -r$base.. to obtain the patch. Mercurial hg parents --template '{node}\n' emits the full revision id (as opposed to the common 12-char truncated) which is a SHA1 hash of the current revision’s contents. This is used as the base revision. hg diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Mercurial will use. Perforce try does a p4 changes -m1 ... to determine the latest changelist and implicitly assumes that the local tree is synced to this revision. This is followed by a p4 diff -du to obtain the patch. A p4 patch differs slightly from a normal diff. It contains full depot paths and must be converted to paths relative to the branch top. To convert the following restriction is imposed. The p4base (see P4Source ) is assumed to be //depot Darcs try does a darcs changes --context to find the list of all patches back to and including the last tag that was made. This text file (plus the location of a repository that contains all these patches) is sufficient to re-create the tree. Therefore the contents of this context file are the revision stamp for a Darcs-controlled source tree. It then does a darcs diff -u to compute the patch relative to that revision. Git git branch -v lists all the branches available in the local repository along with the revision ID it points to and a short summary of the last commit. The line containing the currently checked out branch begins with “* “ (star and space) while all the others start with “ “ (two spaces). try scans for this line and extracts the branch name and revision from it. Then it generates a diff against the base revision. Todo I’m not sure if this actually works the way it’s intended since the extracted base revision might not actually exist in the upstream repository. Perhaps we need to add a –remote option to specify the remote tracking branch to generate a diff against. Monotone mtn automate get_base_revision_id emits the full revision id which is a SHA1 hash of the current revision’s contents. This is used as the base revision. mtn diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Monotone will use. patch information You can provide the option –who=dev to designate who is running the try build. This will add the dev to the Reason field on the try build’s status web page. You can also set try_who = dev in the .buildbot/options file. Note that option –who=dev will not work on version 0.8.3 or earlier masters. Similarly, option –comment=COMMENT will specify the comment for the patch, which is also displayed in the patch information. The corresponding config-file option is try_comment . Sending properties You can set properties to send with your change using either the option –property=key=value option, which sets a single property, or the option –properties=key1=value1,key2=value2… option, which sets multiple comma-separated properties. Either of these can be specified multiple times. Note that the option –properties option uses commas to split on properties, so if your property value itself contains a comma, you’ll need to use the option –property option to set it. try –diff Sometimes you might have a patch from someone else that you want to submit to the buildbot. For example, a user may have created a patch to fix some specific bug and sent it to you by email. You’ve inspected the patch and suspect that it might do the job (and have at least confirmed that it doesn’t do anything evil). Now you want to test it out. One approach would be to check out a new local tree, apply the patch, run your local tests, then use buildbot try to run the tests on other platforms. An alternate approach is to use the buildbot try --diff form to have the buildbot test the patch without using a local tree. This form takes a option –diff argument which points to a file that contains the patch you want to apply. By default this patch will be applied to the TRUNK revision, but if you give the optional option –baserev argument, a tree of the given revision will be used as a starting point instead of TRUNK. You can also use buildbot try --diff=- to read the patch from stdin . Each patch has a patchlevel associated with it. This indicates the number of slashes (and preceding pathnames) that should be stripped before applying the diff. This exactly corresponds to the option -p or option –strip argument to the patch utility. By default buildbot try --diff uses a patchlevel of 0, but you can override this with the option -p argument. When you use option –diff , you do not need to use any of the other options that relate to a local tree, specifically option –vc , option –try-topfile , or option –try-topdir . These options will be ignored. Of course you must still specify how to get to the buildmaster (with option –connect , option –tryhost , etc). 2.7.1.3. Other Tools These tools are generally used by buildmaster administrators. sendchange This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource ( PBChangeSource ) running in the buildmaster (by being set in c['change_source'] ). buildbot sendchange --master {MASTERHOST}:{PORT} --auth {USER}:{PASS} --who {USER} {FILENAMES..} The option –auth option specifies the credentials to use to connect to the master, in the form user:pass . If the password is omitted, then sendchange will prompt for it. If both are omitted, the old default (username “change” and password “changepw”) will be used. Note that this password is well-known, and should not be used on an internet-accessible port. The option –master and option –username arguments can also be given in the options file (see .buildbot config directory ). There are other (optional) arguments which can influence the Change that gets submitted: --branch (or option branch ) This provides the (string) branch specifier. If omitted, it defaults to None , indicating the default branch . All files included in this Change must be on the same branch. --category (or option category ) This provides the (string) category specifier. If omitted, it defaults to None , indicating no category . The category property can be used by schedulers to filter what changes they listen to. --project (or option project ) This provides the (string) project to which this change applies, and defaults to ‘’. The project can be used by schedulers to decide which builders should respond to a particular change. --repository (or option repository ) This provides the repository from which this change came, and defaults to '' . --revision This provides a revision specifier, appropriate to the VC system in use. --revision_file This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument. --property This parameter is used to set a property on the Change generated by sendchange . Properties are specified as a name : value pair, separated by a colon. You may specify many properties by passing this parameter multiple times. --comments This provides the change comments as a single argument. You may want to use option –logfile instead. --logfile This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin. --encoding Specifies the character encoding for all other parameters, defaulting to 'utf8' . --vc Specifies which VC system the Change is coming from, one of: cvs , svn , darcs , hg , bzr , git , mtn , or p4 . Defaults to None . user Note that in order to use this command, you need to configure a CommandlineUserManager instance in your master.cfg file, which is explained in Users Options . This command allows you to manage users in buildbot’s database. No extra requirements are needed to use this command, aside from the Buildmaster running. For details on how Buildbot manages users, see Users . --master The user command can be run virtually anywhere provided a location of the running buildmaster. The option –master argument is of the form MASTERHOST : PORT . --username PB connection authentication that should match the arguments to CommandlineUserManager . --passwd PB connection authentication that should match the arguments to CommandlineUserManager . --op There are four supported values for the option –op argument: add , update , remove , and get . Each are described in full in the following sections. --bb_username Used with the option –op=update option, this sets the user’s username for web authentication in the database. It requires option –bb_password to be set along with it. --bb_password Also used with the option –op=update option, this sets the password portion of a user’s web authentication credentials into the database. The password is first encrypted prior to storage for security reasons. --ids When working with users, you need to be able to refer to them by unique identifiers to find particular users in the database. The option –ids option lets you specify a comma separated list of these identifiers for use with the user command. The option –ids option is used only when using option –op=remove or option –op=get . --info Users are known in buildbot as a collection of attributes tied together by some unique identifier (see Users ). These attributes are specified in the form {TYPE}={VALUE} when using the option –info option. These {TYPE}={VALUE} pairs are specified in a comma separated list, so for example: --info=svn=jdoe,git='John Doe <joe@example.com>' The option –info option can be specified multiple times in the user command, as each specified option will be interpreted as a new user. Note that option –info is only used with option –op=add or with option –op=update , and whenever you use option –op=update you need to specify the identifier of the user you want to update. This is done by prepending the option –info arguments with {ID:} . If we were to update 'jschmo' from the previous example, it would look like this: --info=jdoe:git='Joe Doe <joe@example.com>' Note that option –master , option –username , option –passwd , and option –op are always required to issue the user command. The option –master , option –username , and option –passwd options can be specified in the option file with keywords user_master , user_username , and user_passwd , respectively. If user_master is not specified, then option –master from the options file will be used instead. Below are examples of how each command should look. Whenever a user command is successful, results will be shown to whoever issued the command. For option –op=add : buildbot user --master={MASTERHOST} --op=add \ --username={USER} --passwd={USERPW} \ --info={TYPE}={VALUE},... For option –op=update : buildbot user --master={MASTERHOST} --op=update \ --username={USER} --passwd={USERPW} \ --info={ID}:{TYPE}={VALUE},... For option –op=remove : buildbot user --master={MASTERHOST} --op=remove \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... For option –op=get : buildbot user --master={MASTERHOST} --op=get \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... A note on option –op=update : when updating the option –bb_username and option –bb_password , the option –info doesn’t need to have additional {TYPE}={VALUE} pairs to update and can just take the {ID} portion. 2.7.1.4. .buildbot config directory Many of the buildbot tools must be told how to contact the buildmaster that they interact with. This specification can be provided as a command-line argument, but most of the time it will be easier to set them in an options file. The buildbot command will look for a special directory named .buildbot , starting from the current directory (where the command was run) and crawling upwards, eventually looking in the user’s home directory. It will look for a file named options in this directory, and will evaluate it as a Python script, looking for certain names to be set. You can just put simple name = 'value' pairs in this file to set the options. For a description of the names used in this file, please see the documentation for the individual buildbot sub-commands. The following is a brief sample of what this file’s contents could be. # for status-reading tools masterstatus = 'buildbot.example.org:12345' # for 'sendchange' or the debug port master = 'buildbot.example.org:18990' Note carefully that the names in the options file usually do not match the command-line option name. master Equivalent to option –master for sendchange . It is the location of the pb.PBChangeSource for `sendchange . username Equivalent to option –username for the sendchange command. branch Equivalent to option –branch for the sendchange command. category Equivalent to option –category for the sendchange command. try_connect Equivalent to option –connect , this specifies how the try command should deliver its request to the buildmaster. The currently accepted values are ssh and pb . try_builders Equivalent to option –builders , specifies which builders should be used for the try build. try_vc Equivalent to option –vc for try , this specifies the version control system being used. try_branch Equivalent to option –branch , this indicates that the current tree is on a non-trunk branch. try_topdir try_topfile Use try_topdir , equivalent to option –try-topdir , to explicitly indicate the top of your working tree, or try_topfile , equivalent to option –try-topfile to name a file that will only be found in that top-most directory. try_host try_username try_dir When try_connect is ssh , the command will use try_host for option –tryhost , try_username for option –username , and try_dir for option –trydir . Apologies for the confusing presence and absence of ‘try’. try_username try_password try_master Similarly, when try_connect is pb , the command will pay attention to try_username for option –username , try_password for option –passwd , and try_master for option –master . try_wait masterstatus try_wait and masterstatus (equivalent to option –wait and master , respectively) are used to ask the try command to wait for the requested build to complete. 2.7.2. buildbot-worker buildbot-worker command-line tool is used for worker management only and does not provide any additional functionality. One can create, start, stop and restart the worker. 2.7.2.1. create-worker This creates a new directory and populates it with files that let it be used as a worker’s base directory. You must provide several arguments, which are used to create the initial buildbot.tac file. The option -r option is advisable here, just like for create-master . buildbot-worker create-worker -r {BASEDIR} {MASTERHOST}:{PORT} {WORKERNAME} {PASSWORD} The create-worker options are described in Worker Options . 2.7.2.2. start This starts a worker which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . buildbot-worker start [--nodaemon] BASEDIR The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. 2.7.2.3. restart buildbot-worker restart [--nodaemon] BASEDIR This restarts a worker which is already running. It is equivalent to a stop followed by a start . The option –nodaemon option has the same meaning as for start . 2.7.2.4. stop This terminates the daemon worker running in the given directory. buildbot stop BASEDIR Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://phproundtable.com/show/open-source-series-part-1-git-git-flow | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 7: Open Source Series Part 1: Git & Git-Flow Panelists: Ben Ramsey Beau Simensen Kris Wallsmith Emma Jane December 16 2014 Part one of a multi-part series on open source. Today we discuss open source & code management with a version control system & explore the concept of git-flow. About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:34 |
https://phproundtable.com/show/all-about-http2 | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 47: All About HTTP/2 Panelists: Davey Shafik Ben Ramsey Junade Ali June 16 2016 HTTP/1.1 will eventually be replaced by HTTP/2 so it's important for us PHP nerds to know all about the latest version of the HTTP protocol that's already running some of the internet's biggest websites. We discuss the things we need to know to start usin Why move away from HTTP/1.1? We have stretched the limits of HTTP/1.1 Pressure/innovation from Google: Google developed its own SPDY protocol SPDY was later folded into the HTTP/2 specification About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:34 |
https://hackmd.io/product?utm_source=blog&utm_medium=nav-bar | The HackMD Blog: Product Blog Product Company Changelog Education Sign in Sign in Get HackMD free Product Discover the latest on HackMD, including product launches, updates, and walk-throughs. # en # product Shareable Links: A closer look at the newest update on HackMD Explore HackMD's latest update, Shareable Links. Now you can generate a secure, customizable link to invite anyone directly. Set permissions like read-only or full-edit access, add an expiration date, and even limit how many times the link can be used. Oct 27, 2025 By Chaseton Collins # en # product Tag Management: A closer look at the newest update on HackMD Explore HackMD's latest update, Tag Management. This feature empowers users to build a robust and clean organizational system, whether they prefer using tags, folders, or a combination of both. Sep 23, 2025 By Chaseton Collins # en # product Profile Reboot: A closer look at the latest update on HackMD Explore HackMD's latest update, Profile Reboot. This update is part of a series of interaction boosts designed to help you more easily create content and collaborate with others. Sep 4, 2025 By Chaseton Collins # en # product Paragraph Citation: A closer look at the newest feature on HackMD Explore HackMD's newest feature, Paragraph Citation. These features are a series interaction boosts designed to help you more easily create content and collaborate with others. Aug 7, 2025 By Chaseton Collins # en # product Guided Comment: A closer look at the newest feature on HackMD Explore HackMD's newest feature, Guided Comment. These features are a series interaction boosts designed to help you more easily create content and collaborate with others. Jul 14, 2025 By Chaseton Collins # en # product Emoji Reply: A closer look at the newest feature on HackMD Explore HackMD's newest feature, Emoji Reply. This feature is part of a series of interaction boosts designed to help you more easily create content and collaborate with others. May 21, 2025 By Chaseton Collins # en # product Paragraph Bookmark: A closer look at the newest feature on HackMD Explore HackMD's newest feature, Paragraph Bookmark. These features are a series interaction boosts designed to help you more easily create content and collaborate with others. May 16, 2025 By Chaseton Collins # en # product Version Link: A closer look at the newest feature on HackMD Explore HackMD's newest feature, Version Link. These features are a series interaction boosts designed to help you more easily create content and collaborate with others. Apr 28, 2025 By Chaseton Collins # en # product Link Preview & Show Edit History: A closer look at new features on HackMD Explore HackMD's newest features, Link Preview and Show Edit History. These features are a series interaction boosts designed to help you more easily create content and collaborate with others. Apr 9, 2025 By Chaseton Collins 1 2 3 4 Subscribe to our newsletter Build with confidence. Never miss a beat. Learn about the latest product updates, company happenings, and technical guides in our monthly newsletter. Subscribe Build together with the ultimate Markdown editor. Learning Features Tutorial book Resources Blog Changelog Enterprise Pricing Company About Press Kit Trust Center Terms of use Privacy policy English 中文 日本語 © 2026 HackMD. All Rights Reserved. | 2026-01-13T09:30:34 |
https://www.iso.org/es/home/insights-news/insights/transport.html | ISO - Transporte Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Transporte Sistemas inteligentes de transporte: la transformación de la movilidad moderna Imagine que está en una congestión en hora punta, llega tarde y le llena la frustración cuando, de repente, el semáforo que tiene delante se adapta al flujo de tránsito y disipa la congestión en un abrir y cerrar de ojos. Esto es lo que prometen los sistemas inteligentes de transporte. Últimos artículos Movilidad en ciudades inteligentes: Transformar el futuro del transporte urbano El camino por delante: Cómo los coches autónomos están cambiando la forma en que viajamos Fiabilidad de la cadena de suministro: reforzar la resiliencia empresarial Sistemas inteligentes de transporte: la transformación de la movilidad moderna Cargar más Obtenga un valor añadido en su buzón Regístrese para obtener actualizaciones y recursos relacionados. Website Suscribirse * ¡Ya casi está! Sólo le falta un paso para unirse a la lista de suscriptores de ISO. Confirme su suscripción haciendo clic en el correo electrónico que acabamos de enviarle. No estará registrado hasta que confirme su suscripción. Si no encuentra el correo electrónico, compruebe su carpeta de correo no deseado y/o la pestaña de promociones (si utiliza Gmail). * Boletín de noticias en inglés Para saber cómo se utilizarán sus datos, consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Cómo se utilizarán sus datos Consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Perspectivas y actualidad Perspectivas Transporte Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://hackmd.io/blog/2025/11/12/november-newsletter-2025?utm_source=blog&utm_medium=recent-posts | Harvest new ideas with HackMD this November - HackMD Blog Product Company Changelog Education Sign in Sign in Get HackMD free Back to blog Harvest new ideas with HackMD this November Nov 12, 2025 By Chaseton Collins # en # newsletter November brings a sense of reflection and momentum as we move toward the end of the year. 🍂 It’s the perfect time to gather your thoughts, polish your projects, and set the stage for what’s ahead. Whether you’re wrapping up team initiatives, preparing documentation for next year, or capturing new insights, HackMD helps you stay organized and in sync. With fresh updates designed to simplify collaboration and keep creativity flowing, we’re making it easier than ever to turn your ideas into action. Here’s what’s new this November! – 🌟 Visionary voice Visionary Voice is our spotlight series, where we celebrate inspiring voices from the HackMD community. We highlight creators whose innovative ideas and collaborative spirit are driving meaningful change and setting new standards for creativity and teamwork. This month we are highlighting… Explore More SearchWing is a remarkable open community of volunteers using technology for humanity. Operating as a non-profit, SearchWing designs and builds autonomous drones that assist civilian search and rescue missions across the Mediterranean Sea — offering hope and critical support to those in distress. Founded in 2017 after a spark of inspiration from a CCC talk, the team has grown into a dedicated network of engineers, students, and humanitarians united by a shared mission: to save lives through innovation. Their principles are simple yet powerful — independence, equality, and compassion for all. By documenting their work transparently on HackMD, SearchWing embodies the spirit of collaboration and knowledge sharing, proving how open communication and open technology can come together to make a real difference in the world. 📄 Product updates Simplify collaboration with Shareable Links Inviting collaborators to your notes just got easier. 😉 With Shareable Links, you can now grant others access to your HackMD notes, no email addresses or usernames required. Whether you’re co-authoring project docs, running community workshops, or brainstorming with your team, collaboration has never been this seamless. Learn More 🖋️ From the blog From Wallet to Workspace: Decentralize using Sign-in with ETH Since announcing our wallet integration, teams have told us they love logging in with their ETH wallet. It removes passwords, keeps identity portable, and matches how they already work across chains and dapps. We’re reintroducing how signing in with your wallet works at HackMD today, explaining why our community uses it, and the quickest way to connect your wallet and get back to building. Read Now 💡 News & Insights What 986 million code pushes say about the developer workflow in 2025. Ethereum traders flip bullish as rest of market remains fearful. How AI startups should be thinking about product-market fit. That’s all this month, folks, until next time… We can’t wait to see what you create. Get started for free Play around with it first. Pay and add your team later. Get started for free Related articles Read all posts # en # newsletter Harvest new ideas with HackMD this November This season of gratitude, we’re celebrating the ideas that bring people together. Discover how HackMD’s latest updates make it easier to share knowledge, collaborate seamlessly, and stay organized through the holidays. Nov 12, 2025 By Chaseton Collins # en # newsletter Fall into focus with HackMD this October Did you miss HackMD's exciting updates over the past month? Catch up on that and more in October's Markdown Memo. Oct 15, 2025 By Chaseton Collins # en # newsletter Breeze into fall this September using HackMD Did you miss HackMD's exciting updates over the past month? Catch up on that and more in September's Markdown Memo. Sep 10, 2025 By Chaseton Collins Subscribe to our newsletter Build with confidence. Never miss a beat. Learn about the latest product updates, company happenings, and technical guides in our monthly newsletter. Subscribe Build together with the ultimate Markdown editor. Learning Features Tutorial book Resources Blog Changelog Enterprise Pricing Company About Press Kit Trust Center Terms of use Privacy policy English 中文 日本語 © 2026 HackMD. All Rights Reserved. | 2026-01-13T09:30:34 |
https://phproundtable.com/show/php7-release-management | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 25: PHP7 Release Management Panelists: Kalle Sommer Nielsen Anatol Belski July 14 2015 We've seen 2 alpha releases of PHP 7 so far and the first beta release became available this past Friday, July 10th. We might not put too much thought into what goes into each release of PHP so for this ep About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:34 |
https://aws.amazon.com/waf/pricing/ | Pricing - AWS WAF - Amazon Web Services (AWS) Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Web Application Firewall Overview Pricing Products › AWS WAF › WAF Pricing AWS WAF Pricing Get started for free Request a pricing quote AWS WAF Pricing AWS WAF charges are based on the number of web access control lists (web ACLs) that you create, the number of rules that you add per web ACL, and the number of web requests that you receive. There are no upfront commitments. AWS WAF charges are in addition to Amazon CloudFront pricing , AWS Cognito pricing , Application Load Balancer (ALB) pricing , Amazon API Gateway pricing , AWS AppSync pricing or AWS Shield Advanced pricing . AWS Shield Advanced customers get limited usage of AWS WAF as part of their subscription. AWS WAF includes 500 MB of CloudWatch Logs (Standard and Infrequent Access) and Vended Logs Ingestion per 1 million WAF requests. Any usage beyond the discounted usage is billed by Amazon CloudWatch based on WAF specific Vended Logs pricing. The per GB rate for WAF-specific vended logs pricing matches the CloudWatch Vended Logs pricing per region . WAF logs specific charges will show under the VendedLog-Bytes-WAFlogs (for CW-Standard), S3-Egress-Bytes-WAFLogs (for S3), and VendedLogIA-Bytes-WAFlogs (for CW-IA) usage types. AWS Pricing Calculator Calculate your AWS WAF and architecture cost in a single estimate. Create your custom estimate now » Pricing components AWS WAF Bot Control Fraud Control DDoS Protection AWS WAF You will be charged for each web ACL that you create and each rule that you create per web ACL. In addition, you will be charged for the number of web requests processed by the web ACL. Pricing may vary across AWS Regions. Monthly fees are prorated hourly. Pricing for AWS WAF Classic is the same as shown in the table below. You will be charged for rules inside rule groups that are created by you. In addition, you will be charged $1.00 per month (prorated hourly) for each rule group or each managed rule group that you add to your web ACL. * You will be charged an additional $0.20 per million requests for each 500 WCUs the Web ACL uses beyond the default allocation of 1500. In addition, you will be charged $0.30 per million requests for each additional 16KB analyzed beyond the default body inspection limit. For more information about default limits, see Developer Guide . AWS WAF supports standard rule actions such as Allow, Block, Count at no additional charge. You will be charged per each CAPTCHA attempt and Challenge response as per the table below. CAPTCHA attempt is when a user completes a CAPTCHA challenge that is submitted to AWS WAF for analysis, regardless of the outcome. A single CAPTCHA response can result in multiple attempts. Challenge response is when a user is served a challenge page by AWS WAF as a result of a challenge action, regardless of whether the user attempts the challenge. Bot Control AWS WAF Bot Control are AWS Managed Rules that gives you visibility and control over common and pervasive bot traffic that can consume excess resources, skew metrics, cause downtime or other undesired activities. Common Bot Control includes the first 10 million requests per month for free. Targeted Bot Control includes the first 1 million requests per month for free. The following table lists fees for additional security features that can be enabled on your web ACL. These charges are in addition to the AWS WAF fees listed in the previous table. The cost saving you receive from enabling AWS Shield Advanced resource protection does not apply to security features listed in the following table. Pricing is the same across all AWS Regions. You pay subscription fees (prorated hourly), request fees, and analysis fees where applicable. CAPTCHA attempt is when a user completes a CAPTCHA challenge that is submitted to AWS WAF for analysis, regardless of the outcome. A single CAPTCHA response can result in multiple attempts. Challenge response is when a user is served a challenge page by AWS WAF as a result of a challenge action, regardless of whether the user attempts the challenge. Fraud Control AWS WAF Fraud Control are AWS Managed Rules that protects your login and sign-up pages against attacks such as credential stuffing, credential cracking and fake account creation attacks. AWS WAF Fraud Control consists of Account Takeover Prevention and Account Creation Fraud Prevention. You will be charged a request fee as per the following table for the total requests analyzed by Account Takeover Prevention and Account Creation Fraud Prevention. You also pay a subscription fee of $10 per month per WebACL for using the AMR. CAPTCHA attempt is when a user completes a CAPTCHA challenge that is submitted to AWS WAF for analysis, regardless of the outcome. A single CAPTCHA response can result in multiple attempts. Challenge response is when a user is served a challenge page by AWS WAF as a result of a challenge action, regardless of whether the user attempts the challenge. DDoS Protection AWS WAF DDoS Protection offers protection against Layer 7 distributed denial of service attacks. Pricing is shown in the table below. Managed rule groups from AWS Marketplace When you subscribe to a managed rule group provided by an AWS Marketplace seller, you will be charged additional fees based on the price set by the seller. These charges are in addition to the AWS WAF fees described earlier. Pricing examples Case A: No managed rule group and 19 rules written by you Let’s assume that you have a web application with traffic of 10 million requests per month. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (19 rules) = $19.00 Request charges = $0.60/million * 10 million = $6.00 Total combined charges = $30.00/month Case B: One managed rule group from AWS Marketplace seller and 9 rules written by you Let’s assume that you have a web application with traffic of 10 million requests per month. In addition, let’s assume that the seller sets the price of its managed rule group at $20.00 per month (prorated hourly) and $1.20 per 1 million requests seen and processed by the managed rule group. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 managed rule group + 9 rules) = $10.00 Request charges = $0.60/million * 10 million = $6.00 Total AWS WAF charges = $21.00/month Managed rule group charges = $20.00 Managed rule group request charges = $1.20/million * 10 million = $12.00 Total AWS Marketplace charges = $32.00/month Total combined charges = $53.00/month Case C: One rule group containing 5 rules and 9 rules written by you Let’s assume that you have a web application with traffic of 10 million requests per month. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 rule group + 5 rules + 9 rules) = $15.00 Request charges = $0.60/million * 10 million = $6.00 Total combined charges = $26.00/month Case D: Bot Control enabled on web ACL and 7 rules written by you Let’s assume that you have a web application with traffic of 22 million requests per month. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 managed rule group + 7 rules) = $8.00 Request charges = $0.60/million * 22 million = $13.20 Total WAF charges = $26.20/month Bot Control charges = $10.00 * 1 = $10.00 Bot Control request charges = $1.00/million * (22 million requests - 10 million free requests) = $12.00 Total Bot Control charges = $22.00/month Total combined charges = $48.20/month Case E: Common Bot Control with scope down statement enabled on WebACL and 7 rules written by you Let’s assume that you have a web application with traffic of 20 million requests per month. In addition, let’s assume that you have specified scope down statement to limit traffic inspected by Bot Control, resulting in 50% decrease in traffic evaluated by Bot Control. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 managed rule group + 7 rules) = $8.00 Request charges = $0.60/million * 20 million = $12.00 Total WAF charges = $25.00/month Bot Control charges = $10.00 * 1 = $10.00 Bot Control request charges = $1.00/million * (20 million requests * 50% - 10 million free requests) = $0 Total Bot Control charges = $10.00/month Total combined charges = $35.00/month Case F: Targeted Bot Control enabled on 3 WebACLs and 21 rules written by you processing 35 million requests Let’s assume that you have multiple web applications protected by 3 web ACLs with combined traffic of 35 million requests per month. Web ACL charges = $5.00 * 3 = $15.00 Rule charges = $1.00 * (3 managed rule group + 21 rules) = $24.00 Request charges = $0.60/million * 35 million = $21.00 Total WAF charges = $60.00/month Bot Control charges = $10.00 * 3 = $30.00 Bot Control request charges = $10.00/million * (35 million requests - 1 million free requests) = $340.00 Total Bot Control charges = $370.00/month Total combined charges = $430.00/month Case G: Web ACL with CAPTCHA enabled and containing 4 rules inspecting 100M requests Let's assume that you have a web application with 4 rules and traffic of 100 million requests per month. CAPTCHA is enabled for one or more rules that, together, match on 1 million requests per month. Of those requests, 10,000 CAPTCHA challenges are attempted and 1,000 challenges are successful, resulting in 1,000 retry requests. For the remaining requests that match the rules, CAPTCHA challenges are either not attempted or the request is automatically allowed without having to complete a challenge because the user had previously completed a CAPTCHA challenge within the configured bypass time window. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (4 rules) = $4.00 Request charges = $0.60/million * (100 million requests + 1,000 retries) = $60.00 CAPTCHA attempts = $0.40/thousand * 10,000 = $4.00 Total combined charges = $73.00/month Case H: Web ACL with 1500 WCUs inspecting 100M and 1M requests with 16KB and 32KB body size, respectively Let's assume that you have a web ACL with 1500 web capacity units inspecting 100M request with a 16kb body size and 1M requests with a 32kb body size. Web ACL charges* = $5.00 * 1 = $5.00 Rule charges = $1.00 * (4 rules) = $4.00 Request charges = $0.60/million * (100 million requests) = $60.00 Oversized request handling charges for 32kb body size = $0.90/million * (1 million requests) = $0.90 Total combined charges = $69.90/month *For WebACLs associated with CloudFront distributions Case I: Web ACL with 2000 WCUs inspecting 100 million requests, with a default request body inspection limit of 16KB Let’s assume that you have a web ACL with 2000 web capacity units inspecting 100M request with 16KB body size. Web ACL charges* = $5.00 * 1 = $5.00 Rule charges = $1.00 * (4 rules) = $4.00 Request charges = $0.80/million * (100 million requests) = $80.00 Total combined charges = $89.00/month *For WebACLs associated with CloudFront distributions Case J: Web ACL with account takeover prevention applied on login pages and account creation fraud prevention on registration page, with 3 rules written by you at 1500 WCU and 16kb body inspection, sending 40M requests Let’s assume you have a web ACL with account takeover prevention and account creation fraud prevention with 1500 web capacity units inspecting 40M requests with a default body inspection limit of 16KB. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 managed rule group + 3 rules) = $4.00 Request charges = $0.60/million * 40 million = $24.00 Account Takeover Prevention subscription = $10.00 * 1 = $10.00 Account Creation Fraud Prevention subscription = $10.00 * 1 = $10.00 Fraud Control request charges = ($1000.00/million * 2 million requests) + ($700.00/million * 3 million requests) + ($400.00/million * 10 million requests) + ($200.00/million * 15 million requests) + ($50.00/million * 10 million requests) + 10,000 free requests = $11,600.00 Total Fraud Control charges = $11,620.00 Total combined charges = $11653.00/month Case K: Web ACL with only Account creation fraud prevention on registration page, with 3 rules written by you at 1500 WCU and 16kb body inspection, sending 5M requests Let’s assume you have a web ACL with account creation fraud prevention with 1500 web capacity units, inspecting 5M requests with a default body inspection limit of 16KB. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 managed rule group + 3 rules) = $4.00 Request charges = $0.60/million * 5 million = $3.00 Account Creation Fraud Prevention subscription = $10.00 * 1 = $10.00 Fraud Control request charges = ($1000.00/million * 2 million requests) + ($700.00/million * 3 million requests) + 10,000 free requests = $4100.00 Total Fraud Control charges = $4110.00 Total combined charges = $4122.00/month Case L: Web ACL with only Account takeover prevention applied on sign-in pages, with 3 rules written by you at 1500 WCU and 16kb body inspection, sending 15M requests Let’s assume you have a web ACL with account takeover prevention with 1500 web capacity units, inspecting 15M requests with a default body inspection limit of 16KB. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (1 managed rule group + 3 rules) = $4.00 Request charges = $0.60/million * 15 million = $9.00 Account Takeover Prevention subscription = $10.00 * 1 = $10.00 Fraud Control request charges = ($1000.00/million * 2 million requests) + ($700.00/million * 3 million requests + ($400.00/million * 10 million requests) + 10,000 free requests = $8100.00 Total Fraud Control charges = $8110.00 Total combined charges = $8128.00/month Case M: Web ACL created using Application Load Balancer’s 1-click experience, which adds 3 managed rule groups, sending 10M requests Let's assume you used an Application Load Balancer to create a web ACL, inspecting 10M requests. Web ACL charges = $5.00 * 1 = $5.00 Rule charges = $1.00 * (3 managed rule groups) = $3.00 Request charges = $0.60/million * 10 million = $6.00 Total combined charges = $14.00/month per 10 million requests Additional pricing resources AWS Pricing Calculator Easily calculate your monthly costs with AWS Get pricing assistance Contact AWS specialists to get a personalized quote Get started with AWS WAF Get started with AWS WAF Explore AWS WAF Contact an expert Contact us Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:30:34 |
https://support.microsoft.com/sv-se/windows/hantera-cookies-i-microsoft-edge-visa-till%C3%A5ta-blockera-ta-bort-och-anv%C3%A4nda-168dab11-0753-043d-7c16-ede5947fc64d | Hantera cookies i Microsoft Edge: Visa, tillåta, blockera, ta bort och använda - Microsoft Support Relaterade ämnen × Windows säkerhet och sekretess Översikt Översikt för säkerhet och sekretess Windows-säkerhet Få hjälp med Windows-säkerhet Skydda dig med Windows-säkerhet Innan du återanvänder, säljer eller ger bort din Xbox- eller Windows-dator Ta bort skadlig kod från din Windows-dator Windows-säkerhet Få hjälp med Windows-säkerhet Visa och ta bort webbhistorik i Microsoft Edge Ta bort och hantera cookies Ta bort värdefullt innehåll på ett säkert sätt när du installerar om Windows Hitta och låsa en borttappad Windows-enhet Windows-sekretess Få hjälp med Windows-sekretess Sekretessinställningar i Windows som används av appar Visa dina data på sekretesspanelen Gå till huvudinnehåll Microsoft Support Support Support Startsida Microsoft 365 Office Produkter Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mer... Enheter Surface Datortillbehör Xbox PC-spel HoloLens Surface Hub Maskinvarugarantier Konto och fakturering Konto Microsoft Store & faktureringshjälp Resurser Nyheter Community-forum Microsoft 365 administratörer Portal för småföretag Utvecklare Utbildning Rapportera ett supportbedrägeri Produktsäkerhet Mer Köp Microsoft 365 Hela Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Specialerbjudanden Små företag Support Programvara Programvara Windows-appar AI OneDrive Outlook Byta från Skype till Teams OneNote Microsoft Teams Datorer och enheter Datorer och enheter Köp Xbox Tillbehör Underhållning Underhållning Xbox Game Pass Ultimate Xbox och spel PC-spel Företag Företag Microsoft Security Azure Dynamics 365 Microsoft 365 för företag Microsoft Industry Microsoft Power Platform Windows 365 Utvecklare och IT Utvecklare och IT Microsoft Developer Microsoft Learn Stöd för AI-marknadsappar Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Andra Andra Microsoft Rewards Kostnadsfria nedladdningar och säkerhet Utbildning Presentkort Licensiering Visa webbplatskarta Sök Sök efter hjälp Inga resultat Avbryt Logga in Logga in med Microsoft Logga in eller skapa ett konto. Hej, Välj ett annat konto. Du har flera konton Välj det konto som du vill logga in med. Relaterade ämnen Windows säkerhet och sekretess Översikt Översikt för säkerhet och sekretess Windows-säkerhet Få hjälp med Windows-säkerhet Skydda dig med Windows-säkerhet Innan du återanvänder, säljer eller ger bort din Xbox- eller Windows-dator Ta bort skadlig kod från din Windows-dator Windows-säkerhet Få hjälp med Windows-säkerhet Visa och ta bort webbhistorik i Microsoft Edge Ta bort och hantera cookies Ta bort värdefullt innehåll på ett säkert sätt när du installerar om Windows Hitta och låsa en borttappad Windows-enhet Windows-sekretess Få hjälp med Windows-sekretess Sekretessinställningar i Windows som används av appar Visa dina data på sekretesspanelen Hantera cookies i Microsoft Edge: Visa, tillåta, blockera, ta bort och använda Gäller för Windows 10 Windows 11 Microsoft Edge Cookies är små data som lagras på din enhet av webbplatser du besöker. De har olika syften, till exempel att komma ihåg inloggningsuppgifter, webbplatsinställningar och spåra användarbeteende. Men du kanske vill ta bort cookies av sekretessskäl eller för att lösa problem med surfning. Den här artikeln innehåller instruktioner om hur du: Visa alla cookies Tillåt alla cookies Tillåt cookies från en viss webbplats Blockera cookies från tredje part Med Blockera alla cookies Blockera cookies från en viss webbplats Ta bort alla cookies Ta bort cookies från en särskild webbplats Ta bort cookies varje gång du stänger webbläsaren Använda cookies för att förinstallera sidan för snabbare surfning Visa alla cookies Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och klicka sedan på Visa alla cookies och webbplatsdata för att visa alla lagrade cookies och relaterad webbplatsinformation. Tillåt alla cookies Genom att tillåta cookies kan webbplatser spara och hämta data i din webbläsare, vilket kan förbättra din surfupplevelse genom att komma ihåg dina inställningar och inloggningsinformation. Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och aktivera växlingsknappen Tillåt att webbplatser sparar och läser cookie-data (rekommenderas) för att tillåta alla cookies. Tillåt cookies från en viss webbplats Genom att tillåta cookies kan webbplatser spara och hämta data i din webbläsare, vilket kan förbättra din surfupplevelse genom att komma ihåg dina inställningar och inloggningsinformation. Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och gå till Tillåts att spara cookies. Välj Lägg till webbplats om du vill tillåta cookies per webbplats genom att ange webbplatsens URL. Blockera cookies från tredje part Om du inte vill att webbplatser från tredje part ska lagra cookies på datorn kan du blockera cookies. Men om du gör det kan vissa sidor hindras från att visas korrekt, eller så kan du få ett meddelande från en webbplats om att du måste tillåta cookies för att kunna visa den webbplatsen. Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och aktivera växlingsknappen Blockera cookies från tredje part. Med Blockera alla cookies Om du inte vill att webbplatser från tredje part ska lagra cookies på datorn kan du blockera cookies. Men om du gör det kan vissa sidor hindras från att visas korrekt, eller så kan du få ett meddelande från en webbplats om att du måste tillåta cookies för att kunna visa den webbplatsen. Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och inaktivera Tillåt att webbplatser sparar och läser cookie-data (rekommenderas) för att blockera alla cookies. Blockera cookies från en viss webbplats Med Microsoft Edge kan du blockera cookies från en viss webbplats, men om du gör det kan vissa sidor inte visas korrekt, eller så kan du få ett meddelande från en webbplats om att du måste tillåta cookies för att kunna visa webbplatsen. Så här blockerar du cookies från en viss webbplats: Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och gå till Tillåts inte att spara och läsa cookies . Välj Lägg till webbplats om du vill blockera cookies per webbplats genom att ange webbplatsens URL. Ta bort alla cookies Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Radera webbdata och välj sedan Välj vad du vill radera bredvid Radera webbdata nu . Välj ett tidsintervall under Tidsintervall . Välj Cookies och andra webbplatsdata och sedan Rensa nu . Obs!: Du kan också ta bort cookies genom att trycka på CTRL + SKIFT + DELETE tillsammans och sedan fortsätta med steg 4 och 5. Alla dina cookies och andra webbplatsdata tas nu bort för det tidsintervall som du har valt. Detta loggar ut dig från de flesta webbplatser. Ta bort cookies från en särskild webbplats Öppna webbläsaren Edge, välj Inställningar med mera > Inställningar > Sekretess, sökning och tjänster . Välj Cookies , klicka sedan på Visa alla cookies och webbplatsdata och sök efter webbplatsen vars cookies du vill ta bort. Välj nedåtpilen till höger om webbplatsen vars cookies du vill ta bort och välj Ta bort . Cookies för den valda webbplatsen tas nu bort. Upprepa det här steget för webbplatser vars cookies du vill ta bort. Ta bort cookies varje gång du stänger webbläsaren Öppna webbläsaren Edge, välj Inställningar med mera > Inställningar > Sekretess, sökning och tjänster . Välj Radera webbdata och välj sedan Välj vad du vill radera varje gång du stänger webbläsaren . Aktivera Cookies och andra webbplatsdata . När den här funktionen är aktiverad tas alla cookies och andra webbplatsdata bort varje gång du stänger webbläsaren Edge. Detta loggar ut dig från de flesta webbplatser. Använda cookies för att förinstallera sidan för snabbare surfning Öppna webbläsaren Edge, välj Inställningar med mera i det övre högra hörnet i webbläsarfönstret. Välj Inställningar > Sekretess, sökning och tjänster . Välj Cookies och aktivera växlingsknappen förinläsning av sidor för snabbare surfning och sökning. PRENUMERERA PÅ RSS-FEEDS Behöver du mer hjälp? Vill du ha fler alternativ? Upptäck Community Kontakta oss Utforska prenumerationsförmåner, bläddra bland utbildningskurser, lär dig hur du skyddar din enhet med mera. Fördelar med en Microsoft 365-prenumeration Utbildning för Microsoft 365 Microsoft-säkerhet Hjälpmedelscenter Communities hjälper dig att ställa och svara på frågor, ge feedback och få råd från experter med rika kunskaper. Fråga Microsoft-communityn Microsoft Tech Community Windows Insiders Microsoft 365 Insiders Hitta lösningar på vanliga problem eller få hjälp från en supportagent. Onlinesupport Hade du nytta av den här informationen? Ja Nej Tack! Vill du ha mer feedback för Microsoft? Kan du hjälpa oss att bli bättre? (Skicka feedback till Microsoft så att vi kan hjälpa dig.) Hur nöjd är du med språkkvaliteten? Vad påverkade din upplevelse? Löste mitt problem Tydliga instruktioner Lätt att följa Ingen jargong Bilder hjälpte Översättningskvalitet Matchade inte min skärm Felaktiga instruktioner För tekniskt Det finns inte tillräckligt med information Det finns inte tillräckligt med bilder Översättningskvalitet Har du ytterligare feedback? (Valfritt) Skicka feedback Genom att trycka på skicka, kommer din feedback att användas för att förbättra Microsofts produkter och tjänster. IT-administratören kan samla in denna data. Sekretesspolicy. Tack för din feedback! × Nyheter Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot för organisationer Copilot för användning privat Microsoft 365 Utforska produkter från Microsoft Windows 11-appar Microsoft Store Kontoprofil Download Center Microsoft Store-support Returer Orderspårning Återvinning Kommersiella garantier Utbildning Microsoft Education Enheter för utbildning Microsoft Teams för utbildning Microsoft 365 Education Office Education Utbildning och utveckling för lärare Erbjudanden för elever och föräldrar Azure för studenter Företag Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Små företag Utvecklare och IT Microsoft Developer Microsoft Learn Stöd för AI-marknadsappar Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Företag Karriärmöjligheter Om Microsoft Företagsnyheter Sekretess på Microsoft Investerare Hållbarhet Svenska (Sverige) Ikon för inaktivering av sekretessval Dina sekretessval Ikon för inaktivering av sekretessval Dina sekretessval Sekretess för konsumenthälsa Kontakta Microsoft Integritet Hantera cookies Juridiskt meddelande Varumärken Om våra annonser EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://hackmd.io/blog/2025/11/19/hackmd-visits-jsconf2025?utm_source=blog&utm_medium=recent-posts | Touch down at JSConf 2025: HackMD connects with the JavaScript community - HackMD Blog Product Company Changelog Education Sign in Sign in Get HackMD free Back to blog Touch down at JSConf 2025: HackMD connects with the JavaScript community Nov 19, 2025 By Chaseton Collins # en # company Last month, HackMD touched down at JSConf 2025 with genuine excitement to meet the community that shaped the technologies powering our platform. Since day one, HackMD has been built on JavaScript and the surrounding ecosystem, so joining hundreds of developers, maintainers, and creators felt like returning to our roots. The event brought together fresh ideas, bold experiments, and passionate builders, and it offered the perfect opportunity to connect, learn, and celebrate the tools and people driving the future of JavaScript. Touching down at the event JSConf 2025 took place along the shores of Chesapeake Bay in Maryland at the Hyatt Regency Chesapeake Bay Golf Resort, Spa and Marina. The venue’s waterfront views, quiet marina, and wide open skies created a stunning backdrop for the entire event. It was the kind of setting that encouraged developers to pause, connect, and share ideas in a relaxed and inspiring environment. The beauty of the bay paired with the resort’s open, welcoming layout made it an ideal place for the JavaScript community to come together. Keynotes that set the tone for the week The keynote sessions at JSConf 2025 set a strong technical foundation for the event. One of the most technical highlights was Matteo Collina , Co-Founder & CTO of Platformatic , speaking on “Making Node.js Performance Profiling Actually Work.” Matteo opened with humor before diving into a core problem many developers face: traditional Node.js profiling tools are slow, confusing, and challenging to use in real environments like Docker or production. He walked through why the classic node --prof workflow produces unusable output, why inspector-based profiling adds heavy overhead, and why kernel tools like perf and dtrace aren’t practical for most teams. “All of this… is not really useful.” Matteo then introduced more modern approaches, including Datadog’s low-overhead pprof and the evolution of tools from 0x to Platformatic Flame, which pairs CPU and memory profiling with fast WebGL-based flame graphs. Even with a few “demo-god” surprises, the session showed how better profiling tools help teams quickly spot bottlenecks, understand memory behavior, and debug real issues without slowing down development. For HackMD, the takeaway was clear: great documentation and accessible tooling go hand-in-hand with building high-performance software. See the full keynote here. The future of JavaScript runtimes The panel with Jared Sumner ( Bun ), James Snell ( Node.js / Cloudflare ) and Lizz Parody ( NodeSource ) dug into how the runtime ecosystem has changed now that developers have more choices than ever. Both agreed the focus today isn’t the runtime itself but what developers can build with it — making compatibility, stability, and DX the real differentiators. James highlighted how Node’s governance has matured into pure technical stewardship, while Jared explained Bun’s lightweight approach as a fast-moving small team focused heavily on Node compatibility because “people aren’t going to rewrite their code.” The conversation also touched on open-source sustainability, the pain of streams, AI-assisted development, and how new contributors can get involved. Both emphasized that companies relying on OSS must support it, that AI will influence API design even if it won’t replace runtimes, and that the best way to contribute is simply to start opening PRs. It was a clear snapshot of where JavaScript runtimes stand today and how their communities are shaping what comes next. Watch the full panel here. A keynote centered on people and the story behind JSConf The final keynote HackMD attended was led by Chris Williams , creator of JSConf and Head of Professional Services at Vercel . Instead of a slide deck, Chris shared the story behind the conference itself how JSConf began as an unplanned idea, grew out of curiosity, and evolved into a global community. Chris spoke openly about the ups and downs of building JSConf, the friendships and collaborations formed over the years, and the importance of human connection in tech. His message was simple but powerful the JavaScript community is shaped by its people. Every conversation, shared moment, and unexpected story contributes to the future of the ecosystem. It was a warm, honest way to close out the main sessions and a reminder of why events like JSConf matter so much. Check out what Chris had to say here. Wrapping up with music and new friends The final night of JSConf 2025 captured everything that makes this community special. After three days of keynotes, panels, hallway chats, and shared discoveries, attendees came together for a relaxed evening of karaoke, laughter, and low pressure fun. The stage lights shifted from conference-mode to party-mode, and the room filled with people singing their favorite songs, cheering one another on, and celebrating the end of an unforgettable week. It was the perfect reminder that while JavaScript brings everyone together, it’s the human connections that keep the community strong. Between sessions and the closing celebration, there were plenty of chances to unwind and meet new people. One of our favorite moments was a friendly game of pool at the resort a great way to connect with other attendees in a laid back space. And yes, all of our new friends got a HackMD T-shirt. 😊 A huge thank you to the sponsors JSConf wouldn’t be possible without the organizations that support it. Huge shoutout to OpenJS for the invite and the event’s sponsors that helped create an environment where developers, maintainers, educators, and teams could come together to learn, explore, and collaborate. From open source projects like harper and vlt.sh to companies building the tools the JavaScript ecosystem depends on, each sponsor played a role in making JSConf 2025 a meaningful experience. JSConf 2025 brought together everything HackMD cares about innovation, community, and the power of shared knowledge. We left inspired by the people we met, the stories we heard, and the ideas shaping the future of JavaScript. Until next year. Get started for free Play around with it first. Pay and add your team later. Get started for free Related articles Read all posts # en # company 2025 in Review: New Features, Big Wins, and What Lies Ahead 2025 was about building momentum at HackMD. We are focused on refining how teams and communities collaborate, expanding the editor into a true workspace, and turning everyday documentation into shared knowledge that actually moves work forward. Dec 31, 2025 By Chaseton Collins # en # company Touch down at JSConf 2025: HackMD connects with the JavaScript community A fun recap of HackMD’s experience at JSConf 2025 featuring photos, community moments, event highlights, and insights from the people shaping the future of JavaScript. Nov 19, 2025 By Chaseton Collins # en # company Celebrating 2024: HackMD's biggest moments and a look ahead 2024 has been an incredible year at HackMD, filled with growth, innovation, and collaboration thanks to our amazing community. From launching your most-requested features to integrating web3 capabilities through Sign-In with Ethereum, we've worked to make HackMD more powerful and intuitive. Dec 10, 2024 By Rachel Golden Subscribe to our newsletter Build with confidence. Never miss a beat. Learn about the latest product updates, company happenings, and technical guides in our monthly newsletter. Subscribe Build together with the ultimate Markdown editor. Learning Features Tutorial book Resources Blog Changelog Enterprise Pricing Company About Press Kit Trust Center Terms of use Privacy policy English 中文 日本語 © 2026 HackMD. All Rights Reserved. | 2026-01-13T09:30:34 |
https://phproundtable.com/show/faceoff-taylor-otwell-vs-phil-sturgeon-debating-all-the-things | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 6: Faceoff: Taylor Otwell vs Phil Sturgeon Debating All The Things Panelists: Taylor Otwell Phil Sturgeon October 30 2014 Taylor Otwell & Phil Sturgeon go head-to-head debating all the things. About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:34 |
https://aws.amazon.com/fr/waf/ | Pare-feu pour applications web, protection des API web - AWS WAF - AWS Passer au contenu principal Filter: Tout English Nous contacter AWS Marketplace Assistance Mon compte Recherche Filter: Tout Se connecter à la console Créer un compte Pare-feu pour applications web Présentation Fonctionnalités Tarification Démarrer Ressources Plus Produits › Sécurité, identité et conformité › AWS WAF Obtenez 10 millions de requêtes de contrôle des bots par mois avec l’offre gratuite AWS AWS WAF Protégez vos applications web contre les codes malveillants les plus répandus Démarrer avec AWS WAF Avantages d’AWS WAF Gagnez du temps avec les règles gérées Gagnez du temps avec des règles gérées afin de pouvoir consacrer plus de temps à la création d'applications. Surveillez, bloquez ou limitez le débit des robots Surveillez, bloquez ou limitez plus facilement le débit des bots courants et omniprésents. Réduisez les étapes de configuration de sécurité Accélérez la configuration de sécurité complexe grâce à une interface consolidée qui réduit la complexité et les étapes de configuration du déploiement de la sécurité jusqu'à 80 %. Visibilité centralisée et exploitable Une interface unique et complète combine des fonctions de sécurité de base avec des protections spécialisées pour les partenaires afin d'améliorer la visibilité et les contrôles de sécurité. Cette approche unifiée transforme les données de sécurité en informations exploitables, éliminant les frictions opérationnelles et accélérant la réponse aux risques. Renforcez votre posture de sécurité Les packs de protection préconfigurés tirent parti de l'expertise d'AWS en matière de sécurité pour fournir des modèles de protection instantanés pour des secteurs et des types de charge de travail spécifiques tels que les API, les applications PHP et les services web. Ces modèles sont optimisés en permanence pour garantir une sécurité à jour sans nécessiter une expertise approfondie en matière de déploiement. Bénéficiez de recommandations de sécurité continues pour renforcer la posture de sécurité globale. Pourquoi AWS WAF ? Avec AWS WAF, vous pouvez créer des règles de sécurité qui contrôlent le trafic des robots et bloquent les modèles d'attaque courants tels que l'injection SQL ou les scripts inter-site (XSS). Lecture Cas d'utilisation Filtrer le trafic web Créez des règles afin de filtrer les requêtes web en fonction de conditions telles que les adresses IP, les en-têtes et corps HTTP ou les chaînes personnalisées de l'URI. En savoir plus sur la création de règles Prévenir la fraude liée au piratage de comptes Surveillez la page de connexion de votre application pour détecter tout accès non autorisé à des comptes utilisateur à l'aide d'informations d'identification compromises. En savoir plus sur la prévention des fraudes Protection automatique contre les attaques DDoS de couche 7 Conçu pour surveiller en permanence et atténuer automatiquement les attaques par déni de service distribué (DDoS) de la couche application (couche 7) en quelques secondes. Mise en œuvre rapide de la sécurité Lancez de nouvelles applications en toute confiance à l'aide de la configuration d'intégration simplifiée et guidée avec une interface d'une seule page pour activer les paramètres de sécurité préconfigurés adaptés à vos besoins. Renforcez votre posture de sécurité Grâce à des packs de règles sélectionnés par des experts, à une visibilité consolidée et à des recommandations continues, vous bénéficiez d'une protection immédiate pour optimiser votre posture de sécurité. Démarrer avec AWS WAF Démarrer avec AWS WAF Découvrir AWS WAF Contacter un expert Nous contacter Créer un compte AWS Apprendre Qu’est-ce qu’AWS ? Qu’est-ce que le cloud computing ? Qu’est-ce que l’IA agentique ? Hub de concepts de cloud computing Sécurité dans le Cloud AWS Nouveautés Blogs Communiqués de presse Ressources Démarrer Formation Centre de confiance AWS Bibliothèque de solutions AWS Centre d'architecture Questions fréquentes (FAQ) techniques et sur les produits Rapports d'analystes Partenaires AWS Développeurs Centre pour concepteurs Kits SDK et outils .NET sur AWS Python sur AWS Java sur AWS PHP sur AWS JavaScript sur AWS Aide Contactez-nous Soumettez un ticket de support AWS re:Post Centre de connaissances Présentation d’AWS Support Obtenez l’aide d’experts Accessibilité AWS Informations juridiques English Retour en haut de la page Amazon est un employeur qui souscrit aux principes d’équité en matière d’emploi : minorités, femmes, handicaps, seniors, identité de genre, orientation sexuelle, âge. x facebook linkedin instagram twitch youtube podcasts email Confidentialité Conditions d’utilisation du site Préférences en matière de cookies © 2026, Amazon Web Services, Inc. ou ses sociétés apparentées. Tous droits réservés. | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/tools/clang/docs/index.html | Welcome to Clang's documentation! — Clang 18.1.8 documentation Clang 18.1.8 documentation Welcome to Clang's documentation! Contents   ::   Clang 18.1.8 Release Notes   » Clang 18.1.8 Release Notes Using Clang as a Compiler ¶ Clang Compiler User’s Manual Assembling a Complete Toolchain Clang Language Extensions Clang command line argument reference Attributes in Clang Diagnostic flags in Clang Cross-compilation using Clang Clang Static Analyzer Thread Safety Analysis Data flow analysis: an informal introduction AddressSanitizer ThreadSanitizer MemorySanitizer UndefinedBehaviorSanitizer DataFlowSanitizer LeakSanitizer SanitizerCoverage SanitizerStats Sanitizer special case list -fbounds-safety : Enforcing bounds safety for C Implementation plans for -fbounds-safety Control Flow Integrity LTO Visibility SafeStack ShadowCallStack Source-based Code Coverage Standard C++ Modules Modules MSVC compatibility Misexpect OpenCL Support OpenMP Support SYCL Compiler and Runtime architecture design HIP Support HLSL Support HLSL Design and Implementation ThinLTO API Notes: Annotations Without Modifying Headers Debugging C++ Coroutines AMDGPU Support Clang “man” pages Frequently Asked Questions (FAQ) Using Clang as a Library ¶ Choosing the Right Interface for Your Application External Clang Examples Introduction to the Clang AST LibTooling Libclang tutorial LibFormat Clang Plugins How to write RecursiveASTVisitor based ASTFrontendActions. Tutorial for building tools using LibTooling and LibASTMatchers Matching the Clang AST Clang Transformer Tutorial ASTImporter: Merging Clang ASTs How To Setup Clang Tooling For LLVM JSON Compilation Database Format Specification Clang’s refactoring engine Using Clang Tools ¶ Overview ClangCheck ClangFormat Clang-Format Style Options Clang Formatted Status Clang Linker Wrapper Clang Offload Bundler Clang Offload Packager Clang-Repl Design Documents ¶ Clang Code Owners “Clang” CFE Internals Manual Driver Design & Internals Multilib Offloading Design & Internals Precompiled Header and Modules Internals ABI tags Hardware-assisted AddressSanitizer Design Documentation Constant Interpreter Indices and tables ¶ Index Search Page Contents   ::   Clang 18.1.8 Release Notes   » © Copyright 2007-2024, The Clang Team. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://www.php.net/x-myracloud-5958a2bbbed300a9b9ac631223924e0b/1768296241.933 | PHP update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box A popular general-purpose scripting language that is especially suited to web development. Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. What's new in 8.5 Download 8.5.1 · Changelog · Upgrading 8.4.16 · Changelog · Upgrading 8.3.29 · Changelog · Upgrading 8.2.30 · Changelog · Upgrading 18 Dec 2025 PHP 8.1.34 Released! The PHP development team announces the immediate availability of PHP 8.1.34. This is a security release. All PHP 8.1 users are encouraged to upgrade to this version. For source downloads of PHP 8.1.34 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 18 Dec 2025 PHP 8.4.16 Released! The PHP development team announces the immediate availability of PHP 8.4.16. This is a security release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.16 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 18 Dec 2025 PHP 8.2.30 Released! The PHP development team announces the immediate availability of PHP 8.2.30. This is a security release. All PHP 8.2 users are encouraged to upgrade to this version. For source downloads of PHP 8.2.30 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 18 Dec 2025 PHP 8.3.29 Released! The PHP development team announces the immediate availability of PHP 8.3.29. This is a security release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.29 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 18 Dec 2025 PHP 8.5.1 Released! The PHP development team announces the immediate availability of PHP 8.5.1. This is a security release. All PHP 8.5 users are encouraged to upgrade to this version. For source downloads of PHP 8.5.1 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 20 Nov 2025 PHP 8.5.0 Released! The PHP development team announces the immediate availability of PHP 8.5.0. This release marks the latest minor release of the PHP language. PHP 8.5 comes with numerous improvements and new features such as: New "URI" extension New pipe operator (|>) Clone With New #[\NoDiscard] attribute Support for closures, casts, and first class callables in constant expressions And much much more... For source downloads of PHP 8.5.0 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . The migration guide is available in the PHP Manual. Please consult it for the detailed list of new features and backward incompatible changes. Kudos to all the contributors and supporters! 20 Nov 2025 PHP 8.4.15 Released! The PHP development team announces the immediate availability of PHP 8.4.15. This is a bug fix release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.15 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 20 Nov 2025 PHP 8.3.28 Released! The PHP development team announces the immediate availability of PHP 8.3.28. This is a bug fix release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.28 please visit our downloads page , Windows source and binaries can also be found there . The list of changes is recorded in the ChangeLog . 13 Nov 2025 PHP 8.5.0 RC 5 available for testing The PHP team is pleased to announce the fifth release candidate of PHP 8.5.0, RC 5. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 RC5, please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is a test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be the GA release of PHP 8.5.0, planned for 20 Nov 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 06 Nov 2025 PHP 8.5.0 RC4 available for testing The PHP team is pleased to announce the final planned release candidate of PHP 8.5.0, RC 4. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 RC4, please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is a test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be the GA release of PHP 8.5.0, planned for 20 Nov 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 23 Oct 2025 PHP 8.3.27 Released! The PHP development team announces the immediate availability of PHP 8.3.27. This is a bug fix release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.27 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 23 Oct 2025 PHP 8.4.14 Released! The PHP development team announces the immediate availability of PHP 8.4.14. This is a bug fix release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.14 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 23 Oct 2025 PHP 8.5.0 RC 3 available for testing The PHP team is pleased to announce the third release candidate of PHP 8.5.0, RC 3. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 RC3, please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be RC4, planned for 6 Nov 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 09 Oct 2025 PHP 8.5.0 RC 2 available for testing The PHP team is pleased to announce the second release candidate of PHP 8.5.0, RC 2. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 RC2, please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be RC3, planned for 23 Oct 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 25 Sep 2025 PHP 8.5.0 RC 1 available for testing The PHP team is pleased to announce the first release candidate of PHP 8.5.0, RC 1. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 RC1, please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be RC2, planned for 9 Oct 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 25 Sep 2025 PHP 8.3.26 Released! The PHP development team announces the immediate availability of PHP 8.3.26. This is a bug fix release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.26 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 25 Sep 2025 PHP 8.4.13 Released! The PHP development team announces the immediate availability of PHP 8.4.13. This is a bug fix release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.13 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 11 Sep 2025 PHP 8.5.0 Beta 3 available for testing The PHP team is pleased to announce the third beta release of PHP 8.5.0, Beta 3. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 Beta 3, please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be RC1, planned for 25 Sep 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 28 Aug 2025 PHP 8.5.0 Beta 2 available for testing The PHP team is pleased to announce the second beta release of PHP 8.5.0, Beta 2. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 Beta 2 please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be Beta 3, planned for 11 Sep 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 28 Aug 2025 PHP 8.3.25 Released! The PHP development team announces the immediate availability of PHP 8.3.25. This is a bug fix release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.25 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 28 Aug 2025 PHP 8.4.12 Released! The PHP development team announces the immediate availability of PHP 8.4.12. This is a bug fix release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.12 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 14 Aug 2025 PHP 8.5.0 Beta 1 available for testing The PHP team is pleased to announce the first beta release of PHP 8.5.0, Beta 1. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 Beta 1 please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be Beta 2, planned for 28 Aug 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 01 Aug 2025 PHP 8.5.0 Alpha 4 available for testing The PHP team is pleased to announce the third testing release of PHP 8.5.0, Alpha 4. This continues the PHP 8.5 release cycle, the rough outline of which is specified in the PHP Wiki . For source downloads of PHP 8.5.0 Alpha 4 please visit the download page . Please carefully test this version and report any issues found on GitHub . Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be Beta 1, planned for 14 Aug 2025. The signatures for the release can be found in the manifest or on the Release Candidates page . Thank you for helping us make PHP better. 31 Jul 2025 PHP 8.4.11 Released! The PHP development team announces the immediate availability of PHP 8.4.11. This is a bug fix release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.11 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . 31 Jul 2025 PHP 8.3.24 Released! The PHP development team announces the immediate availability of PHP 8.3.24. This is a bug fix release. All PHP 8.3 users are encouraged to upgrade to this version. For source downloads of PHP 8.3.24 please visit our downloads page , Windows source and binaries can be found on windows.php.net/download/ . The list of changes is recorded in the ChangeLog . Older News Entries The PHP Foundation The PHP Foundation is a collective of people and organizations, united in the mission to ensure the long-term prosperity of the PHP language. Donate Upcoming conferences International PHP Conference Berlin 2026 Laravel Live Japan Conferences calling for papers Dutch PHP Conference 2026 User Group Events Special Thanks Social media @official_php @php@fosstodon.org @phpnet Copyright © 2001-2026 The PHP Group My PHP.net Contact Other PHP.net sites Privacy policy View Source ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/developer/index.html | 3. Buildbot Development — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 3. Buildbot Development 3.1. Development Quick-start 3.2. Submitting Pull Requests 3.3. General Documents 3.4. REST API 3.5. REST API Specification 3.6. Data API 3.7. Database 3.8. Database connectors API 3.9. Messaging and Queues 3.10. Classes 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 3. Buildbot Development View page source 3. Buildbot Development This chapter is the official repository for the collected wisdom of the Buildbot hackers. It is intended both for developers writing patches that will be included in Buildbot itself and for advanced users who wish to customize Buildbot. Note Public API Any API that is not documented in the official Buildbot documentation is considered internal and subject to change. If you would like it to be officially exposed, open a bug report on the Buildbot Github project . 3.1. Development Quick-start 3.1.1. Create a Buildbot Python Environment 3.1.2. Create a JavaScript Frontend Environment 3.2. Submitting Pull Requests 3.2.1. Guidelines 3.2.2. How to create a pull request 3.2.3. Local testing cheat sheet 3.3. General Documents 3.3.1. Master Organization 3.3.2. Buildbot Coding Style 3.3.3. Buildbot’s Test Suite 3.3.4. Configuration 3.3.5. Configuration in AngularJS 3.3.6. Writing Schedulers 3.3.7. Utilities 3.3.8. Build Result Codes 3.3.9. WWW Server 3.3.10. Javascript Data Module 3.3.11. Base web application 3.3.12. Authentication 3.3.13. Authorization 3.3.14. Master-Worker API 3.3.15. Master-Worker connection with MessagePack over WebSocket protocol 3.3.16. Claiming Build Requests 3.3.17. String Encodings 3.3.18. Metrics 3.3.19. Secrets 3.3.20. Secrets manager 3.3.21. Secrets providers 3.3.22. Statistics Service 3.3.23. How to package Buildbot plugins 3.4. REST API 3.4.1. Versions 3.4.2. Getting 3.4.3. Collections 3.4.4. Controlling 3.4.5. Authentication 3.5. REST API Specification 3.5.1. builder 3.5.2. buildrequest 3.5.3. build 3.5.4. buildset 3.5.5. build_data 3.5.6. change 3.5.7. changesource 3.5.8. codebase 3.5.9. codebase_branch 3.5.10. codebase_commit 3.5.11. forcescheduler 3.5.12. identifier 3.5.13. logchunk 3.5.14. log 3.5.15. master 3.5.16. patch 3.5.17. project 3.5.18. rootlink 3.5.19. scheduler 3.5.20. sourcedproperties 3.5.21. sourcestamp 3.5.22. spec 3.5.23. step 3.5.24. worker 3.5.25. test_result 3.5.26. test_result_set 3.5.27. Raw endpoints 3.6. Data API 3.6.1. Sections 3.6.2. Concrete Interfaces 3.6.3. Extending the Data API 3.6.4. Data Model 3.7. Database 3.7.1. Database Overview 3.7.2. Schema 3.7.3. Identifier 3.7.4. Writing Database Connector Methods 3.7.5. Modifying the Database Schema 3.7.6. Foreign key checking 3.7.7. Database Compatibility Notes 3.7.8. Testing migrations with real databases 3.8. Database connectors API 3.8.1. Buildsets connector 3.8.2. Buildrequests connector 3.8.3. Builders connector 3.8.4. Builds connector 3.8.5. Build data connector 3.8.6. Steps connector 3.8.7. Logs connector 3.8.8. Changes connector 3.8.9. Change sources connector 3.8.10. Schedulers connector 3.8.11. Source stamps connector 3.8.12. State connector 3.8.13. Users connector 3.8.14. Masters connector 3.8.15. Workers connector 3.9. Messaging and Queues 3.9.1. Overview 3.9.2. Connector API 3.9.3. Queue Schema 3.9.4. Message Schema 3.10. Classes 3.10.1. Builds 3.10.2. Workers 3.10.3. BuildFactory 3.10.4. Change Sources 3.10.5. RemoteCommands 3.10.6. BuildSteps 3.10.7. BaseScheduler 3.10.8. ForceScheduler 3.10.9. IRenderable 3.10.10. IProperties 3.10.11. IConfigurator 3.10.12. ResultSpecs 3.10.13. Protocols 3.10.14. WorkerManager 3.10.15. Logs 3.10.16. LogObservers 3.10.17. Authentication 3.10.18. Avatars 3.10.19. Web Server Classes Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://pt-br.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1KY84hKm_-by-YRr4vpnWKQpQpwSlqcHtHuJaVKw1bW8wItTohGpLUCnyGOFaKEl24B0RlP8zqhkc8lgjUOBrHeD_3-x2x1wAeaDTMaMg12_UywdHBUwoulr3RtwamghKKTr5Z0_NPtXeL | Facebook Facebook Email ou telefone Senha Esqueceu a conta? Criar nova conta Você está bloqueado temporariamente Você está bloqueado temporariamente Parece que você estava usando este recurso de forma indevida. Bloqueamos temporariamente sua capacidade de usar o recurso. Back Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Français (France) Deutsch Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Configurações Registro de atividades Meta © 2026 | 2026-01-13T09:30:34 |
https://aws.amazon.com/id/waf/ | Web Application Firewall - Perlindungan API Web - AWS WAF - AWS Lewati ke Konten Utama Filter: Semua English Hubungi kami AWS Marketplace Dukungan Akun saya Cari Filter: Semua Masuk ke konsol Buat akun AWS Web Application Firewall Gambaran Umum Fitur Harga Memulai Sumber Daya Lainnya Produk › Keamanan, Identitas, dan Kepatuhan › AWS WAF Dapatkan 10 juta permintaan kontrol bot umum per bulan dengan AWS Tingkat Free → AWS WAF Lindungi aplikasi web Anda dari eksploitasi umum Mulai AWS WAF Manfaat AWS WAF Hemat waktu dengan aturan terkelola Hemat waktu dengan aturan terkelola sehingga Anda dapat menghabiskan lebih banyak waktu untuk membuat aplikasi. Memantau, memblokir, atau membatasi kecepatan bot dengan mudah Pantau, blokir, atau batasi kecepatan bot umum dan pervasive (terus menerus aktif) dengan lebih mudah. Mengurangi langkah-langkah konfigurasi keamanan Percepat konfigurasi keamanan yang kompleks dengan antarmuka terkonsolidasi yang mengurangi kompleksitas dan langkah-langkah konfigurasi deployment keamanan hingga 80%. Visibilitas terpusat dan dapat ditindaklanjuti Antarmuka tunggal yang komprehensif menggabungkan fungsi keamanan inti dengan perlindungan partner khusus untuk meningkatkan visibilitas dan kontrol keamanan. Pendekatan terpadu ini mengubah data keamanan menjadi wawasan yang dapat ditindaklanjuti sehingga menghilangkan gesekan operasional dan mempercepat respons risiko. Perkuat postur keamanan Paket perlindungan yang telah dikonfigurasi sebelumnya memanfaatkan keahlian keamanan AWS untuk menyediakan templat perlindungan instan bagi industri dan tipe beban kerja tertentu, seperti API, aplikasi PHP, dan layanan web. Templat ini terus dioptimalkan untuk memastikan keamanan terkini tanpa memerlukan keahlian deployment yang mendalam. Dapatkan rekomendasi keamanan berkelanjutan untuk memperkuat postur keamanan secara keseluruhan. Mengapa AWS WAF? Dengan AWS WAF, Anda dapat membuat aturan keamanan yang mengontrol lalu lintas bot dan memblokir pola serangan umum, seperti injeksi SQL atau pembuatan skrip lintas situs (XSS). Putar Kasus penggunaan Filter lalu lintas web Buat aturan untuk memfilter permintaan web berdasarkan kondisi, seperti alamat IP, header dan isi HTTP, atau URI khusus. Pelajari selengkapnya tentang pembuatan aturan Cegah penipuan pengambilalihan akun Pantau akses yang tidak sah ke akun pengguna di halaman masuk aplikasi Anda menggunakan kredensial yang disusupi. Pelajari selengkapnya tentang pencegahan penipuan Perlindungan DDoS lapisan 7 otomatis Dirancang untuk terus memantau dan secara otomatis mengatasi peristiwa serangan Penolakan Layanan Terdistribusi (DDoS) pada lapisan aplikasi (lapisan 7) dalam hitungan detik. Implementasi keamanan yang cepat Luncurkan aplikasi baru dengan percaya diri melalui proses pengaturan orientasi terpandu yang efisien menggunakan antarmuka satu halaman untuk mengaktifkan pengaturan keamanan default yang telah dikonfigurasi sebelumnya yang disesuaikan dengan kebutuhan Anda. Perkuat postur keamanan Melalui paket aturan yang dikuratori oleh ahli, visibilitas terkonsolidasi, dan rekomendasi berkelanjutan, Anda mendapatkan perlindungan langsung untuk mengoptimalkan postur keamanan Anda. Mulai AWS WAF Mulai AWS WAF Jelajahi AWS WAF Hubungi ahli Hubungi kami Buat akun AWS Pelajari Apa itu AWS? Apa Itu Komputasi Cloud? Apa Itu AI Agentik? Hub Konsep Komputasi Cloud Keamanan AWS Cloud Apa yang Baru Blog Siaran Pers Sumber Daya Memulai Pelatihan Pusat Kepercayaan AWS Pustaka Solusi AWS Pusat Arsitektur FAQ Produk dan Teknis Laporan Analis Partner AWS Developer Pusat Builder SDK dan Alat .NET di AWS Python di AWS Java di AWS PHP di AWS JavaScript di AWS Bantuan Hubungi Kami Ajukan Tiket Dukungan AWS re:Post Pusat Pengetahuan Gambaran Umum Dukungan AWS Dapatkan Bantuan Ahli Aksesibilitas AWS Legal English Kembali ke atas Amazon merupakan Pemberi Kerja yang Memberikan Kesempatan yang Sama untuk semua orang: Minoritas/Wanita/Difabel/Veteran/Identitas Gender/Orientasi Seksual/Usia. x facebook linkedin instagram twitch youtube podcasts email Privasi Ketentuan situs Preferensi Cookie © 2026, Amazon Web Services, Inc. atau afiliasinya. Hak cipta dilindungi undang-undang. | 2026-01-13T09:30:34 |
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fawscommunity-asean%252Fcountermeasure-against-cve-2021-44228-with-aws-waf-4n3d%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/ja_jp/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-event-request-response.html | Lambda@Edge がリクエストとレスポンスで機能する仕組み - Amazon CloudFront Lambda@Edge がリクエストとレスポンスで機能する仕組み - Amazon CloudFront ドキュメント Amazon CloudFront デベロッパーガイド Lambda@Edge がリクエストとレスポンスで機能する仕組み CloudFront ディストリビューションを Lambda@Edge 関数に関連付けると、CloudFront エッジロケーションでリクエストとレスポンスがインターセプトされます。Lambda 関数は、次の CloudFront イベントの発生時に実行できます。 CloudFront がビューワーからリクエストを受信したとき (ビューワーリクエスト) CloudFront がリクエストをオリジンに転送する前 (オリジンリクエスト) CloudFront がオリジンからレスポンスを受信したとき (オリジンレスポンス) CloudFront がビューワーにレスポンスを返す前 (ビューワーレスポンス) AWS WAF を使用している場合、Lambda@Edge ビューワーリクエストは AWS WAF ルールの適用後に実行されます。 詳細については、「 リクエストとレスポンスを使用する 」および「 Lambda@Edge イベント構造 」を参照してください。 ブラウザで JavaScript が無効になっているか、使用できません。 AWS ドキュメントを使用するには、JavaScript を有効にする必要があります。手順については、使用するブラウザのヘルプページを参照してください。 ドキュメントの表記規則 Lambda@Edge でカスタマイズする Lambda@Edge の使用方法 このページは役に立ちましたか? - はい ページが役に立ったことをお知らせいただき、ありがとうございます。 お時間がある場合は、何が良かったかお知らせください。今後の参考にさせていただきます。 このページは役に立ちましたか? - いいえ このページは修正が必要なことをお知らせいただき、ありがとうございます。ご期待に沿うことができず申し訳ありません。 お時間がある場合は、ドキュメントを改善する方法についてお知らせください。 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/it_it/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-how-it-works.html | Nozioni di base sulle funzioni Lambda@Edge (console) - Amazon CloudFront Nozioni di base sulle funzioni Lambda@Edge (console) - Amazon CloudFront Documentazione Amazon CloudFront Guida per gli sviluppatori Le traduzioni sono generate tramite traduzione automatica. In caso di conflitto tra il contenuto di una traduzione e la versione originale in Inglese, quest'ultima prevarrà. Nozioni di base sulle funzioni Lambda@Edge (console) Con Lambda @Edge, puoi usare i CloudFront trigger per richiamare una funzione Lambda. Quando associ una CloudFront distribuzione a una funzione Lambda, CloudFront intercetta le richieste e le risposte nelle posizioni CloudFront periferiche ed esegue la funzione. Le funzioni Lambda possono migliorare la sicurezza o personalizzare le informazioni vicine ai visualizzatori per migliorare le prestazioni. L'elenco seguente fornisce una panoramica di base su come creare e utilizzare le funzioni Lambda con. CloudFront Panoramica: creazione e utilizzo di funzioni Lambda con CloudFront Crea una funzione Lambda nella regione Stati Uniti orientali (Virginia settentrionale). Salvare e pubblicare una versione numerata della funzione. Per apportare modifiche alla funzione è necessario modificare la versione $LATEST della funzione nella regione Stati Uniti orientali (N. Virginia). Quindi, prima di configurarlo per funzionare CloudFront, pubblicate una nuova versione numerata. Associate la funzione a un comportamento CloudFront di distribuzione e cache. Specificate quindi uno o più CloudFront eventi ( trigger ) che causano l'esecuzione della funzione. Ad esempio, è possibile creare un trigger per l'esecuzione della funzione quando si CloudFront riceve una richiesta da un visualizzatore. Quando si crea un trigger, Lambda crea repliche della funzione nelle posizioni AWS in tutto il mondo. Suggerimento Per ulteriori informazioni, consultate la creazione e l'aggiornamento delle funzioni , la struttura degli eventi e l'aggiunta di CloudFront trigger . Puoi inoltre trovare ulteriori idee e ottenere esempi di codice in Esempi di funzioni Lambda@Edge . Per un step-by-step tutorial, consultate il seguente argomento: Argomenti Tutorial: creazione di una funzione Lambda@Edge di base (console) JavaScript è disabilitato o non è disponibile nel tuo browser. Per usare la documentazione AWS, JavaScript deve essere abilitato. Consulta le pagine della guida del browser per le istruzioni. Convenzioni dei documenti Modi per usare Lambda@Edge Tutorial: funzione Lambda@Edge di base Questa pagina ti è stata utile? - Sì Grazie per averci comunicato che stiamo facendo un buon lavoro! Se hai un momento, ti invitiamo a dirci che cosa abbiamo fatto che ti è piaciuto così possiamo offrirti altri contenuti simili. Questa pagina ti è stata utile? - No Grazie per averci comunicato che questa pagina ha bisogno di essere modificata. Siamo spiacenti di non aver soddisfatto le tue esigenze. Se hai un momento, ti invitiamo a dirci come possiamo migliorare la documentazione. | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/578 | LLVM Weekly - #578, January 27th 2025 LLVM Weekly - #578, January 27th 2025 Welcome to the five hundred and seventy-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Voting in LLVM area team elections is now open and will close on 11th February. Yeoul Na announces that the preview of -fbounds-safety is now available . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Johannes Doerfert. Online sync-ups on the following topics: pointer authentication, OpenMP in LLVM, Flang, SPIR-V, RISC-V, LLVM embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Chris Lattner argued against the proposed commit access criteria RFC , on the basis that it makes it more difficult to get involved with LLVM. Tom Stellard proposes LLVM point releases every two weeks . Anton Korobeynikov is seeking mentors and project ideas for Google Summer of Code this year . Tom Stellard reminds us that the LLVM 20.x branch will be created on Tue January 28th . Meanwhile, Tobias Hieta noted that LLVM 19.1.8 won’t be released at this time as there are insufficient changes to be worthwhile . Proposals for 2025 EuroLLVM co-located workshops are open until Feb 1st . Mircea Trofin is gauging interest in LLVM :hearts: ML . jyn514 is seeking input on supporting a mechanism for marking certain stack frames as ‘unimportant’ when printing unwind information . David Spickett started an RFC discussion on how to encourage reviewers to merge on behalf of PR authors without commit access and plans to “1) Make the documentation more clear for PR authors and reviewers, with reference to the current way things are expected to happen. 2) Work on workflows to first add a comment on open, then, on a timer, find labelled and approved PRs and add comments to them with instructions for PR author and reviewers.”. LLVM commits The SPIRV backend graduated from experimental to official target. cda81b1 . LLVM’s policy on embedded copyright notices was documented. c59ede6 . Support was added for the arch15 SystemZ architecture. 8424bf20 . The SLPVectorizer gained support for non-power-of-2 (but still whole register) vectorisation for nodes other than stores and reductions. 5deb4ef . A TableGen backend was committed that generates SDNode descriptions. 6aeffcd . AArch64 build attribute support was implemented. ee99c4d . Quick start notes were written for Sandbox IR. e0ae889 . Assembler support for the Qualcomm Xqcilo (Large Offset Load Store) RISC-V extension was implemented. 163935a . The Static Data Splitter pass was implemented, using branch profile data to split static data (jump tables initially). de209fa . Clang commits Some of the implementation-defined keywords supported by Clang were documented. c248fc1 . AST support was added for SYCL kernel entry point functions. 8fb4230 . A bounds safety adoption guide was written, explaining how to trial -fbounds-safety using the previous implementation in an llvm-project fork. 6436089 . Predefined macros for integer constants were defined, matching those in GCC. 33ad474 . clang-reorder-fields will now move leading comments along with the field. fbd86d0 . Other project commits std::flat_multimap was implemented in libcxx. def50f7 . libcxx’s test infrastructure C++ standard filtering was improved. de5ff8a . mlir-cpu-runner was renamed to mlir-runner. eb206e9 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://www.iso.org/es/home/insights-news/resources/iso-22000-explained.html | ISO - ISO 22000 explained Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito ISO 22000 explained Why this guide? If you’ve searched: Who needs ISO 22000? What is ISO 22000 certification for? What is ISO 22002? ISO 22002 vs ISO 22000? You are not alone. Food safety systems can be difficult to navigate, especially when standards, schemes and buyer expectations overlap. This guide provides a clear and compact explanation of ISO 22000, how ISO 22002 fits in, and what organizations need to know before going further. 1. What ISO 22000 is ISO 22000 is the International Standard for food safety management systems. It helps organizations identify hazards, manage risks and demonstrate their ability to provide safe food consistently. It applies to the entire food chain, including primary production, food manufacturing, distribution, food service, packaging, equipment, and feed production. 2. Who uses certification for ISO 22000 Certification for ISO 22000 is voluntary. Organizations choose it when they need independent confirmation that their food safety management system meets the requirements of ISO 22000:2018. This is often requested by: • major retailers • manufacturers with strict supplier approval processes • international buyers • public procurement tenders ISO does not certify organizations. Certification is performed by independent certification bodies, which may be accredited. 3. What ISO 22002 is ISO 22002 provides the prerequisite programmes (PRPs) that support safe food production. These are the hygiene and operational conditions needed to prevent contamination and maintain a safe environment. Different parts cover different sectors: • ISO 22002-1: PRPs for food manufacturing • ISO 22002-4: PRPs for food packaging • ISO 22002-100: a unified PRP approach across sectors Together, ISO 22000 and ISO 22002 create a complete system: ISO 22000 is the management framework and ISO 22002 provides the operational foundations. 4. How ISO 22000 compares with other standards ISO 22000 vs ISO 9001 ISO 9001 focuses on quality management in all industries. ISO 22000 focuses specifically on food safety, including hazard control and supply chain communication. Highest food safety certifications Many recognized food safety schemes build on ISO 22000 and ISO 22002. For example, FSSC 22000 combines them into a scheme widely used by global food companies. 5. Practical ISO 22002 checklists Organizations can strengthen food safety practices immediately by focusing on basic PRPs: • daily, weekly and monthly cleaning schedules • temperature controls, recording and verification • separation of raw, processed and allergenic materials • incoming materials inspection • packaging controls and supplier checks • pest monitoring and facility hygiene • traceability and recall readiness These PRP foundations support the effective implementation of ISO 22000. Takeaway ISO 22000 provides a structured, internationally recognized approach to food safety management . ISO 22002 complements it with detailed hygiene and operational requirements . Together, they help organizations increase trust, meet buyer expectations, improve safety and strengthen their position in the global food chain. Explore International Standard ISO 22002-1:2025 Prerequisite programmes on food safety — Part 1: Food manufacturing Reference number ISO 22002-1:2025 Edition 1 2025-07 © ISO 2026 ISO 22002-1:2025 Prerequisite programmes on food safety Part 1: Food manufacturing International Standard ISO 22002-4:2025 Prerequisite programmes on food safety — Part 4: Food packaging manufacturing Reference number ISO 22002-4:2025 Edition 1 2025-07 © ISO 2026 ISO 22002-4:2025 Prerequisite programmes on food safety Part 4: Food packaging manufacturing International Standard ISO 22002-100:2025 Prerequisite programmes on food safety — Part 100: Requirements for the food, feed and packaging supply chain Reference number ISO 22002-100:2025 Edition 1 2025-07 © ISO 2026 ISO 22002-100:2025 Prerequisite programmes on food safety Part 100: Requirements for the food, feed and packaging supply chain Perspectivas y actualidad Resources ISO 22000 explained Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/582 | LLVM Weekly - #582, February 24th 2025 LLVM Weekly - #582, February 24th 2025 Welcome to the five hundred and eighty-second issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Registration is now open for EuroLLVM , with early bird registration ending on March 12th. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Amara Emerson, Johannes Doerfert. Online sync-ups on the following topics: pointer authentication, OpenMP, Flang, RISC-V, LLVM embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Britton Watson introduced themselves as the new assistant program director at the LLVM Foundation . Welcome! The Flang Liaison reports to the US Fortran Programming Language Standards Technical Committee (‘J3’) always serve as a great summary of recent progress, and the latest is no exception. Thank you Mark LeAir and any other contributors to the write-up. Lucile Rose Nihlen provided a detailed update on the LLVM premerge infrastructure . “The plan for the Beta test is to keep the current infrastructure in production while enabling PRs to also be tested on the new infrastructure. During beta testing, PRs will have a new Github Actions check labelled LLVM Premerge. Initially we will have these set to pass regardless of whether or not the build/test passes or fails, purely to test the infrastructure.” “student433” proposed supporting ‘pseudo’ targets in the Clang frontend , i.e. targets that has no backend support but where the target should be recognised by the frontend. Graham Hunter posted an RFC thread on supporting more early-exit loops in the vectoriser . LLVM commits LLVM’s developer policy was updated with new commit access requirements, with an explicit requirement that 3 committed patches are needed. ca0406d . Codegen support for Armv9.6-A’s compare-and-branch instructions was added to the AArch64 backend. 0fe0968c . The loop vectorizer gained initial support for vectorising literal struct return values. e0e67a6 . Mips now supports the llvm.readcyclecounter intrinsic. af1e2a3 . The __extendhfsf2 and __truncsfhf2 spellings of half<->float conversions are now used by default, with targets using different names (e.g. Arm) needing to override it. cc53913 . A new RISC-V pass removes excess ADDI that can be reassociated and folded into a load/store address. 26e3750 . The superword level parallelism (SLP) graph is now represented as a tree. 894935c . Assembler/disassembler support for the XRivosVizip RISC-V vendor extension was implemented. aef63c5 . Clang commits ClangIR generation for simple function bodies was upstreamed. f8bdbed . Clang learned to lower sincos[f|l] calls to llvm.sincos.* when -fno-math-errno is set. 7781e10 . An option was added to exclude the LLVM build from PGO training (with some disadvantages of using the it noted in the commit message). dca7306 . Code generation was implemented for HLSL cbuffer (constant buffer) declaration blocks. 19af858 . You can now specify a separate configuration for C vs C++ in clang-format and specify the language of a header file (C, C++, or Objective-C) via a comment. 0968df9 . Other project commits The fledgling llvm-bolt-binary-analysis-tool gained its first analysis in the form of an initial pac-ret gadget scanner. 850b4929 . Flang’s runtime library can now be built with LLVM_ENABLE_RUNTIMES=flang-rt . b55f751 . The size of the llvm-bolt binary was substantially reduced by only linking to supported targets. e235fcb . The list of supported compilers for libcxx was updated to reflect that Clang 17 is no longer supported after Clang the LLVM 20 branch. b22fc43 . LLD headers and libraries can now be installed via the new lld-headers and lld-libraries components in LLVM_DISTRIBUTION_COMPONENTS . 6273877 . MLIR MPI dialect to LLVM lowering was implemented. ab166d4 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://www.iso.org/es/home/insights-news/news/dossier-medias.html | ISO - Kit de prensa Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Kit de prensa ISO (International Organization for Standardization) is the world’s largest developer and publisher of International Standards. ISO is a network of national standards bodies of 175 countries, with a Central Secretariat in Geneva, Switzerland. ISO standards are voluntary and we don’t regulate or legislate, although countries may decide to adopt our standards as regulations or refer to them in legislation. We have more than 26119 standards in our portfolio. Our programme ranges from standards for traditional activities, such as agriculture and construction, through mechanical engineering, manufacturing and distribution, to transport, medical devices, the environment, safety, information and communication technologies and to standards for good practice and for services. Press contact press@iso.org Linkedin Twitter Facebook YouTube More than 100 of our members are from developing countries and every full member has the right to take part in standards development, no matter what the size or strength of their economy. Currently the ISO standards-development system comprise 829 technical bodies including 238 ISO technical committees. Read more about ISO Read more about how ISO develops standards Read more about the benefits of International Standards Our name From the Greek isos, meaning equal. Whatever the country, whatever the language, the short form of our name is always ISO. Our logo The ISO logo is a registered trademark and, unless we specifically authorise it, its use is not allowed . If you’d like to use our logo, contact our press team. Standards in action Learn about how International Standards work in the real world, and the benefits they bring to business, society and the environment. Annual reports A summary of the year's activities ISO in figures Our key achievements in figures at a single glance. ISO in brief An introduction to the ISO system, how it works and how ISO standards benefit the world. More introductory publications about ISO and standards Sergio Mujica ISO Secretary-General Sergio Mujica joined ISO as Secretary-General in July 2017, having spent 7 years at the World Custom’s Organization (WCO) as Deputy Secretary-General. Prior to working at the World Customs Organization, Mr Mujica spent 15 years working for the Government of Chile with the Ministry of Agriculture, the Ministry of Economic Affairs and as the Director General of Chile Customs Read Sergio's full profile Official Twitter account: @isosecgen Sergio Mujica, Secretary-General ( High resolution ) Central Secretariat premises in Geneva ( High resolution ) Perspectivas y actualidad Actualidad Kit de prensa Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-how-it-works.html | Get started with Lambda@Edge functions (console) - Amazon CloudFront Get started with Lambda@Edge functions (console) - Amazon CloudFront Documentation Amazon CloudFront Developer Guide Get started with Lambda@Edge functions (console) With Lambda@Edge, you can use CloudFront triggers to invoke a Lambda function. When you associate a CloudFront distribution with a Lambda function, CloudFront intercepts requests and responses at CloudFront edge locations and runs the function. Lambda functions can improve security or customize information close to your viewers to improve performance. The following list provides a basic overview of how to create and use Lambda functions with CloudFront. Overview: Creating and using Lambda functions with CloudFront Create a Lambda function in the US East (N. Virginia) Region. Save and publish a numbered version of the function. If you want to change the function, you must edit the $LATEST version of the function in the US East (N. Virginia) Region. Then, before you set it up to work with CloudFront, you publish a new numbered version. Associate the function with a CloudFront distribution and cache behavior. Then specify one or more CloudFront events ( triggers ) that cause the function to execute. For example, you can create a trigger for the function to execute when CloudFront receives a request from a viewer. When you create a trigger, Lambda creates replicas of the function at AWS locations around the world. Tip For more information, see creating and updating functions , the event structure , and adding CloudFront triggers . You can also find more ideas and get code samples in Lambda@Edge example functions . For a step-by-step tutorial, see the following topic: Topics Tutorial: Create a basic Lambda@Edge function (console) Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Ways to use Lambda@Edge Tutorial: Basic Lambda@Edge function Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/cmdline.html#create-worker | 2.7. Command-line Tool — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.7.1. buildbot 2.7.1.1. Administrator Tools 2.7.1.2. Developer Tools 2.7.1.3. Other Tools 2.7.1.4. .buildbot config directory 2.7.2. buildbot-worker 2.7.2.1. create-worker 2.7.2.2. start 2.7.2.3. restart 2.7.2.4. stop 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.7. Command-line Tool View page source 2.7. Command-line Tool This section describes command-line tools available after buildbot installation. The two main command-line tools are buildbot and buildbot-worker . The former handles a Buildbot master and the former handles a Buildbot worker. Every command-line tool has a list of global options and a set of commands which have their own options. One can run these tools in the following way: buildbot [global options] command [command options] buildbot-worker [global options] command [command options] The buildbot command is used on the master, while buildbot-worker is used on the worker. Global options are the same for both tools which perform the following actions: --help Print general help about available commands and global options and exit. All subsequent arguments are ignored. --verbose Set verbose output. --version Print current buildbot version and exit. All subsequent arguments are ignored. You can get help on any command by specifying --help as a command option: buildbot command --help You can also use manual pages for buildbot and buildbot-worker for quick reference on command-line options. The remainder of this section describes each buildbot command. See Command Line Index for a full list. 2.7.1. buildbot The buildbot command-line tool can be used to start or stop a buildmaster or buildbot, and to interact with a running buildmaster. Some of its subcommands are intended for buildmaster admins, while some are for developers who are editing the code that the buildbot is monitoring. 2.7.1.1. Administrator Tools The following buildbot sub-commands are intended for buildmaster administrators: create-master buildbot create-master -r {BASEDIR} This creates a new directory and populates it with files that allow it to be used as a buildmaster’s base directory. You will usually want to use the option -r option to create a relocatable buildbot.tac . This allows you to move the master directory without editing this file. upgrade-master buildbot upgrade-master {BASEDIR} This upgrades a previously created buildmaster’s base directory for a new version of buildbot master source code. This will copy the web server static files, and potentially upgrade the db. start buildbot start [--nodaemon] {BASEDIR} This starts a buildmaster which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. Additionally, the user can set the environment variable START_TIMEOUT to specify the amount of time the script waits for the master to start until it declares the operation as failure. restart buildbot restart [--nodaemon] {BASEDIR} Restart the buildmaster. This is equivalent to stop followed by start The option –nodaemon option has the same meaning as for start . stop buildbot stop {BASEDIR} This terminates the daemon (either buildmaster or worker) running in the given directory. The --clean option shuts down the buildmaster cleanly. With --no-wait option buildbot stop command will send buildmaster shutdown signal and will immediately exit, not waiting for complete buildmaster shutdown. sighup buildbot sighup {BASEDIR} This sends a SIGHUP to the buildmaster running in the given directory, which causes it to re-read its master.cfg file. checkconfig buildbot checkconfig {BASEDIR|CONFIG_FILE} This checks if the buildmaster configuration is well-formed and contains no deprecated or invalid elements. If no arguments are used or the base directory is passed as the argument the config file specified in buildbot.tac is checked. If the argument is the path to a config file then it will be checked without using the buildbot.tac file. cleanupdb buildbot cleanupdb {BASEDIR|CONFIG_FILE} [-q] This command is frontend for various database maintenance jobs: optimiselogs: This optimization groups logs into bigger chunks to apply higher level of compression. This script runs for as long as it takes to finish the job including the time needed to check master.cfg file. copy-db buildbot copy-db {DESTINATION_URL} {BASEDIR} [-q] This command copies all buildbot data from source database configured in the buildbot configuration file to the destination database. The URL of the destination database is specified on the command line. The destination database may have different type from the source database. The destination database must be empty. The script will initialize it in the same way as if a new Buildbot installation was created. Source database must be already upgraded to the current Buildbot version by the buildbot upgrade-master command. 2.7.1.2. Developer Tools These tools are provided for use by the developers who are working on the code that the buildbot is monitoring. try This lets a developer to ask the question What would happen if I committed this patch right now? . It runs the unit test suite (across multiple build platforms) on the developer’s current code, allowing them to make sure they will not break the tree when they finally commit their changes. The buildbot try command is meant to be run from within a developer’s local tree, and starts by figuring out the base revision of that tree (what revision was current the last time the tree was updated), and a patch that can be applied to that revision of the tree to make it match the developer’s copy. This (revision, patch) pair is then sent to the buildmaster, which runs a build with that SourceStamp . If you want, the tool will emit status messages as the builds run, and will not terminate until the first failure has been detected (or the last success). There is an alternate form which accepts a pre-made patch file (typically the output of a command like svn diff ). This --diff form does not require a local tree to run from. See try –diff concerning the --diff command option. For this command to work, several pieces must be in place: the Try_Jobdir or : Try_Userpass , as well as some client-side configuration. Locating the master The try command needs to be told how to connect to the try scheduler, and must know which of the authentication approaches described above is in use by the buildmaster. You specify the approach by using --connect=ssh or --connect=pb (or try_connect = 'ssh' or try_connect = 'pb' in .buildbot/options ). For the PB approach, the command must be given a option –master argument (in the form HOST : PORT ) that points to TCP port that you picked in the Try_Userpass scheduler. It also takes a option –username and option –passwd pair of arguments that match one of the entries in the buildmaster’s userpass list. These arguments can also be provided as try_master , try_username , and try_password entries in the .buildbot/options file. For the SSH approach, the command must be given option –host and option –username , to get to the buildmaster host. It must also be given option –jobdir , which points to the inlet directory configured above. The jobdir can be relative to the user’s home directory, but most of the time you will use an explicit path like ~buildbot/project/trydir . These arguments can be provided in .buildbot/options as try_host , try_username , try_password , and try_jobdir . If you need to use something different from the default ssh command for connecting to the remote system, you can use –ssh command line option or try_ssh in the configuration file. The SSH approach also provides a option –buildbotbin argument to allow specification of the buildbot binary to run on the buildmaster. This is useful in the case where buildbot is installed in a virtualenv on the buildmaster host, or in other circumstances where the buildbot command is not on the path of the user given by option –username . The option –buildbotbin argument can be provided in .buildbot/options as try_buildbotbin The following command line arguments are deprecated, but retained for backward compatibility: --tryhost is replaced by option –host --trydir is replaced by option –jobdir --master is replaced by option –masterstatus Likewise, the following .buildbot/options file entries are deprecated, but retained for backward compatibility: try_dir is replaced by try_jobdir masterstatus is replaced by try_masterstatus Waiting for results If you provide the option –wait option (or try_wait = True in .buildbot/options ), the buildbot try command will wait until your changes have either been proven good or bad before exiting. Unless you use the option –quiet option (or try_quiet=True ), it will emit a progress message every 60 seconds until the builds have completed. The SSH connection method does not support waiting for results. Choosing the Builders A trial build is performed on multiple Builders at the same time, and the developer gets to choose which Builders are used (limited to a set selected by the buildmaster admin with the TryScheduler ’s builderNames= argument). The set you choose will depend upon what your goals are: if you are concerned about cross-platform compatibility, you should use multiple Builders, one from each platform of interest. You might use just one builder if that platform has libraries or other facilities that allow better test coverage than what you can accomplish on your own machine, or faster test runs. The set of Builders to use can be specified with multiple option –builder arguments on the command line. It can also be specified with a single try_builders option in .buildbot/options that uses a list of strings to specify all the Builder names: try_builders = [ "full-OSX" , "full-win32" , "full-linux" ] If you are using the PB approach, you can get the names of the builders that are configured for the try scheduler using the get-builder-names argument: buildbot try --get-builder-names --connect = pb --master = ... --username = ... --passwd = ... Specifying the VC system The try command also needs to know how to take the developer’s current tree and extract the (revision, patch) source-stamp pair. Each VC system uses a different process, so you start by telling the try command which VC system you are using, with an argument like option –vc=cvs or option –vc=git . This can also be provided as try_vc in .buildbot/options . The following names are recognized: bzr cvs darcs hg git mtn p4 svn Finding the top of the tree Some VC systems (notably CVS and SVN) track each directory more-or-less independently, which means the try command needs to move up to the top of the project tree before it will be able to construct a proper full-tree patch. To accomplish this, the try command will crawl up through the parent directories until it finds a marker file. The default name for this marker file is .buildbot-top , so when you are using CVS or SVN you should touch .buildbot-top from the top of your tree before running buildbot try . Alternatively, you can use a filename like ChangeLog or README , since many projects put one of these files in their top-most directory (and nowhere else). To set this filename, use --topfile=ChangeLog , or set it in the options file with try_topfile = 'ChangeLog' . You can also manually set the top of the tree with --topdir=~/trees/mytree , or try_topdir = '~/trees/mytree' . If you use try_topdir , in a .buildbot/options file, you will need a separate options file for each tree you use, so it may be more convenient to use the try_topfile approach instead. Other VC systems which work on full projects instead of individual directories (Darcs, Mercurial, Git, Monotone) do not require try to know the top directory, so the option –try-topfile and option –try-topdir arguments will be ignored. If the try command cannot find the top directory, it will abort with an error message. The following command line arguments are deprecated, but retained for backward compatibility: --try-topdir is replaced by option –topdir --try-topfile is replaced by option –topfile Determining the branch name Some VC systems record the branch information in a way that try can locate it. For the others, if you are using something other than the default branch, you will have to tell the buildbot which branch your tree is using. You can do this with either the option –branch argument, or a try_branch entry in the .buildbot/options file. Determining the revision and patch Each VC system has a separate approach for determining the tree’s base revision and computing a patch. CVS try pretends that the tree is up to date. It converts the current time into a option -D time specification, uses it as the base revision, and computes the diff between the upstream tree as of that point in time versus the current contents. This works, more or less, but requires that the local clock be in reasonably good sync with the repository. SVN try does a svn status -u to find the latest repository revision number (emitted on the last line in the Status against revision: NN message). It then performs an svn diff -r NN to find out how your tree differs from the repository version, and sends the resulting patch to the buildmaster. If your tree is not up to date, this will result in the try tree being created with the latest revision, then backwards patches applied to bring it back to the version you actually checked out (plus your actual code changes), but this will still result in the correct tree being used for the build. bzr try does a bzr revision-info to find the base revision, then a bzr diff -r$base.. to obtain the patch. Mercurial hg parents --template '{node}\n' emits the full revision id (as opposed to the common 12-char truncated) which is a SHA1 hash of the current revision’s contents. This is used as the base revision. hg diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Mercurial will use. Perforce try does a p4 changes -m1 ... to determine the latest changelist and implicitly assumes that the local tree is synced to this revision. This is followed by a p4 diff -du to obtain the patch. A p4 patch differs slightly from a normal diff. It contains full depot paths and must be converted to paths relative to the branch top. To convert the following restriction is imposed. The p4base (see P4Source ) is assumed to be //depot Darcs try does a darcs changes --context to find the list of all patches back to and including the last tag that was made. This text file (plus the location of a repository that contains all these patches) is sufficient to re-create the tree. Therefore the contents of this context file are the revision stamp for a Darcs-controlled source tree. It then does a darcs diff -u to compute the patch relative to that revision. Git git branch -v lists all the branches available in the local repository along with the revision ID it points to and a short summary of the last commit. The line containing the currently checked out branch begins with “* “ (star and space) while all the others start with “ “ (two spaces). try scans for this line and extracts the branch name and revision from it. Then it generates a diff against the base revision. Todo I’m not sure if this actually works the way it’s intended since the extracted base revision might not actually exist in the upstream repository. Perhaps we need to add a –remote option to specify the remote tracking branch to generate a diff against. Monotone mtn automate get_base_revision_id emits the full revision id which is a SHA1 hash of the current revision’s contents. This is used as the base revision. mtn diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Monotone will use. patch information You can provide the option –who=dev to designate who is running the try build. This will add the dev to the Reason field on the try build’s status web page. You can also set try_who = dev in the .buildbot/options file. Note that option –who=dev will not work on version 0.8.3 or earlier masters. Similarly, option –comment=COMMENT will specify the comment for the patch, which is also displayed in the patch information. The corresponding config-file option is try_comment . Sending properties You can set properties to send with your change using either the option –property=key=value option, which sets a single property, or the option –properties=key1=value1,key2=value2… option, which sets multiple comma-separated properties. Either of these can be specified multiple times. Note that the option –properties option uses commas to split on properties, so if your property value itself contains a comma, you’ll need to use the option –property option to set it. try –diff Sometimes you might have a patch from someone else that you want to submit to the buildbot. For example, a user may have created a patch to fix some specific bug and sent it to you by email. You’ve inspected the patch and suspect that it might do the job (and have at least confirmed that it doesn’t do anything evil). Now you want to test it out. One approach would be to check out a new local tree, apply the patch, run your local tests, then use buildbot try to run the tests on other platforms. An alternate approach is to use the buildbot try --diff form to have the buildbot test the patch without using a local tree. This form takes a option –diff argument which points to a file that contains the patch you want to apply. By default this patch will be applied to the TRUNK revision, but if you give the optional option –baserev argument, a tree of the given revision will be used as a starting point instead of TRUNK. You can also use buildbot try --diff=- to read the patch from stdin . Each patch has a patchlevel associated with it. This indicates the number of slashes (and preceding pathnames) that should be stripped before applying the diff. This exactly corresponds to the option -p or option –strip argument to the patch utility. By default buildbot try --diff uses a patchlevel of 0, but you can override this with the option -p argument. When you use option –diff , you do not need to use any of the other options that relate to a local tree, specifically option –vc , option –try-topfile , or option –try-topdir . These options will be ignored. Of course you must still specify how to get to the buildmaster (with option –connect , option –tryhost , etc). 2.7.1.3. Other Tools These tools are generally used by buildmaster administrators. sendchange This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource ( PBChangeSource ) running in the buildmaster (by being set in c['change_source'] ). buildbot sendchange --master {MASTERHOST}:{PORT} --auth {USER}:{PASS} --who {USER} {FILENAMES..} The option –auth option specifies the credentials to use to connect to the master, in the form user:pass . If the password is omitted, then sendchange will prompt for it. If both are omitted, the old default (username “change” and password “changepw”) will be used. Note that this password is well-known, and should not be used on an internet-accessible port. The option –master and option –username arguments can also be given in the options file (see .buildbot config directory ). There are other (optional) arguments which can influence the Change that gets submitted: --branch (or option branch ) This provides the (string) branch specifier. If omitted, it defaults to None , indicating the default branch . All files included in this Change must be on the same branch. --category (or option category ) This provides the (string) category specifier. If omitted, it defaults to None , indicating no category . The category property can be used by schedulers to filter what changes they listen to. --project (or option project ) This provides the (string) project to which this change applies, and defaults to ‘’. The project can be used by schedulers to decide which builders should respond to a particular change. --repository (or option repository ) This provides the repository from which this change came, and defaults to '' . --revision This provides a revision specifier, appropriate to the VC system in use. --revision_file This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument. --property This parameter is used to set a property on the Change generated by sendchange . Properties are specified as a name : value pair, separated by a colon. You may specify many properties by passing this parameter multiple times. --comments This provides the change comments as a single argument. You may want to use option –logfile instead. --logfile This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin. --encoding Specifies the character encoding for all other parameters, defaulting to 'utf8' . --vc Specifies which VC system the Change is coming from, one of: cvs , svn , darcs , hg , bzr , git , mtn , or p4 . Defaults to None . user Note that in order to use this command, you need to configure a CommandlineUserManager instance in your master.cfg file, which is explained in Users Options . This command allows you to manage users in buildbot’s database. No extra requirements are needed to use this command, aside from the Buildmaster running. For details on how Buildbot manages users, see Users . --master The user command can be run virtually anywhere provided a location of the running buildmaster. The option –master argument is of the form MASTERHOST : PORT . --username PB connection authentication that should match the arguments to CommandlineUserManager . --passwd PB connection authentication that should match the arguments to CommandlineUserManager . --op There are four supported values for the option –op argument: add , update , remove , and get . Each are described in full in the following sections. --bb_username Used with the option –op=update option, this sets the user’s username for web authentication in the database. It requires option –bb_password to be set along with it. --bb_password Also used with the option –op=update option, this sets the password portion of a user’s web authentication credentials into the database. The password is first encrypted prior to storage for security reasons. --ids When working with users, you need to be able to refer to them by unique identifiers to find particular users in the database. The option –ids option lets you specify a comma separated list of these identifiers for use with the user command. The option –ids option is used only when using option –op=remove or option –op=get . --info Users are known in buildbot as a collection of attributes tied together by some unique identifier (see Users ). These attributes are specified in the form {TYPE}={VALUE} when using the option –info option. These {TYPE}={VALUE} pairs are specified in a comma separated list, so for example: --info=svn=jdoe,git='John Doe <joe@example.com>' The option –info option can be specified multiple times in the user command, as each specified option will be interpreted as a new user. Note that option –info is only used with option –op=add or with option –op=update , and whenever you use option –op=update you need to specify the identifier of the user you want to update. This is done by prepending the option –info arguments with {ID:} . If we were to update 'jschmo' from the previous example, it would look like this: --info=jdoe:git='Joe Doe <joe@example.com>' Note that option –master , option –username , option –passwd , and option –op are always required to issue the user command. The option –master , option –username , and option –passwd options can be specified in the option file with keywords user_master , user_username , and user_passwd , respectively. If user_master is not specified, then option –master from the options file will be used instead. Below are examples of how each command should look. Whenever a user command is successful, results will be shown to whoever issued the command. For option –op=add : buildbot user --master={MASTERHOST} --op=add \ --username={USER} --passwd={USERPW} \ --info={TYPE}={VALUE},... For option –op=update : buildbot user --master={MASTERHOST} --op=update \ --username={USER} --passwd={USERPW} \ --info={ID}:{TYPE}={VALUE},... For option –op=remove : buildbot user --master={MASTERHOST} --op=remove \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... For option –op=get : buildbot user --master={MASTERHOST} --op=get \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... A note on option –op=update : when updating the option –bb_username and option –bb_password , the option –info doesn’t need to have additional {TYPE}={VALUE} pairs to update and can just take the {ID} portion. 2.7.1.4. .buildbot config directory Many of the buildbot tools must be told how to contact the buildmaster that they interact with. This specification can be provided as a command-line argument, but most of the time it will be easier to set them in an options file. The buildbot command will look for a special directory named .buildbot , starting from the current directory (where the command was run) and crawling upwards, eventually looking in the user’s home directory. It will look for a file named options in this directory, and will evaluate it as a Python script, looking for certain names to be set. You can just put simple name = 'value' pairs in this file to set the options. For a description of the names used in this file, please see the documentation for the individual buildbot sub-commands. The following is a brief sample of what this file’s contents could be. # for status-reading tools masterstatus = 'buildbot.example.org:12345' # for 'sendchange' or the debug port master = 'buildbot.example.org:18990' Note carefully that the names in the options file usually do not match the command-line option name. master Equivalent to option –master for sendchange . It is the location of the pb.PBChangeSource for `sendchange . username Equivalent to option –username for the sendchange command. branch Equivalent to option –branch for the sendchange command. category Equivalent to option –category for the sendchange command. try_connect Equivalent to option –connect , this specifies how the try command should deliver its request to the buildmaster. The currently accepted values are ssh and pb . try_builders Equivalent to option –builders , specifies which builders should be used for the try build. try_vc Equivalent to option –vc for try , this specifies the version control system being used. try_branch Equivalent to option –branch , this indicates that the current tree is on a non-trunk branch. try_topdir try_topfile Use try_topdir , equivalent to option –try-topdir , to explicitly indicate the top of your working tree, or try_topfile , equivalent to option –try-topfile to name a file that will only be found in that top-most directory. try_host try_username try_dir When try_connect is ssh , the command will use try_host for option –tryhost , try_username for option –username , and try_dir for option –trydir . Apologies for the confusing presence and absence of ‘try’. try_username try_password try_master Similarly, when try_connect is pb , the command will pay attention to try_username for option –username , try_password for option –passwd , and try_master for option –master . try_wait masterstatus try_wait and masterstatus (equivalent to option –wait and master , respectively) are used to ask the try command to wait for the requested build to complete. 2.7.2. buildbot-worker buildbot-worker command-line tool is used for worker management only and does not provide any additional functionality. One can create, start, stop and restart the worker. 2.7.2.1. create-worker This creates a new directory and populates it with files that let it be used as a worker’s base directory. You must provide several arguments, which are used to create the initial buildbot.tac file. The option -r option is advisable here, just like for create-master . buildbot-worker create-worker -r {BASEDIR} {MASTERHOST}:{PORT} {WORKERNAME} {PASSWORD} The create-worker options are described in Worker Options . 2.7.2.2. start This starts a worker which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . buildbot-worker start [--nodaemon] BASEDIR The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. 2.7.2.3. restart buildbot-worker restart [--nodaemon] BASEDIR This restarts a worker which is already running. It is equivalent to a stop followed by a start . The option –nodaemon option has the same meaning as for start . 2.7.2.4. stop This terminates the daemon worker running in the given directory. buildbot stop BASEDIR Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://www.iso.org/es/contents/data/sdg/SDG16.html | ISO - Peace, Justice and Strong Institutions Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito ODS 16 Peace, Justice and Strong Institutions Objetivos de Desarrollo Sostenible ODS 01 - No Poverty ODS 02 - Zero Hunger ODS 03 - Good Health and Well-being ODS 04 - Quality Education ODS 05 - Gender Equality ODS 06 - Clean Water and Sanitation ODS 07 - Affordable and Clean Energy ODS 08 - Decent Work and Economic Growth ODS 09 - Industry, Innovation and Infrastructure ODS 10 - Reduced Inequalities ODS 11 - Sustainable Cities and Communities ODS 12 - Responsible Consumption and Production ODS 13 - Climate Action ODS 14 - Life Below Water ODS 15 - Life on Land ODS 16 - Peace, Justice and Strong Institutions ODS 17 - Partnerships for the Goals Goal 16: Peace, Justice and Strong Institutions Promote peaceful and inclusive societies for sustainable development, provide access to justice for all and build effective, accountable and inclusive institutions at all levels Sustainable Development Goal 16 (SDG 16) aims to promote peaceful and inclusive societies, provide access to justice for all, and build effective, accountable institutions. This goal is fundamental to creating stable, fair, and prosperous societies. At ISO, we are committed to supporting SDG 16 through our standards, which provide frameworks and solutions that enhance governance, promote transparency, and support ethical practices. How ISO Standards Support SDG 16 ISO standards play a vital role in supporting SDG 16 by addressing key aspects of organizational governance, transparency, and anti-corruption practices. Our standards help organizations implement ethical practices, improve accountability, and enhance their overall governance structures. Here are some of the relevant standards: ISO 37001: Anti-bribery management systems — Requirements with guidance for use Provides a framework for organizations to establish, implement, maintain, and improve an anti-bribery management system. Helps organizations prevent, detect, and address bribery, promoting ethical business practices and supporting the fight against corruption. ISO 37301: Compliance management systems — Requirements with guidance for use Specifies requirements for establishing, developing, implementing, evaluating, maintaining, and improving an effective compliance management system within an organization. Supports organizations in meeting their compliance obligations and managing compliance risks, contributing to more transparent and accountable institutions. Take Action: Implement ISO Standards to Support SDG 16 Interested in learning how your organization can contribute to promoting peace, justice, and strong institutions through the implementation of ISO standards? Download our comprehensive guide to understand the role of ISO standards in achieving SDG 16 and other global goals. Together, we can work towards more peaceful, just, and inclusive societies. ISO and IEC International Standards for policy makers This leaflet summarizes the information found in the brochure "Using and referencing ISO and IEC standards to support public policy". It briefly describes the advantages and benefits of using ISO and IEC International Standards to support policy initiatives. See also www.iso.org/policy. ISO 37001 Anti-bribery management systems This free brochure gives an overview of the standard and how it can impact your business. Normas ODS Objetivo 16: Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://penneo.com/da/finance/ | Finans og bank - Penneo Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Brancher Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus LOG PÅ Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ BOOK ET MØDE GRATIS PRØVEPERIODE DA EN NO FR NL Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus BOOK ET MØDE GRATIS PRØVEPERIODE LOG PÅ DA EN NO FR NL Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ Slip for de gentagne manuelle opgaver og gør hverdagen enklere med digital signering Med Penneo kan finansielle institutioner slippe for tidskrævende papirarbejde og manuelle underskriftsprocesser. Det reducerer omkostningerne, effektiviserer arbejdsgangene og skaber en bedre oplevelse for både medarbejdere og kunder. OPDAG PENNEO Hvordan påvirker forældede processer den finansielle sektor? Forældede processer i den finansielle sektor er ofte tidskrævende og flytter medarbejdernes fokus væk fra kunderne og over på administrative opgaver. Det skaber ineffektivitet, kan øge driftsomkostningerne og forringe den samlede kundeoplevelse. Digitaliseringen går stærkt – og traditionelle, manuelle underskriftsprocesser kan ikke længere følge med. De bremser effektiviteten, øger risikoen for fejl og gør det vanskeligt at følge med i en branche i hastig udvikling. Se, hvordan Penneo kan hjælpe dig Maksimer effektiviteten ved at integrere Penneo med dine værktøjer Ved at integrere Penneo med dine eksisterende værktøjer kan du optimere arbejdsgange og øge effektiviteten. Penneo tilbyder forudbyggede integrationer med software som ByteLab, M-Files, DCR Solutions og ELO Digital Office . Derudover kan du oprette tilpassede integrationer, der er skræddersyet til dine specifikke behov, ved hjælp af Penneos åbne API. Se alle integrationer Spar tid ved at automatisere dokumentunderskrift Penneo strømliner og sikrer dokumentunderskrivelsesprocesser ved at: Tilbyder juridisk bindende elektroniske signaturer – Du kan bruge MitID eller svensk BankID til avancerede elektroniske signaturer og dit pas, norsk BankID, itsme® eller .beID til kvalificerede elektroniske signaturer. Automatisere arbejdsgange – Gør det let at indsamle underskrifter på forsikringsaftaler, pensionsordninger, låneaftaler og andre forretningskontrakter. Sikre datasikkerhed og compliance – Opbevar underskrevne dokumenter sikkert og beskyt dem mod uautoriseret adgang. Se alle funktioner Moderniser din drift og frigør tid med Penneo Med integrationer , automatiserede signeringsflows og digitale signaturer, der lever op til eIDAS-forordningen, kan du reducere manuelle opgaver, øge nøjagtigheden og frigøre tid til det, der virkelig tæller. Penneo overholder GDPR, har ISO 27001- og 27701-certificeringer og anvender kryptering for at sikre data- og dokumentsikkerheden. Med Penneo kan du oprette kvalificerede elektroniske signaturer (QES) ved hjælp af pas, norsk BankID, itsme® eller .beID, samt avancerede elektroniske signaturer (AdES) med MitID, MitID Erhverv eller svensk BankID. Reducer risikoen for fejl og arbejd mere effektivt med ensartede underskriftsprocesser og fuldt overblik via detaljerede aktivitetslogfiler. Gør det nemt for dine kunder at underskrive dokumenter digitalt, når og hvor det passer dem – og skab en smidigere og mere personlig oplevelse. Tiltræk nye talenter ved at skabe en moderne arbejdsplads. Digitale værktøjer fremmer innovation og produktivitet og gør samtidig din organisation mere attraktiv for dygtige unge fagfolk. Se, hvordan Penneo fungerer Betroet af over 3.000 virksomheder Opdag, hvordan Penneo kan hjælpe dig BOOK ET MØDE Produkter Penneo Sign Priser Integrationer Åben API Validator Hvorfor Penneo Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Ressourcer Vidensunivers Trust Center Produktopdateringer SUPPORT SIGN Hjælpecenter KYC Hjælpecenter Systemstatus Virksomhed Om os Karriere Privatlivspolitik Vilkår Brug af cookies Accessibility Statement Whistleblower Policy Kontakt os PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
http://pecl.php.net/package/dio | PECL :: Package :: dio Login | Packages | Support | Bugs S earch for in the Packages This site (using Google) Developers Developer mailing list SVN commits mailing list Home News Documentation: Support Downloads: Browse Packages Search Packages Download Statistics Top Level :: System :: dio dio Package Information Summary Direct I/O functions Maintainers Melanie Rhianna Lewis (lead) [ details ] Remi Collet (lead) [ details ] License PHP-3.01 Description PHP supports the direct io functions as described in the Posix Standard (Section 6) for performing I/O functions at a lower level than the C-Language stream I/O functions (fopen(), fread(),..). DIO provides functions and stream wrappers which provide raw and serial low level IO support. The use of the DIO functions should be considered only when direct control of a device is needed. In all other cases, the standard filesystem functions are more than adequate. [ Latest Tarball ] [ Changelog ] [ View Statistics ] [ Browse Source ] [ Package Bugs ] Available Releases Version State Release Date Downloads 0.3.0 stable 2024-02-22 dio-0.3.0.tgz (22.1kB) DLL [ Changelog ] 0.3.0RC1 beta 2024-01-25 dio-0.3.0RC1.tgz (22.0kB) [ Changelog ] 0.2.2 beta 2024-01-23 dio-0.2.2.tgz (36.4kB) [ Changelog ] 0.2.1 beta 2022-01-25 dio-0.2.1.tgz (36.1kB) DLL [ Changelog ] 0.2.0 beta 2020-04-16 dio-0.2.0.tgz (36.5kB) DLL [ Changelog ] 0.1.0 beta 2017-03-25 dio-0.1.0.tgz (36.1kB) DLL [ Changelog ] 0.0.9 beta 2016-12-13 dio-0.0.9.tgz (35.8kB) DLL [ Changelog ] 0.0.8 beta 2016-12-13 dio-0.0.8.tgz (35.8kB) DLL [ Changelog ] 0.0.7 beta 2013-02-19 dio-0.0.7.tgz (19.1kB) DLL [ Changelog ] 0.0.6 beta 2012-06-30 dio-0.0.6.tgz (18.4kB) [ Changelog ] 0.0.5 beta 2012-02-17 dio-0.0.5.tgz (18.3kB) [ Changelog ] 0.0.4RC4 beta 2010-02-10 dio-0.0.4RC4.tgz (17.9kB) [ Changelog ] 0.0.2 beta 2008-12-07 dio-0.0.2.tgz (5.6kB) [ Changelog ] Dependencies Release 0.3.0: PHP Version: PHP 8.0.0 or newer PEAR Package: PEAR 1.10.0 or newer Release 0.3.0RC1: PHP Version: PHP 8.0.0 or newer PEAR Package: PEAR 1.10.0 or newer Release 0.2.2: PHP Version: PHP 5.3.3 or newer PEAR Package: PEAR 1.9.4 or newer Dependencies for older releases can be found on the release overview page. PRIVACY POLICY | CREDITS Copyright © 2001-2026 The PHP Group All rights reserved. Last updated: Wed Sep 03 10:50:24 2025 UTC Bandwidth and hardware provided by: pair Networks | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions_create-policies.html | Creating roles and attaching policies (console) - AWS Identity and Access Management Creating roles and attaching policies (console) - AWS Identity and Access Management Documentation AWS Identity and Access Management User Guide Example 1: Configuring a user as a database administrator (console) Example 2: Configuring a user as a network administrator (console) Creating roles and attaching policies (console) Several of the previously listed policies grant the ability to configure AWS services with roles that enable those services to perform operations on your behalf. The job function policies either specify exact role names that you must use or at least include a prefix that specifies the first part of the name that can be used. To create one of these roles, perform the steps in the following procedure. To create a role for an AWS service (IAM console) Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/ . In the navigation pane of the IAM console, choose Roles , and then choose Create role . For Trusted entity type , choose AWS service . For Service or use case , choose a service, and then choose the use case. Use cases are defined by the service to include the trust policy that the service requires. Choose Next . For Permissions policies , the options depend on the use case that you selected: If the service defines the permissions for the role, you can't select permissions policies. Select from a limited set of permission polices. Select from all permission policies. Select no permissions policies, create the policies after the role is created, and then attach the policies to the role. (Optional) Set a permissions boundary . This is an advanced feature that is available for service roles, but not service-linked roles. Open the Set permissions boundary section, and then choose Use a permissions boundary to control the maximum role permissions . IAM includes a list of the AWS managed and customer-managed policies in your account. Select the policy to use for the permissions boundary. Choose Next . For Role name , the options depend on the service: If the service defines the role name, you can't edit the role name. If the service defines a prefix for the role name, you can enter an optional suffix. If the service doesn't define the role name, you can name the role. Important When you name a role, note the following: Role names must be unique within your AWS account, and can't be made unique by case. For example, don't create roles named both PRODROLE and prodrole . When a role name is used in a policy or as part of an ARN, the role name is case sensitive, however when a role name appears to customers in the console, such as during the sign-in process, the role name is case insensitive. You can't edit the name of the role after it's created because other entities might reference the role. (Optional) For Description , enter a description for the role. (Optional) To edit the use cases and permissions for the role, in the Step 1: Select trusted entities or Step 2: Add permissions sections, choose Edit . (Optional) To help identify, organize, or search for the role, add tags as key-value pairs. For more information about using tags in IAM, see Tags for AWS Identity and Access Management resources in the IAM User Guide . Review the role, and then choose Create role . Example 1: Configuring a user as a database administrator (console) This example shows the steps required to configure Alice, an IAM user, as a Database Administrator . You use the information in first row of the table in that section and allow the user to enable Amazon RDS monitoring. You attach the DatabaseAdministrator policy to Alice's IAM user so that they can manage the Amazon database services. That policy also allows Alice to pass a role called rds-monitoring-role to the Amazon RDS service that allows the service to monitor the Amazon RDS databases on their behalf. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/ . Choose Policies , type database in the search box, and then press enter. Select the radio button for the DatabaseAdministrator policy, choose Actions , and then choose Attach . In the list of entities, select Alice and then choose Attach policy . Alice now can administer AWS databases. However, to allow Alice to monitor those databases, you must configure the service role. In the navigation pane of the IAM console, choose Roles , and then choose Create role . Choose the AWS Service role type, and then choose Amazon RDS . Choose the Amazon RDS Role for Enhanced Monitoring use case. Amazon RDS defines the permissions for your role. Choose Next: Review to continue. The role name must be one of those specified by the DatabaseAdministrator policy that Alice now has. One of those is rds-monitoring-role . Enter that for the Role name . (Optional) For Role description , enter a description for the new role. After you review the details, choose Create role . Alice can now enable RDS Enhanced Monitoring in the Monitoring section of the Amazon RDS console. For example, they might do this when they create a DB instance, create a read replica, or modify a DB instance. They must enter the role name they created (rds-monitoring-role) in the Monitoring Role box when they set Enable Enhanced Monitoring to Yes . Example 2: Configuring a user as a network administrator (console) This example shows the steps required to configure Jorge, an IAM user, as a Network Administrator . It uses the information in the table in that section to allow Jorge to monitor IP traffic going to and from a VPC. It also allows Jorge to capture that information in the logs in CloudWatch Logs. You attach the NetworkAdministrator policy to Jorge's IAM user so that they can configure AWS network resources. That policy also allows Jorge to pass a role whose name begins with flow-logs* to Amazon EC2 when you create a flow log. In this scenario, unlike Example 1, there isn't a predefined service role type, so you must perform a few steps differently. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/ . In the navigation pane, choose Policies and then enter network in the search box, and then press enter. Select the radio button next to NetworkAdministrator policy, choose Actions , and then choose Attach . In the list of users, select the checkbox next to Jorge and then choose Attach policy . Jorge can now administer AWS network resources. However, to enable monitoring of IP traffic in your VPC, you must configure the service role. Because the service role you need to create doesn't have a predefined managed policy, you must first create it. In the navigation pane, choose Policies , then choose Create policy . In the Policy editor section, choose the JSON option and copy the text from the following JSON policy document. Paste this text into the JSON text box. JSON { "Version":"2012-10-17", "Statement": [ { "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:PutLogEvents", "logs:DescribeLogGroups", "logs:DescribeLogStreams" ], "Effect": "Allow", "Resource": "*" } ] } Resolve any security warnings, errors, or general warnings generated during policy validation , and then choose Next . Note You can switch between the Visual and JSON editor options any time. However, if you make changes or choose Next in the Visual editor, IAM might restructure your policy to optimize it for the visual editor. For more information, see Policy restructuring . On the Review and create page, type vpc-flow-logs-policy-for-service-role for the policy name. Review the Permissions defined in this policy to see the permissions granted by your policy, and then choose Create policy to save your work. The new policy appears in the list of managed policies and is ready to attach. In the navigation pane of the IAM console, choose Roles , and then choose Create role . Choose the AWS Service role type, and then choose Amazon EC2 . Choose the Amazon EC2 use case. On the Attach permissions policies page, choose the policy you created earlier, vpc-flow-logs-policy-for-service-role , and then choose Next: Review . The role name must be permitted by the NetworkAdministrator policy that Jorge now has. Any name that begins with flow-logs- is allowed. For this example, enter flow-logs-for-jorge for the Role name . (Optional) For Role description , enter a description for the new role. After you review the details, choose Create role . Now you can configure the trust policy required for this scenario. On the Roles page, choose the flow-logs-for-jorge role (the name, not the checkbox). On the details page for your new role, choose the Trust relationships tab, and then choose Edit trust relationship . Change the "Service" line to read as follows, replacing the entry for ec2.amazonaws.com : "Service": "vpc-flow-logs.amazonaws.com" Jorge can now create flow logs for a VPC or subnet in the Amazon EC2 console. When you create the flow log, specify the flow-logs-for-jorge role. That role has the permissions to create the log and write data to it. Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions AWS managed policies for job functions Global condition keys Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
https://phproundtable.com/show/checking-in-with-php-and-hhvm-internals | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 31: Checking in with PHP and HHVM internals Panelists: Julien Pauli Sara Golemon Bob Weinand Nikita Popov October 6 2015 We chatting with some PHP & HHVM internals folks to learn what's been going on in the world of internals. About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-permissions.html | Set up IAM permissions and roles for Lambda@Edge - Amazon CloudFront Set up IAM permissions and roles for Lambda@Edge - Amazon CloudFront Documentation Amazon CloudFront Developer Guide IAM permissions required to associate Lambda@Edge functions with CloudFront distributions Function execution role for service principals Service-linked roles for Lambda@Edge Set up IAM permissions and roles for Lambda@Edge To configure Lambda@Edge, you must have the following IAM permissions and roles for AWS Lambda: IAM permissions – These permissions allow you to create your Lambda function and associate it with your CloudFront distribution. A Lambda function execution role (IAM role) – The Lambda service principals assume this role to execute your function. Service-linked roles for Lambda@Edge – The service-linked roles allow specific AWS services to replicate Lambda functions to AWS Regions and to enable CloudWatch to use CloudFront log files. IAM permissions required to associate Lambda@Edge functions with CloudFront distributions In addition to the IAM permissions that you need for Lambda, you need the following permissions to associate Lambda functions with CloudFront distributions: lambda:GetFunction – Grants permission to get configuration information for your Lambda function and a presigned URL to download a .zip file that contains the function. lambda:EnableReplication* – Grants permission to the resource policy so that the Lambda replication service can get the function code and configuration. lambda:DisableReplication* – Grants permission to the resource policy so that the Lambda replication service can delete the function. Important You must add the asterisk ( * ) at the end of the lambda:EnableReplication * and lambda:DisableReplication * actions. For the resource, specify the ARN of the function version that you want to execute when a CloudFront event occurs, such as the following example: arn:aws:lambda:us-east-1:123456789012:function: TestFunction :2 iam:CreateServiceLinkedRole – Grants permission to create a service-linked role that Lambda@Edge uses to replicate Lambda functions in CloudFront. After you configure Lambda@Edge for the first time, the service-linked role is automatically created for you. You don't need to add this permission to other distributions that use Lambda@Edge. cloudfront:UpdateDistribution or cloudfront:CreateDistribution – Grants permission to update or create a distribution. For more information, see the following topics: Identity and Access Management for Amazon CloudFront Lambda resource access permissions in the AWS Lambda Developer Guide Function execution role for service principals You must create an IAM role that the lambda.amazonaws.com and edgelambda.amazonaws.com service principals can assume when they execute your function. Tip When you create your function in the Lambda console, you can choose to create a new execution role by using an AWS policy template. This step automatically adds the required Lambda@Edge permissions to execute your function. See Step 5 in the Tutorial: Creating a simple Lambda@Edge function . For more information about creating an IAM role manually, see Creating roles and attaching policies (console) in the IAM User Guide . Example: Role trust policy You can add this role under the Trust Relationship tab in the IAM console. Don't add this policy under the Permissions tab. JSON { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "lambda.amazonaws.com", "edgelambda.amazonaws.com" ] }, "Action": "sts:AssumeRole" } ] } For more information about the permissions that you need to grant to the execution role, see Lambda resource access permissions in the AWS Lambda Developer Guide . Notes By default, whenever a CloudFront event triggers a Lambda function, data is written to CloudWatch Logs. If you want to use these logs, the execution role needs permission to write data to CloudWatch Logs. You can use the predefined AWSLambdaBasicExecutionRole to grant permission to the execution role. For more information about CloudWatch Logs, see Edge function logs . If your Lambda function code accesses other AWS resources, such as reading an object from an S3 bucket, the execution role needs permission to perform that action. Service-linked roles for Lambda@Edge Lambda@Edge uses IAM service-linked roles . A service-linked role is a unique type of IAM role that is linked directly to a service. Service-linked roles are predefined by the service and include all of the permissions that the service requires to call other AWS services on your behalf. Lambda@Edge uses the following IAM service-linked roles: AWSServiceRoleForLambdaReplicator – Lambda@Edge uses this role to allow Lambda@Edge to replicate functions to AWS Regions. When you first add a Lambda@Edge trigger in CloudFront, a role named AWSServiceRoleForLambdaReplicator is created automatically to allow Lambda@Edge to replicate functions to AWS Regions. This role is required to use Lambda@Edge functions. The ARN for the AWSServiceRoleForLambdaReplicator role looks like the following example: arn:aws:iam::123456789012:role/aws-service-role/replicator.lambda.amazonaws.com/AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger – CloudFront uses this role to push log files into CloudWatch. You can use log files to debug Lambda@Edge validation errors. The AWSServiceRoleForCloudFrontLogger role is created automatically when you add Lambda@Edge function association to allow CloudFront to push Lambda@Edge error log files to CloudWatch. The ARN for the AWSServiceRoleForCloudFrontLogger role looks like this: arn:aws:iam::account_number:role/aws-service-role/logger.cloudfront.amazonaws.com/AWSServiceRoleForCloudFrontLogger A service-linked role makes setting up and using Lambda@Edge easier because you don’t have to manually add the necessary permissions. Lambda@Edge defines the permissions of its service-linked roles, and only Lambda@Edge can assume the roles. The defined permissions include the trust policy and the permissions policy. You can't attach the permissions policy to any other IAM entity. You must remove any associated CloudFront or Lambda@Edge resources before you can delete a service-linked role. This helps protect your Lambda@Edge resources so that you don't remove a service-linked role that is still required to access active resources. For more information about service-linked roles, see Service-linked roles for CloudFront . Service-linked role permissions for Lambda@Edge Lambda@Edge uses two service-linked roles, named AWSServiceRoleForLambdaReplicator and AWSServiceRoleForCloudFrontLogger . The following sections describe the permissions for each of these roles. Contents Service-linked role permissions for Lambda replicator Service-linked role permissions for CloudFront logger Service-linked role permissions for Lambda replicator This service-linked role allows Lambda to replicate Lambda@Edge functions to AWS Regions. The AWSServiceRoleForLambdaReplicator service-linked role trusts the replicator.lambda.amazonaws.com service to assume the role. The role permissions policy allows Lambda@Edge to complete the following actions on the specified resources: lambda:CreateFunction on arn:aws:lambda:*:*:function:* lambda:DeleteFunction on arn:aws:lambda:*:*:function:* lambda:DisableReplication on arn:aws:lambda:*:*:function:* iam:PassRole on all AWS resources cloudfront:ListDistributionsByLambdaFunction on all AWS resources Service-linked role permissions for CloudFront logger This service-linked role allows CloudFront to push log files into CloudWatch so that you can debug Lambda@Edge validation errors. The AWSServiceRoleForCloudFrontLogger service-linked role trusts the logger.cloudfront.amazonaws.com service to assume the role. The role permissions policy allows Lambda@Edge to complete the following actions on the specified arn:aws:logs:*:*:log-group:/aws/cloudfront/* resource: logs:CreateLogGroup logs:CreateLogStream logs:PutLogEvents You must configure permissions to allow an IAM entity (such as a user, group, or role) to delete the Lambda@Edge service-linked roles. For more information, see Service-linked role permissions in the IAM User Guide . Creating service-linked roles for Lambda@Edge You don’t typically manually create the service-linked roles for Lambda@Edge. The service creates the roles for you automatically in the following scenarios: When you first create a trigger, the service creates the AWSServiceRoleForLambdaReplicator role (if it doesn’t already exist). This role allows Lambda to replicate Lambda@Edge functions to AWS Regions. If you delete the service-linked role, the role will be created again when you add a new trigger for Lambda@Edge in a distribution. When you update or create a CloudFront distribution that has a Lambda@Edge association, the service creates the AWSServiceRoleForCloudFrontLogger role (if the role doesn’t already exist). This role allows CloudFront to push your log files to CloudWatch. If you delete the service-linked role, the role will be created again when you update or create a CloudFront distribution that has a Lambda@Edge association. To manually create these service-linked roles, you can run the following AWS Command Line Interface (AWS CLI) commands: To create the AWSServiceRoleForLambdaReplicator role Run the following command. aws iam create-service-linked-role --aws-service-name replicator.lambda.amazonaws.com To create the AWSServiceRoleForCloudFrontLogger role Run the following command. aws iam create-service-linked-role --aws-service-name logger.cloudfront.amazonaws.com Editing Lambda@Edge service-linked roles Lambda@Edge doesn't allow you to edit the AWSServiceRoleForLambdaReplicator or AWSServiceRoleForCloudFrontLogger service-linked roles. After the service has created a service-linked role, you can't change the name of the role because various entities might reference the role. However, you can use IAM to edit the role description. For more information, see Editing a service-linked role in the IAM User Guide . Supported AWS Regions for Lambda@Edge service-linked roles CloudFront supports using service-linked roles for Lambda@Edge in the following AWS Regions: US East (N. Virginia) – us-east-1 US East (Ohio) – us-east-2 US West (N. California) – us-west-1 US West (Oregon) – us-west-2 Asia Pacific (Mumbai) – ap-south-1 Asia Pacific (Seoul) – ap-northeast-2 Asia Pacific (Singapore) – ap-southeast-1 Asia Pacific (Sydney) – ap-southeast-2 Asia Pacific (Tokyo) – ap-northeast-1 Europe (Frankfurt) – eu-central-1 Europe (Ireland) – eu-west-1 Europe (London) – eu-west-2 South America (São Paulo) – sa-east-1 Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Tutorial: Basic Lambda@Edge function Write and create a Lambda@Edge function Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/security-iam.html | Identity and Access Management untuk Amazon CloudFront - Amazon CloudFront Identity and Access Management untuk Amazon CloudFront - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Audiens Mengautentikasi dengan identitas Mengelola akses menggunakan kebijakan Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Identity and Access Management untuk Amazon CloudFront AWS Identity and Access Management (IAM) adalah Layanan AWS yang membantu administrator mengontrol akses ke AWS sumber daya dengan aman. Administrator IAM mengontrol siapa yang dapat diautentikasi (masuk) dan diberi wewenang (memiliki izin) untuk menggunakan sumber daya. CloudFront IAM adalah Layanan AWS yang dapat Anda gunakan tanpa biaya tambahan. Topik Audiens Mengautentikasi dengan identitas Mengelola akses menggunakan kebijakan Bagaimana Amazon CloudFront bekerja dengan IAM Contoh kebijakan berbasis identitas untuk Amazon CloudFront AWS kebijakan terkelola untuk Amazon CloudFront Gunakan peran terkait layanan untuk CloudFront Memecahkan masalah CloudFront identitas dan akses Amazon Audiens Cara Anda menggunakan AWS Identity and Access Management (IAM) berbeda berdasarkan peran Anda: Pengguna layanan - minta izin dari administrator Anda jika Anda tidak dapat mengakses fitur (lihat Memecahkan masalah CloudFront identitas dan akses Amazon ) Administrator layanan - tentukan akses pengguna dan mengirimkan permintaan izin (lihat Bagaimana Amazon CloudFront bekerja dengan IAM ) Administrator IAM - tulis kebijakan untuk mengelola akses (lihat Contoh kebijakan berbasis identitas untuk Amazon CloudFront ) Mengautentikasi dengan identitas Otentikasi adalah cara Anda masuk AWS menggunakan kredensi identitas Anda. Anda harus diautentikasi sebagai Pengguna root akun AWS, pengguna IAM, atau dengan mengasumsikan peran IAM. Anda dapat masuk sebagai identitas federasi menggunakan kredensil dari sumber identitas seperti AWS IAM Identity Center (Pusat Identitas IAM), autentikasi masuk tunggal, atau kredensional. Google/Facebook Untuk informasi selengkapnya tentang cara masuk, lihat Cara masuk ke Akun AWS Anda dalam Panduan Pengguna AWS Sign-In . Untuk akses terprogram, AWS sediakan SDK dan CLI untuk menandatangani permintaan secara kriptografis. Untuk informasi selengkapnya, lihat AWS Signature Version 4 untuk permintaan API dalam Panduan Pengguna IAM . Akun AWS pengguna root Saat Anda membuat Akun AWS, Anda mulai dengan satu identitas masuk yang disebut pengguna Akun AWS root yang memiliki akses lengkap ke semua Layanan AWS dan sumber daya. Kami sangat menyarankan agar Anda tidak menggunakan pengguna root untuk tugas sehari-hari. Untuk tugas yang memerlukan kredensial pengguna root, lihat Tugas yang memerlukan kredensial pengguna root dalam Panduan Pengguna IAM . Identitas terfederasi Sebagai praktik terbaik, mewajibkan pengguna manusia untuk menggunakan federasi dengan penyedia identitas untuk mengakses Layanan AWS menggunakan kredensi sementara. Identitas federasi adalah pengguna dari direktori perusahaan Anda, penyedia identitas web, atau Directory Service yang mengakses Layanan AWS menggunakan kredensil dari sumber identitas. Identitas terfederasi mengambil peran yang memberikan kredensial sementara. Untuk manajemen akses terpusat, kami menyarankan AWS IAM Identity Center. Untuk informasi selengkapnya, lihat Apa itu Pusat Identitas IAM? dalam Panduan Pengguna AWS IAM Identity Center . Pengguna dan grup IAM Pengguna IAM adalah identitas dengan izin khusus untuk satu orang atau aplikasi. Sebaiknya gunakan kredensial sementara alih-alih pengguna IAM dengan kredensial jangka panjang. Untuk informasi selengkapnya, lihat Mewajibkan pengguna manusia untuk menggunakan federasi dengan penyedia identitas untuk mengakses AWS menggunakan kredensi sementara di Panduan Pengguna IAM . Grup IAM menentukan kumpulan pengguna IAM dan mempermudah pengelolaan izin untuk pengguna dalam jumlah besar. Untuk mempelajari selengkapnya, lihat Kasus penggunaan untuk pengguna IAM dalam Panduan Pengguna IAM . Peran IAM Peran IAM adalah identitas dengan izin khusus yang menyediakan kredensial sementara. Anda dapat mengambil peran dengan beralih dari pengguna ke peran IAM (konsol) atau dengan memanggil operasi AWS CLI atau AWS API. Untuk informasi selengkapnya, lihat Metode untuk mengambil peran dalam Panduan Pengguna IAM . Peran IAM berguna untuk akses pengguna gabungan, izin pengguna IAM sementara, akses lintas akun, akses lintas layanan, dan aplikasi yang berjalan di Amazon. EC2 Untuk informasi selengkapnya, lihat Akses sumber daya lintas akun di IAM dalam Panduan Pengguna IAM . Mengelola akses menggunakan kebijakan Anda mengontrol akses AWS dengan membuat kebijakan dan melampirkannya ke AWS identitas atau sumber daya. Kebijakan menentukan izin saat dikaitkan dengan identitas atau sumber daya. AWS mengevaluasi kebijakan ini ketika kepala sekolah membuat permintaan. Sebagian besar kebijakan disimpan AWS sebagai dokumen JSON. Untuk informasi selengkapnya tentang dokumen kebijakan JSON, lihat Gambaran umum kebijakan JSON dalam Panduan Pengguna IAM . Menggunakan kebijakan, administrator menentukan siapa yang memiliki akses ke apa dengan mendefinisikan principal mana yang dapat melakukan tindakan pada sumber daya apa, dan dalam kondisi apa. Secara default, pengguna dan peran tidak memiliki izin. Administrator IAM membuat kebijakan IAM dan menambahkannya ke peran, yang kemudian dapat diambil oleh pengguna. Kebijakan IAM mendefinisikan izin terlepas dari metode yang Anda gunakan untuk melakukan operasinya. Kebijakan berbasis identitas Kebijakan berbasis identitas adalah dokumen kebijakan izin JSON yang Anda lampirkan ke identitas (pengguna, grup, atau peran). Kebijakan ini mengontrol tindakan apa yang bisa dilakukan oleh identitas tersebut, terhadap sumber daya yang mana, dan dalam kondisi apa. Untuk mempelajari cara membuat kebijakan berbasis identitas, lihat Tentukan izin IAM kustom dengan kebijakan yang dikelola pelanggan dalam Panduan Pengguna IAM . Kebijakan berbasis identitas dapat berupa kebijakan inline (disematkan langsung ke dalam satu identitas) atau kebijakan terkelola (kebijakan mandiri yang dilampirkan pada banyak identitas). Untuk mempelajari cara memilih antara kebijakan terkelola dan kebijakan inline, lihat Pilih antara kebijakan terkelola dan kebijakan inline dalam Panduan Pengguna IAM . Kebijakan berbasis sumber daya Kebijakan berbasis sumber daya adalah dokumen kebijakan JSON yang Anda lampirkan ke sumber daya. Contohnya termasuk kebijakan kepercayaan peran IAM dan kebijakan bucket Amazon S3. Dalam layanan yang mendukung kebijakan berbasis sumber daya, administrator layanan dapat menggunakannya untuk mengontrol akses ke sumber daya tertentu. Anda harus menentukan principal dalam kebijakan berbasis sumber daya. Kebijakan berbasis sumber daya merupakan kebijakan inline yang terletak di layanan tersebut. Anda tidak dapat menggunakan kebijakan AWS terkelola dari IAM dalam kebijakan berbasis sumber daya. Jenis-jenis kebijakan lain AWS mendukung jenis kebijakan tambahan yang dapat menetapkan izin maksimum yang diberikan oleh jenis kebijakan yang lebih umum: Batasan izin – Menetapkan izin maksimum yang dapat diberikan oleh kebijakan berbasis identitas kepada entitas IAM. Untuk informasi selengkapnya, lihat Batasan izin untuk entitas IAM dalam Panduan Pengguna IAM . Kebijakan kontrol layanan (SCPs) — Tentukan izin maksimum untuk organisasi atau unit organisasi di AWS Organizations. Untuk informasi selengkapnya, lihat Kebijakan kontrol layanan dalam Panduan Pengguna AWS Organizations . Kebijakan kontrol sumber daya (RCPs) — Tetapkan izin maksimum yang tersedia untuk sumber daya di akun Anda. Untuk informasi selengkapnya, lihat Kebijakan kontrol sumber daya (RCPs) di Panduan AWS Organizations Pengguna . Kebijakan sesi – Kebijakan lanjutan yang diteruskan sebagai parameter saat membuat sesi sementara untuk peran atau pengguna terfederasi. Untuk informasi selengkapnya, lihat Kebijakan sesi dalam Panduan Pengguna IAM . Berbagai jenis kebijakan Ketika beberapa jenis kebijakan berlaku pada suatu permintaan, izin yang dihasilkan lebih rumit untuk dipahami. Untuk mempelajari cara AWS menentukan apakah akan mengizinkan permintaan saat beberapa jenis kebijakan terlibat, lihat Logika evaluasi kebijakan di Panduan Pengguna IAM . Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Perlindungan data Bagaimana Amazon CloudFront bekerja dengan IAM Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-permissions.html#using-service-linked-roles-lambda-edge | Siapkan izin dan peran IAM untuk Lambda @Edge - Amazon CloudFront Siapkan izin dan peran IAM untuk Lambda @Edge - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Izin IAM diperlukan untuk mengaitkan fungsi Lambda @Edge dengan distribusi CloudFront Peran eksekusi fungsi untuk prinsipal layanan Peran terkait layanan untuk Lambda @Edge Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Siapkan izin dan peran IAM untuk Lambda @Edge Untuk mengonfigurasi Lambda @Edge, Anda harus memiliki izin dan peran IAM berikut untuk: AWS Lambda Izin IAM — Izin ini memungkinkan Anda membuat fungsi Lambda dan mengaitkannya dengan distribusi Anda. CloudFront Peran eksekusi fungsi Lambda (peran IAM) — Prinsipal layanan Lambda mengasumsikan peran ini untuk menjalankan fungsi Anda. Peran terkait layanan untuk Lambda @Edge — Peran terkait layanan memungkinkan spesifik untuk Layanan AWS mereplikasi fungsi Lambda ke dan mengaktifkan penggunaan file log. Wilayah AWS CloudWatch CloudFront Izin IAM diperlukan untuk mengaitkan fungsi Lambda @Edge dengan distribusi CloudFront Selain izin IAM yang Anda perlukan untuk Lambda, Anda memerlukan izin berikut untuk mengaitkan fungsi Lambda dengan distribusi: CloudFront lambda:GetFunction — Memberikan izin untuk mendapatkan informasi konfigurasi untuk fungsi Lambda Anda dan URL yang telah ditentukan sebelumnya untuk mengunduh file .zip yang berisi fungsi tersebut. lambda:EnableReplication* — Memberikan izin ke kebijakan sumber daya sehingga layanan replikasi Lambda bisa mendapatkan kode fungsi dan konfigurasi. lambda:DisableReplication* — Memberikan izin untuk kebijakan sumber daya sehingga layanan replikasi Lambda dapat menghapus fungsi. penting Anda harus menambahkan tanda bintang ( * ) di akhir lambda:EnableReplication * dan lambda:DisableReplication * tindakan. Untuk sumber daya, tentukan ARN dari versi fungsi yang ingin Anda jalankan ketika suatu CloudFront peristiwa terjadi, seperti contoh berikut: arn:aws:lambda:us-east-1:123456789012:function: TestFunction :2 iam:CreateServiceLinkedRole — Memberikan izin untuk membuat peran terkait layanan yang digunakan Lambda @Edge untuk mereplikasi fungsi Lambda. CloudFront Setelah Anda mengonfigurasi Lambda @Edge untuk pertama kalinya, peran terkait layanan akan dibuat secara otomatis untuk Anda. Anda tidak perlu menambahkan izin ini ke distribusi lain yang menggunakan Lambda @Edge. cloudfront:UpdateDistribution atau cloudfront:CreateDistribution — Memberikan izin untuk memperbarui atau membuat distribusi. Untuk informasi selengkapnya, lihat topik berikut: Identity and Access Management untuk Amazon CloudFront Izin akses sumber daya Lambda di Panduan Pengembang AWS Lambda Peran eksekusi fungsi untuk prinsipal layanan Anda harus membuat peran IAM yang dapat diasumsikan oleh kepala sekolah lambda.amazonaws.com dan edgelambda.amazonaws.com layanan ketika mereka menjalankan fungsi Anda. Tip Saat membuat fungsi di konsol Lambda, Anda dapat memilih untuk membuat peran eksekusi baru dengan menggunakan templat AWS kebijakan. Langkah ini secara otomatis menambahkan izin Lambda @Edge yang diperlukan untuk menjalankan fungsi Anda. Lihat Langkah 5 dalam Tutorial: Membuat fungsi Lambda @Edge sederhana . Untuk informasi selengkapnya tentang membuat peran IAM secara manual, lihat Membuat peran dan melampirkan kebijakan (konsol) di Panduan Pengguna IAM . contoh Contoh: Kebijakan kepercayaan peran Anda dapat menambahkan peran ini di bawah tab Trust Relationship di konsol IAM. Jangan tambahkan kebijakan ini di bawah tab Izin . JSON { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "lambda.amazonaws.com", "edgelambda.amazonaws.com" ] }, "Action": "sts:AssumeRole" } ] } Untuk informasi selengkapnya tentang izin yang perlu Anda berikan ke peran eksekusi, lihat Izin akses sumber daya Lambda di AWS Lambda Panduan Pengembang. Catatan Secara default, setiap kali CloudFront peristiwa memicu fungsi Lambda, data ditulis CloudWatch ke Log. Jika Anda ingin menggunakan log ini, peran eksekusi memerlukan izin untuk menulis data ke CloudWatch Log. Anda dapat menggunakan standar AWSLambdaBasicExecutionRole untuk memberikan izin ke peran eksekusi. Untuk informasi selengkapnya tentang CloudWatch Log, lihat Log fungsi tepi . Jika kode fungsi Lambda Anda mengakses AWS sumber daya lain, seperti membaca objek dari bucket S3, peran eksekusi memerlukan izin untuk melakukan tindakan tersebut. Peran terkait layanan untuk Lambda @Edge Lambda @Edge menggunakan peran terkait layanan IAM. Peran yang terhubung dengan layanan adalah jenis peran IAM unik yang terhubung langsung ke layanan. Peran yang ditautkan dengan layanan ditentukan sebelumnya oleh layanan dan mencakup semua izin yang diperlukan layanan untuk menghubungi layanan AWS lainnya atas nama Anda. Lambda @Edge menggunakan peran terkait layanan IAM berikut: AWSServiceRoleForLambdaReplicator — Lambda @Edge menggunakan peran ini untuk memungkinkan Lambda @Edge mereplikasi fungsi. Wilayah AWS Saat Anda pertama kali menambahkan pemicu Lambda @Edge CloudFront, peran bernama dibuat AWSServiceRoleForLambdaReplicator secara otomatis untuk memungkinkan Lambda @Edge mereplikasi fungsi. Wilayah AWS Peran ini diperlukan untuk menggunakan fungsi Lambda @Edge. ARN untuk AWSServiceRoleForLambdaReplicator peran tersebut terlihat seperti contoh berikut: arn:aws:iam::123456789012:role/aws-service-role/replicator.lambda.amazonaws.com/AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger — CloudFront menggunakan peran ini untuk mendorong file log ke CloudWatch. Anda dapat menggunakan file log untuk men-debug kesalahan validasi Lambda @Edge. AWSServiceRoleForCloudFrontLoggerPeran dibuat secara otomatis saat Anda menambahkan asosiasi fungsi Lambda @Edge CloudFront untuk memungkinkan mendorong file log kesalahan Lambda @Edge ke. CloudWatch ARN untuk AWSServiceRoleForCloudFrontLogger peran yang terlihat seperti ini: arn:aws:iam::account_number:role/aws-service-role/logger.cloudfront.amazonaws.com/AWSServiceRoleForCloudFrontLogger Peran yang terhubung dengan layanan memudahkan pengaturan dan penggunaan Lambda@Edge karena Anda tidak perlu menambahkan izin yang diperlukan secara manual. Lambda@Edge mendefinisikan izin peran yang terhubung ke layanan, dan hanya Lambda@Edge yang dapat memegang peran tersebut. Izin yang ditentukan mencakup kebijakan kepercayaan dan kebijakan izin. Kebijakan izin tidak dapat dilampirkan ke entitas IAM lainnya. Anda harus menghapus sumber daya terkait CloudFront atau Lambda @Edge sebelum dapat menghapus peran terkait layanan. Ini membantu melindungi sumber daya Lambda @Edge Anda sehingga Anda tidak menghapus peran terkait layanan yang masih diperlukan untuk mengakses sumber daya aktif. Untuk mengetahui informasi selengkapnya tentang peran terkait layanan, lihat Peran terkait layanan untuk CloudFront . Izin peran terkait layanan untuk Lambda @Edge Lambda @Edge menggunakan dua peran terkait layanan, bernama dan. AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger Bagian berikut menjelaskan izin untuk masing-masing peran ini. Daftar Isi Izin peran terkait layanan untuk replikator Lambda Izin peran terkait layanan untuk logger CloudFront Izin peran terkait layanan untuk replikator Lambda Peran terkait layanan ini memungkinkan Lambda untuk mereplikasi fungsi Lambda @Edge. Wilayah AWS Peran terkait layanan AWSServiceRoleForLambdaReplicator memercayai layanan replicator.lambda.amazonaws.com untuk menjalankan peran. Kebijakan izin peran memungkinkan Lambda@Edge menyelesaikan tindakan berikut pada sumber daya yang ditentukan: lambda:CreateFunction pada arn:aws:lambda:*:*:function:* lambda:DeleteFunction pada arn:aws:lambda:*:*:function:* lambda:DisableReplication pada arn:aws:lambda:*:*:function:* iam:PassRole pada all AWS resources cloudfront:ListDistributionsByLambdaFunction pada all AWS resources Izin peran terkait layanan untuk logger CloudFront Peran terkait layanan ini memungkinkan CloudFront untuk mendorong file log ke dalam CloudWatch sehingga Anda dapat men-debug kesalahan validasi Lambda @Edge. Peran terkait layanan AWSServiceRoleForCloudFrontLogger memercayai layanan logger.cloudfront.amazonaws.com untuk menjalankan peran. Kebijakan izin peran memungkinkan Lambda @Edge menyelesaikan tindakan berikut pada sumber daya yang ditentukan: arn:aws:logs:*:*:log-group:/aws/cloudfront/* logs:CreateLogGroup logs:CreateLogStream logs:PutLogEvents Anda harus mengonfigurasi izin untuk mengizinkan entitas IAM (seperti pengguna, grup, atau peran) untuk menghapus peran yang ditautkan oleh layanan Lambda@Edge. Untuk informasi selengkapnya, lihat Izin peran terkait layanan dalam Panduan Pengguna IAM . Membuat peran terkait layanan untuk Lambda @Edge Anda biasanya tidak membuat peran terkait layanan secara manual untuk Lambda@Edge. Layanan ini membuat peran untuk Anda secara otomatis dalam skenario berikut: Saat pertama kali membuat pemicu, layanan akan membuat AWSServiceRoleForLambdaReplicator peran (jika belum ada). Peran ini memungkinkan Lambda untuk mereplikasi fungsi Lambda @Edge ke. Wilayah AWS Jika Anda menghapus peran layanan yang ditautkan, peran tersebut akan dibuat lagi saat Anda menambahkan pemicu baru untuk Lambda@Edge dalam distribusi. Saat Anda memperbarui atau membuat CloudFront distribusi yang memiliki asosiasi Lambda @Edge, layanan akan membuat AWSServiceRoleForCloudFrontLogger peran (jika peran tersebut belum ada). Peran ini memungkinkan CloudFront untuk mendorong file log Anda ke CloudWatch. Jika Anda menghapus peran terkait layanan, peran akan dibuat lagi saat Anda memperbarui atau membuat CloudFront distribusi yang memiliki asosiasi Lambda @Edge. Untuk membuat peran terkait layanan ini secara manual, Anda dapat menjalankan perintah AWS Command Line Interface (AWS CLI) berikut: Untuk membuat AWSServiceRoleForLambdaReplicator peran Jalankan perintah berikut. aws iam create-service-linked-role --aws-service-name replicator.lambda.amazonaws.com Untuk membuat AWSServiceRoleForCloudFrontLogger peran Jalankan perintah berikut. aws iam create-service-linked-role --aws-service-name logger.cloudfront.amazonaws.com Mengedit peran terkait layanan Lambda @Edge Lambda @Edge tidak mengizinkan Anda mengedit AWSServiceRoleForLambdaReplicator atau peran terkait AWSServiceRoleForCloudFrontLogger layanan. Setelah layanan membuat peran terkait layanan, Anda tidak dapat mengubah nama peran karena berbagai entitas mungkin mereferensikan peran tersebut. Namun, Anda dapat menggunakan IAM untuk mengedit deskripsi peran. Untuk informasi selengkapnya, lihat Mengedit peran terkait layanan dalam Panduan Pengguna IAM . Didukung Wilayah AWS untuk peran terkait layanan Lambda @Edge CloudFront mendukung penggunaan peran terkait layanan untuk Lambda @Edge sebagai berikut: Wilayah AWS AS Timur (Virginia Utara)– us-east-1 AS Timur (Ohio)– us-east-2 AS Barat (California Utara)– us-west-1 AS Barat (Oregon)– us-west-2 Asia Pasifik (Mumbai)– ap-south-1 Asia Pasifik (Seoul)– ap-northeast-2 Asia Pasifik (Singapura)– ap-southeast-1 Asia Pasifik (Sydney)– ap-southeast-2 Asia Pasifik (Tokyo) – ap-northeast-1 Eropa (Frankfurt) – eu-central-1 Eropa (Irlandia)– eu-west-1 Eropa (London) – eu-west-2 Amerika Selatan (São Paulo) – sa-east-1 Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Tutorial: Fungsi dasar Lambda @Edge Tulis dan buat fungsi Lambda @Edge Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-permissions.html#lambda-edge-permissions-function-execution | Siapkan izin dan peran IAM untuk Lambda @Edge - Amazon CloudFront Siapkan izin dan peran IAM untuk Lambda @Edge - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Izin IAM diperlukan untuk mengaitkan fungsi Lambda @Edge dengan distribusi CloudFront Peran eksekusi fungsi untuk prinsipal layanan Peran terkait layanan untuk Lambda @Edge Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Siapkan izin dan peran IAM untuk Lambda @Edge Untuk mengonfigurasi Lambda @Edge, Anda harus memiliki izin dan peran IAM berikut untuk: AWS Lambda Izin IAM — Izin ini memungkinkan Anda membuat fungsi Lambda dan mengaitkannya dengan distribusi Anda. CloudFront Peran eksekusi fungsi Lambda (peran IAM) — Prinsipal layanan Lambda mengasumsikan peran ini untuk menjalankan fungsi Anda. Peran terkait layanan untuk Lambda @Edge — Peran terkait layanan memungkinkan spesifik untuk Layanan AWS mereplikasi fungsi Lambda ke dan mengaktifkan penggunaan file log. Wilayah AWS CloudWatch CloudFront Izin IAM diperlukan untuk mengaitkan fungsi Lambda @Edge dengan distribusi CloudFront Selain izin IAM yang Anda perlukan untuk Lambda, Anda memerlukan izin berikut untuk mengaitkan fungsi Lambda dengan distribusi: CloudFront lambda:GetFunction — Memberikan izin untuk mendapatkan informasi konfigurasi untuk fungsi Lambda Anda dan URL yang telah ditentukan sebelumnya untuk mengunduh file .zip yang berisi fungsi tersebut. lambda:EnableReplication* — Memberikan izin ke kebijakan sumber daya sehingga layanan replikasi Lambda bisa mendapatkan kode fungsi dan konfigurasi. lambda:DisableReplication* — Memberikan izin untuk kebijakan sumber daya sehingga layanan replikasi Lambda dapat menghapus fungsi. penting Anda harus menambahkan tanda bintang ( * ) di akhir lambda:EnableReplication * dan lambda:DisableReplication * tindakan. Untuk sumber daya, tentukan ARN dari versi fungsi yang ingin Anda jalankan ketika suatu CloudFront peristiwa terjadi, seperti contoh berikut: arn:aws:lambda:us-east-1:123456789012:function: TestFunction :2 iam:CreateServiceLinkedRole — Memberikan izin untuk membuat peran terkait layanan yang digunakan Lambda @Edge untuk mereplikasi fungsi Lambda. CloudFront Setelah Anda mengonfigurasi Lambda @Edge untuk pertama kalinya, peran terkait layanan akan dibuat secara otomatis untuk Anda. Anda tidak perlu menambahkan izin ini ke distribusi lain yang menggunakan Lambda @Edge. cloudfront:UpdateDistribution atau cloudfront:CreateDistribution — Memberikan izin untuk memperbarui atau membuat distribusi. Untuk informasi selengkapnya, lihat topik berikut: Identity and Access Management untuk Amazon CloudFront Izin akses sumber daya Lambda di Panduan Pengembang AWS Lambda Peran eksekusi fungsi untuk prinsipal layanan Anda harus membuat peran IAM yang dapat diasumsikan oleh kepala sekolah lambda.amazonaws.com dan edgelambda.amazonaws.com layanan ketika mereka menjalankan fungsi Anda. Tip Saat membuat fungsi di konsol Lambda, Anda dapat memilih untuk membuat peran eksekusi baru dengan menggunakan templat AWS kebijakan. Langkah ini secara otomatis menambahkan izin Lambda @Edge yang diperlukan untuk menjalankan fungsi Anda. Lihat Langkah 5 dalam Tutorial: Membuat fungsi Lambda @Edge sederhana . Untuk informasi selengkapnya tentang membuat peran IAM secara manual, lihat Membuat peran dan melampirkan kebijakan (konsol) di Panduan Pengguna IAM . contoh Contoh: Kebijakan kepercayaan peran Anda dapat menambahkan peran ini di bawah tab Trust Relationship di konsol IAM. Jangan tambahkan kebijakan ini di bawah tab Izin . JSON { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "lambda.amazonaws.com", "edgelambda.amazonaws.com" ] }, "Action": "sts:AssumeRole" } ] } Untuk informasi selengkapnya tentang izin yang perlu Anda berikan ke peran eksekusi, lihat Izin akses sumber daya Lambda di AWS Lambda Panduan Pengembang. Catatan Secara default, setiap kali CloudFront peristiwa memicu fungsi Lambda, data ditulis CloudWatch ke Log. Jika Anda ingin menggunakan log ini, peran eksekusi memerlukan izin untuk menulis data ke CloudWatch Log. Anda dapat menggunakan standar AWSLambdaBasicExecutionRole untuk memberikan izin ke peran eksekusi. Untuk informasi selengkapnya tentang CloudWatch Log, lihat Log fungsi tepi . Jika kode fungsi Lambda Anda mengakses AWS sumber daya lain, seperti membaca objek dari bucket S3, peran eksekusi memerlukan izin untuk melakukan tindakan tersebut. Peran terkait layanan untuk Lambda @Edge Lambda @Edge menggunakan peran terkait layanan IAM. Peran yang terhubung dengan layanan adalah jenis peran IAM unik yang terhubung langsung ke layanan. Peran yang ditautkan dengan layanan ditentukan sebelumnya oleh layanan dan mencakup semua izin yang diperlukan layanan untuk menghubungi layanan AWS lainnya atas nama Anda. Lambda @Edge menggunakan peran terkait layanan IAM berikut: AWSServiceRoleForLambdaReplicator — Lambda @Edge menggunakan peran ini untuk memungkinkan Lambda @Edge mereplikasi fungsi. Wilayah AWS Saat Anda pertama kali menambahkan pemicu Lambda @Edge CloudFront, peran bernama dibuat AWSServiceRoleForLambdaReplicator secara otomatis untuk memungkinkan Lambda @Edge mereplikasi fungsi. Wilayah AWS Peran ini diperlukan untuk menggunakan fungsi Lambda @Edge. ARN untuk AWSServiceRoleForLambdaReplicator peran tersebut terlihat seperti contoh berikut: arn:aws:iam::123456789012:role/aws-service-role/replicator.lambda.amazonaws.com/AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger — CloudFront menggunakan peran ini untuk mendorong file log ke CloudWatch. Anda dapat menggunakan file log untuk men-debug kesalahan validasi Lambda @Edge. AWSServiceRoleForCloudFrontLoggerPeran dibuat secara otomatis saat Anda menambahkan asosiasi fungsi Lambda @Edge CloudFront untuk memungkinkan mendorong file log kesalahan Lambda @Edge ke. CloudWatch ARN untuk AWSServiceRoleForCloudFrontLogger peran yang terlihat seperti ini: arn:aws:iam::account_number:role/aws-service-role/logger.cloudfront.amazonaws.com/AWSServiceRoleForCloudFrontLogger Peran yang terhubung dengan layanan memudahkan pengaturan dan penggunaan Lambda@Edge karena Anda tidak perlu menambahkan izin yang diperlukan secara manual. Lambda@Edge mendefinisikan izin peran yang terhubung ke layanan, dan hanya Lambda@Edge yang dapat memegang peran tersebut. Izin yang ditentukan mencakup kebijakan kepercayaan dan kebijakan izin. Kebijakan izin tidak dapat dilampirkan ke entitas IAM lainnya. Anda harus menghapus sumber daya terkait CloudFront atau Lambda @Edge sebelum dapat menghapus peran terkait layanan. Ini membantu melindungi sumber daya Lambda @Edge Anda sehingga Anda tidak menghapus peran terkait layanan yang masih diperlukan untuk mengakses sumber daya aktif. Untuk mengetahui informasi selengkapnya tentang peran terkait layanan, lihat Peran terkait layanan untuk CloudFront . Izin peran terkait layanan untuk Lambda @Edge Lambda @Edge menggunakan dua peran terkait layanan, bernama dan. AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger Bagian berikut menjelaskan izin untuk masing-masing peran ini. Daftar Isi Izin peran terkait layanan untuk replikator Lambda Izin peran terkait layanan untuk logger CloudFront Izin peran terkait layanan untuk replikator Lambda Peran terkait layanan ini memungkinkan Lambda untuk mereplikasi fungsi Lambda @Edge. Wilayah AWS Peran terkait layanan AWSServiceRoleForLambdaReplicator memercayai layanan replicator.lambda.amazonaws.com untuk menjalankan peran. Kebijakan izin peran memungkinkan Lambda@Edge menyelesaikan tindakan berikut pada sumber daya yang ditentukan: lambda:CreateFunction pada arn:aws:lambda:*:*:function:* lambda:DeleteFunction pada arn:aws:lambda:*:*:function:* lambda:DisableReplication pada arn:aws:lambda:*:*:function:* iam:PassRole pada all AWS resources cloudfront:ListDistributionsByLambdaFunction pada all AWS resources Izin peran terkait layanan untuk logger CloudFront Peran terkait layanan ini memungkinkan CloudFront untuk mendorong file log ke dalam CloudWatch sehingga Anda dapat men-debug kesalahan validasi Lambda @Edge. Peran terkait layanan AWSServiceRoleForCloudFrontLogger memercayai layanan logger.cloudfront.amazonaws.com untuk menjalankan peran. Kebijakan izin peran memungkinkan Lambda @Edge menyelesaikan tindakan berikut pada sumber daya yang ditentukan: arn:aws:logs:*:*:log-group:/aws/cloudfront/* logs:CreateLogGroup logs:CreateLogStream logs:PutLogEvents Anda harus mengonfigurasi izin untuk mengizinkan entitas IAM (seperti pengguna, grup, atau peran) untuk menghapus peran yang ditautkan oleh layanan Lambda@Edge. Untuk informasi selengkapnya, lihat Izin peran terkait layanan dalam Panduan Pengguna IAM . Membuat peran terkait layanan untuk Lambda @Edge Anda biasanya tidak membuat peran terkait layanan secara manual untuk Lambda@Edge. Layanan ini membuat peran untuk Anda secara otomatis dalam skenario berikut: Saat pertama kali membuat pemicu, layanan akan membuat AWSServiceRoleForLambdaReplicator peran (jika belum ada). Peran ini memungkinkan Lambda untuk mereplikasi fungsi Lambda @Edge ke. Wilayah AWS Jika Anda menghapus peran layanan yang ditautkan, peran tersebut akan dibuat lagi saat Anda menambahkan pemicu baru untuk Lambda@Edge dalam distribusi. Saat Anda memperbarui atau membuat CloudFront distribusi yang memiliki asosiasi Lambda @Edge, layanan akan membuat AWSServiceRoleForCloudFrontLogger peran (jika peran tersebut belum ada). Peran ini memungkinkan CloudFront untuk mendorong file log Anda ke CloudWatch. Jika Anda menghapus peran terkait layanan, peran akan dibuat lagi saat Anda memperbarui atau membuat CloudFront distribusi yang memiliki asosiasi Lambda @Edge. Untuk membuat peran terkait layanan ini secara manual, Anda dapat menjalankan perintah AWS Command Line Interface (AWS CLI) berikut: Untuk membuat AWSServiceRoleForLambdaReplicator peran Jalankan perintah berikut. aws iam create-service-linked-role --aws-service-name replicator.lambda.amazonaws.com Untuk membuat AWSServiceRoleForCloudFrontLogger peran Jalankan perintah berikut. aws iam create-service-linked-role --aws-service-name logger.cloudfront.amazonaws.com Mengedit peran terkait layanan Lambda @Edge Lambda @Edge tidak mengizinkan Anda mengedit AWSServiceRoleForLambdaReplicator atau peran terkait AWSServiceRoleForCloudFrontLogger layanan. Setelah layanan membuat peran terkait layanan, Anda tidak dapat mengubah nama peran karena berbagai entitas mungkin mereferensikan peran tersebut. Namun, Anda dapat menggunakan IAM untuk mengedit deskripsi peran. Untuk informasi selengkapnya, lihat Mengedit peran terkait layanan dalam Panduan Pengguna IAM . Didukung Wilayah AWS untuk peran terkait layanan Lambda @Edge CloudFront mendukung penggunaan peran terkait layanan untuk Lambda @Edge sebagai berikut: Wilayah AWS AS Timur (Virginia Utara)– us-east-1 AS Timur (Ohio)– us-east-2 AS Barat (California Utara)– us-west-1 AS Barat (Oregon)– us-west-2 Asia Pasifik (Mumbai)– ap-south-1 Asia Pasifik (Seoul)– ap-northeast-2 Asia Pasifik (Singapura)– ap-southeast-1 Asia Pasifik (Sydney)– ap-southeast-2 Asia Pasifik (Tokyo) – ap-northeast-1 Eropa (Frankfurt) – eu-central-1 Eropa (Irlandia)– eu-west-1 Eropa (London) – eu-west-2 Amerika Selatan (São Paulo) – sa-east-1 Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Tutorial: Fungsi dasar Lambda @Edge Tulis dan buat fungsi Lambda @Edge Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:30:34 |
https://www.php.net/manual/de/function.session-regenerate-id.php | PHP: session_regenerate_id - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_register_shutdown » « session_name PHP-Handbuch Funktionsreferenz Session-Erweiterungen Sessions Session-Funktionen Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_regenerate_id (PHP 4 >= 4.3.2, PHP 5, PHP 7, PHP 8) session_regenerate_id — Ersetzt die aktuelle Session-ID durch eine neu erzeugte Beschreibung session_regenerate_id ( bool $delete_old_session = false ): bool Die Funktion session_regenerate_id() ersetzt die aktuelle Session-ID durch eine neue und übernimmt die aktuellen Session-Informationen. Wenn session.use_trans_sid aktiviert ist, darf die Ausgabe erst nach dem Aufruf von session_regenerate_id() beginnen. Andernfalls wird die alte Session-ID verwendet. Warnung Zurzeit kann session_regenerate_id nicht gut mit unstabilen Netzwerken, z. B. Mobil- und WiFi-Netzwerke, umgehen. Daher kann es zu verlorenen Sessions kommen, wenn session_regenerate_id aufgerufen wird. Die alten Session-Daten sollten nicht sofort zerstört werden, sondern es sollte ein Destroy-Zeitstempel verwendet werden und der Zugriff auf die alte Session-ID sollte kontrolliert werden. Andernfalls kann ein konkurrierender Zugriff auf die Seite möglicherweise zu einem inkonsistenten Zustand führen, oder die Session kann gänzlich verloren werden, oder es kann sich eine Race-Condition im Client (Browser) ergeben und viele Session-IDs könnten nutzlos erzeugt werden. Die sofortige Löschung der Session-Daten verhindert die Erkennung von Session-Hijack-Angriffen und auch deren Vorbeugung. Parameter-Liste delete_old_session Legt fest, ob die zugehörige alte Session-Datei gelöscht werden soll oder nicht. Die alten Session-Daten sollten nicht gelöscht werden, wenn Race-Conditions, die durch die Löschung verursacht werden, verhindert, oder Session-Hijack-Angriffe erkannt oder vermieden werden müssen. Rückgabewerte Gibt bei Erfolg true zurück. Bei einem Fehler wird false zurückgegeben. Beispiele Beispiel #1 Ein session_regenerate_id() -Beispiel <?php // ACHTUNG: dieser Code ist nicht voll funktionsfähig, sondern dient nur als Beispiel! session_start (); // Prüfe den Destroy-Zeitstempel if (isset( $_SESSION [ 'destroyed' ]) && $_SESSION [ 'destroyed' ] < time () - 300 ) { // Dies sollte normalerweise nicht passieren. Es könnte durch einen Angriff // oder ein unstabiles Netzwerk verursacht worden sein. // Entferne den Authentifizierungsstatus dieser Nutzer-Session. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } $old_sessionid = session_id (); // Lege den Destroy-Zeitstempel fest $_SESSION [ 'destroyed' ] = time (); // session_regenerate_id() speichert die // alten Session-Daten // Der einfache Aufruf von session_regenerate_id() kann in einer verlorenen // Session resultieren, etc. Siehe das nächste Beispiel. session_regenerate_id (); // Die neue Session braucht keinen Destroy-Zeitstempel unset( $_SESSION [ 'destroyed' ]); $new_sessionid = session_id (); echo "Alte Session: $old_sessionid <br />" ; echo "Neue Session: $new_sessionid <br />" ; print_r ( $_SESSION ); ?> Zurzeit kann das Session-Modul nicht gut mit unstabilen Netzwerken umgehen. Die Session-ID sollte selbst verwaltet werden, um verlorene Sessions durch session_regenarate_id zu verhindern. Beispiel #2 Verhindern von verlorenen Sessions durch session_regenerate_id() <?php // ACHTUNG: dieser Code ist nicht voll funktionsfähig, sondern dient nur als Beispiel! // my_session_start() und my_session_regenerate_id() verhindern verlorene Session // durch unstabile Netzwerke. Zusätzlich kann dieser Code dem Ausnutzen einer // gestohlenen Session durch Angreifer vorbeugen. function my_session_start () { session_start (); if (isset( $_SESSION [ 'destroyed' ])) { if ( $_SESSION [ 'destroyed' ] < time ()- 300 ) { // Dies sollte normalerweise nicht passieren. Es könnte durch einen Angriff // oder ein unstabiles Netzwerk verursacht worden sein. // Entferne den Authentifizierungsstatus dieser Nutzer-Session. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } if (isset( $_SESSION [ 'new_session_id' ])) { // Noch nicht vollständig abgelaufen. Könnte an einem verlorenen Cookie // durch ein unstabiles Netzwerk liegen. // Noch einmal versuchen, das ordnungsgemäße Session-ID-Cookie zu setzen. // ACHTUNG: es sollte nicht versucht werden, die Session-ID erneut // festzulegen, wenn das Authentifizierungsflag entfernt werden soll. session_commit (); session_id ( $_SESSION [ 'new_session_id' ]); // Die neue Session-ID sollte existieren session_start (); return; } } } function my_session_regenerate_id () { // Eine neue Session-ID wird benötigt, um die richtige Session-ID festzulegen, // wenn die Session-ID aufgrund eines unstabilen Netzwerks nicht gesetzt wurde. $new_session_id = session_create_id (); $_SESSION [ 'new_session_id' ] = $new_session_id ; // Lege den Destroy-Zeitstempel fest $_SESSION [ 'destroyed' ] = time (); // Schreibe und schließe die aktuelle Session session_commit (); // Starte die Session mit einer neuen Session-ID session_id ( $new_session_id ); ini_set ( 'session.use_strict_mode' , 0 ); session_start (); ini_set ( 'session.use_strict_mode' , 1 ); // Die neue Session braucht sie nicht unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Siehe auch session_id() - Liefert und/oder setzt die aktuelle Session-ID session_create_id() - Erzeugt eine neue Session-ID session_start() - Erzeugt eine neue Session oder setzt eine vorhandene fort session_destroy() - Löscht alle in einer Session registrierten Daten session_reset() - Initialisiert das Session-Array mit seinen ursprünglichen Werten neu session_name() - Liefert und/oder setzt den Namen der aktuellen Session Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 22 notes up down 42 tedivm at tedivm dot com ¶ 9 years ago I wrote the current top voted comment on this and wanted to add something. The existing code from my previous comment generates it's nonces in an insecure way- <?php $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); ?> Since "microtime" is predictable it makes brute forcing the nonce much easier. A better option would be something that utilizes randomness, such as- <?php bin2hex ( openssl_random_pseudo_bytes ( 32 )) ?> up down 42 tedivm at tedivm dot com ¶ 17 years ago I wrote the following code for a project I'm working on- it attempts to resolve the regenerate issue, as well as deal with a couple of other session related things. I tried to make it a little more generic and usable (for instance, in the full version it throws different types of exceptions for the different types of session issues), so hopefully someone might find it useful. <?php function regenerateSession ( $reload = false ) { // This token is used by forms to prevent cross site forgery attempts if(!isset( $_SESSION [ 'nonce' ]) || $reload ) $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); if(!isset( $_SESSION [ 'IPaddress' ]) || $reload ) $_SESSION [ 'IPaddress' ] = $_SERVER [ 'REMOTE_ADDR' ]; if(!isset( $_SESSION [ 'userAgent' ]) || $reload ) $_SESSION [ 'userAgent' ] = $_SERVER [ 'HTTP_USER_AGENT' ]; //$_SESSION['user_id'] = $this->user->getId(); // Set current session to expire in 1 minute $_SESSION [ 'OBSOLETE' ] = true ; $_SESSION [ 'EXPIRES' ] = time () + 60 ; // Create new session without destroying the old one session_regenerate_id ( false ); // Grab current session ID and close both sessions to allow other scripts to use them $newSession = session_id (); session_write_close (); // Set session ID to the new one, and start it back up again session_id ( $newSession ); session_start (); // Don't want this one to expire unset( $_SESSION [ 'OBSOLETE' ]); unset( $_SESSION [ 'EXPIRES' ]); } function checkSession () { try{ if( $_SESSION [ 'OBSOLETE' ] && ( $_SESSION [ 'EXPIRES' ] < time ())) throw new Exception ( 'Attempt to use expired session.' ); if(! is_numeric ( $_SESSION [ 'user_id' ])) throw new Exception ( 'No session started.' ); if( $_SESSION [ 'IPaddress' ] != $_SERVER [ 'REMOTE_ADDR' ]) throw new Exception ( 'IP Address mixmatch (possible session hijacking attempt).' ); if( $_SESSION [ 'userAgent' ] != $_SERVER [ 'HTTP_USER_AGENT' ]) throw new Exception ( 'Useragent mixmatch (possible session hijacking attempt).' ); if(! $this -> loadUser ( $_SESSION [ 'user_id' ])) throw new Exception ( 'Attempted to log in user that does not exist with ID: ' . $_SESSION [ 'user_id' ]); if(! $_SESSION [ 'OBSOLETE' ] && mt_rand ( 1 , 100 ) == 1 ) { $this -> regenerateSession (); } return true ; }catch( Exception $e ){ return false ; } } ?> up down 3 Rumour ¶ 2 years ago The code example provided of my_session_regenerate_id() DOES NOT work and DESTROYS all session variables. Plus the second ini_set gives an error. The code for regenerating (only that part, the rest seems fine) should simply be this: <?php function my_session_regenerate_id () { $new_session_id = session_create_id (); // backup session variables $keepSession = $_SESSION ; // add info for users with bad connection not receiving the new session id $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit () ; // Start session with new session ID ini_set ( 'session.use_strict_mode' , 0 ); session_id ( $new_session_id ); session_start (); $_SESSION = $keepSession ; } ?> up down 13 ei dot rik dot ops dot tad at gmail dot com ¶ 9 years ago In PHP 5.6 (and probably older versions), session_regenerate_id(true) do not trigger a read() call to the session handler for the new session id. In PHP 7, read() is triggered during session_regenerate_id(true). Nice to know when working with custom session handlers. up down 8 gr at gr5 dot org ¶ 14 years ago If you are trying to maintain 2 active sessions don't use session_regenerate_id(). Especially if the first session is closed and it's time to open the second. Because the session id is cached you also have to explicitly set it the second time. <?php session_name ( 'PHPSESSID' ); // redundant - here for clarity session_start (); // ...do stuff session_write_close (); // now switch to session 2... session_name ( 'PHPSESSID_2' ); if (isset( $_COOKIE [ 'phpsessid_2' ])) session_id ( $_COOKIE [ 'phpsessid_2' ]); // not doing this will simply reopen the first session again else session_id ( sha1 ( mt_rand ()); // dont use session_regenerate_id() here. Not creating a new id will create two cookies with same session id and same session variables session_start (); // ... do stuff with session 2 session_write_close (); ?> up down 13 ross at kndr dot org ¶ 21 years ago In a previous note, php at 5mm de describes how to prevent session hijacking by ensuring that the session id provided matches the HTTP_USER_AGENT and REMOTE_ADDR fields that were present when the session id was first issued. It should be noted that HTTP_USER_AGENT is supplied by the client, and so can be easily modified by a malicious user. Also, the client IP addresses can be spoofed, although that's a bit more difficult. Care should be taken when relying on the session for authentication. up down 4 babel at nosqamplease sympatico ca ¶ 21 years ago To add to php at 5mm de's comments: If the session is held over https, it's even better to save the client's cert or ssl session id instead of the hostname or ip, as it's proxy-transparent and more secure. up down 10 spmtrap at yahoo dot com ¶ 13 years ago `session_regenerate_id` sends a new cookie but doesn't overwrite the value stored in `$_COOKIE`. After calling `session_destroy`, the open session ID is discarded, so simply restarting the session with `session_start` (as done in Ben Johnson's code) will re-open the original, though now empty, session for the current request (subsequent requests will use the new session ID). Instead of `session_destroy`+`session_start`, use the `$delete_old_session` parameter to `session_regenerate_id` to delete the previous session data. <?php session_start (); /* Create a new session, deleting the previous session data. */ session_regenerate_id ( TRUE ); /* erase data carried over from previous session */ $_SESSION =array(); ?> To start a new session and leave the old untouched, simply leave out the argument to `session_regenerate_id`. up down 6 php at cny dot de ¶ 21 years ago Also note that REMOTE_ADDR may change on every request if the user comes through a proxy farm. Most AOL-users do. up down 2 k-gun !! mail ¶ 9 years ago Document example is wrong with usage of "session.use_strict_mode" according to RFC (says: "warning error for session_id() when use_strice_mode=1" on https://wiki.php.net/rfc/strict_sessions ). So, this directive affects "session_id()" not "session_start()". So usage must be like this; <?php // first set ini ini_set ( 'session.use_strict_mode' , '0' ); // and session_id ( $sid ); // then // maybe run this: ini_restore('session.use_strict_mode'); // then go on... ?> Refs (ctrl+f & use_strict_mode); https://wiki.php.net/rfc/strict_sessions https://wiki.php.net/rfc/session-create-id http://php.net/manual/en/function.session-id.php#119997 up down 3 madsen at sjovedyr.dk ¶ 22 years ago I had problems with a proxy changing a visitors session_id-cookie, so he'd get a LOT of errors when visiting my site. I handled the bogus session-id's like this. (Note: It only works in versions > 4.3.2.) <?php // Start a session and suppress error-messages. @ session_start (); // Catch bogus session-id's. if (! preg_match ( "/^[0-9a-z]*$/i" , session_id ())) { // Output a warning about the messed up session-id. $error -> handleError ( "WARN" , "Your session id is messed up, you might not be able to use some features on this site." ); // Generate a fresh session-id. session_regenerate_id (); } // Site contents. ?> Hope someone can use it. up down 1 Nicolas dot Chachereau at Infomaniak dot ch ¶ 20 years ago Session_destroy() does not only destroy the data associated with the current session_id (i.e. the file if you use the default session save handler), but also the session itself: if you call session_destroy() and then session_regenerate_id(), it will return false, and session_id() won't return anything. In order to manipulate a session after destroying it, you need to restart it. So in fact, the code mentionned by chris won't work. If you want to destroy the file associated with the old session_id, try the following: <?php session_start (); $old_sessid = session_id (); session_regenerate_id (); $new_sessid = session_id (); session_id ( $old_sessid ); session_destroy (); //If you don't copy the $_SESSION array, you won't be able to use the data associated with the old session id. $old_session = $_SESSION ; session_id ( $new_sessid ); session_start (); $_SESSION = $old_session ; //... ?> Note: this technique will send 3 Set-Cookie headers (one on each session_start() and one on session_regenerate_id()). I don't think this is a problem, but if it appears to be one, you could either leave it alone and wait for the garbage collector to catch the file associated with the old session, or try to delete the file with unlink(). up down 1 soapergem at gmail dot com ¶ 17 years ago This can be a very dangerous function if you're not careful about how you handle things, because even though it generates a whole new set of session data, it keeps the old data "open" until the script terminates, locking out any other scripts trying to run concurrently with the old session id. Recently I came across a situation where I wanted to explicitly pass in a session ID, copy the data from that session into a *new* session, and then continue operating under that new session, thereby allowing other scripts to use the old one concurrently. But I quickly found that these "other scripts" would not execute until the first script finished--even though it had already started a new session--because it kept the old session open. So if you're trying to copy over session data to a new session to free up the old session for continued, concurrent use, here's some code to ensure nobody's feet get stepped on: <?php // get session id of an existing session $sid = $_GET [ 'sid' ]; // start the old session to retrieve $_SESSION data session_id ( $sid ); session_start (); // start a new session; this copies the $_SESSION data over session_regenerate_id (); // hang on to the new session id $sid = session_id (); // close the old and new sessions session_write_close (); // re-open the new session session_id ( $sid ); session_start (); /* main code here */ ?> This could probably be encapsulated into a function with one parameter as well to save space if it was a repeated thing. up down 0 primenetworkzx at gmail dot com ¶ 17 years ago If you are storing your session data in a database you have to manually update the session_id in the database. The session_set_save_handler() will not do it for you. function UpdateSessID() { $old_sess_id = session_id(); session_regenerate_id(false); $new_sess_id = session_id(); $query = "UPDATE `session_table` SET `session_id` = '$new_sess_id' WHERE session_id = '$old_sess_id'"; mysql_query($query); } Be sure to set session_regenerate_id() to FALSE since it's not really necessary to delete the whole record from MySQL and add it again. That's unnecessary overhead. Only changing the id matters. up down 0 dyer85 at gmail dot com ¶ 20 years ago There could be a potential problem with elger at NOSPAM dot yellowbee dot nl's a few posts below. In the code, was used the REQUEST_URI server variable, which, in some cases might already contain the query string. Therefore, always apending '?whatever=foo' would occasionally cause the script to malfunction. I suggest using PHP_SELF, which will not contain the query string after the file. up down -2 mikebranttx at gmail dot com ¶ 8 years ago Note that in current PHP 7.2 nightly builds example #2 above will not work as shown. You will get following error upon trying to turn strict mode back on after session_start(): "ini_set(): A session is active. You cannot change the session module's ini settings at this time" I suppose this means that for any session where you perform session ID regeneration or session ID forwarding (from a session for which a recent session ID regeneration was performed to the new session ID). That you will just have to live with strict mode being disabled for the remainder of that active session. I don't know that this is really a security concern so long as you are following a single-session per request design (i.e. you are not working with multiple concurrent sessions). up down -2 chris at knowledge dot tee-vee ¶ 20 years ago licp - no, session_regenerate_id() does not destroy any saved session data. elger, I prefer the following order [code] // populate $_SESSION with any previously saved session data for the current session_id session_start(); ... // delete any saved data associated with current session_id, $_SESSION is not changed session_destroy(); // change session_id, $_SESSION not altered session_regenerate_id(); ... // save any $_SESSION data under the current session_id session_close(); [/code] up down -1 antomsa at hotmail dot it ¶ 4 years ago <?php function my_session_regenerate_id () { ... session_start (); ... unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Within my_session_regenerate_id(), unset($_SESSION['destroyed']) and unset($_SESSION['new_session_id']) are useless because session_start() will open an empty session. They would be needed if built-in session_regenerate_id() was called. up down -4 kgm_india at yahoo dot co dot in ¶ 12 years ago as far as I have understood reading this online notes, session_name() is the name which is identified as session a through the cookies or http links. session_id is like a transaction within a session_name() and one session_name may have many session_id each session_id has the corresponding data stored. session_id are used in read and write callback under a session_name whatever it is, first call the session_name(), then call session_id () and then call start_session() start_session will open the session_name, then check the session_id called before and use it in the read or write call back for storing or retrieving data calling start_session() without session_name or session_id will use the default session_name and the default session_id in that order I hope if the order is followed there should not be any problems. do not call session_name or session_id after start_session(), if you are specific on using them. thank you for others note. up down -5 raido dot aasoja at gmail dot com ¶ 15 years ago A note on lost sessions and trying to fix it with session_regenerate_id: Make sure that you're not trying to push SimpleXML object to the session. It just won't go without first converting it to array. :) up down -3 sopel ¶ 20 years ago for php 5.1> user probably worth visiting is http://ilia.ws/archives/47-session_regenerate_id-Improvement.html up down -4 Alamin ¶ 7 years ago In the second example provided by php.net, should it call my_session_start inside the session regenerate method instead of directly calling session_start? I think it is an error. ＋ add a note Session-Funktionen session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://support.microsoft.com/es-es/microsoft-edge/microsoft-edge-datos-de-exploraci%C3%B3n-y-privacidad-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Microsoft Edge, datos de exploración y privacidad - Soporte técnico de Microsoft Saltar al contenido principal Microsoft Soporte técnico Soporte técnico Soporte técnico Inicio Microsoft 365 Office Productos Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows más ... Dispositivos Surface Accesorios de PC Xbox Juegos en PC HoloLens Surface Hub Garantías de hardware Cuenta y facturación Cuenta Microsoft Store & facturación Recursos Novedades Foros de la comunidadForos de la comunidad Administradores de Microsoft 365 Portal de la Pequeña Empresa Desarrollador Educación Comunicar una estafa de soporte técnico Seguridad del producto Más Comprar Microsoft 365 Todo Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Ofertas Pequeñas empresas Soporte Software Software Aplicaciones Windows IA OneDrive Outlook Paso de Skype a Teams OneNote Microsoft Teams PCs y dispositivos PCs y dispositivos Comprar Xbox Accesorios Entretenimiento Entretenimiento Xbox Game Pass Ultimate Xbox y juegos Juegos para PC Empresas Empresas Seguridad de Microsoft Azure Dynamics 365 Microsoft 365 para empresas Microsoft Industry Microsoft Power Platform Windows 365 Desarrolladores y TI Desarrolladores y TI Desarrollador de Microsoft Microsoft Learn Soporte técnico para aplicaciones del marketplace de IA Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Otro Otro Microsoft Rewards Seguridad y descargas gratuitas Educación Tarjetas regalo Licenciamiento Ver mapa del sitio Buscar Búsqueda de ayuda Sin resultados Cancelar Iniciar sesión Iniciar sesión con Microsoft Iniciar sesión o crear una cuenta Hola: Seleccione una cuenta diferente. Tiene varias cuentas Elija la cuenta con la que desea iniciar sesión. Microsoft Edge, datos de exploración y privacidad Se aplica a Privacy Microsoft Edge Windows 10 Windows 11 Microsoft Edge te ayuda a navegar, buscar, comprar en línea y mucho más. Como todos los navegadores modernos, Microsoft Edge te permite recopilar y almacenar datos específicos en su dispositivo, como las cookies, y te permite enviarnos información, como el historial de exploración, para que la experiencia sea lo más enriquecida, rápida y personal posible. Siempre que recopilamos datos, queremos asegurarnos de que sea la opción adecuada para ti. Algunas personas se preocupan de que se recopile su historial de exploración web. Por ese motivo, te indicamos qué datos se almacenan en tu dispositivo o los recopilamos nosotros. Tú eliges cómo controlar los datos que se recopilan. Para obtener más información sobre la privacidad en Microsoft Edge, te recomendamos revisar nuestra Declaración de privacidad . Qué datos se recopilan o almacenan y por qué Microsoft usa datos de diagnóstico para mejorar nuestros productos y servicios. Usamos estos datos para conocer mejor cómo funcionan nuestros productos y dónde se deben realizar mejoras. Microsoft Edge recopila un conjunto de datos de diagnóstico necesarios para mantener la seguridad de Microsoft Edge, al día y funcionando según lo esperado. Microsoft cree en la minimización de la recopilación de información y la pone en práctica. Nos esforzamos por recopilar solo la información que necesitamos y almacenarla solo durante el tiempo necesario para proporcionar un servicio o realizar análisis. Además, puedes controlar si compartes con Microsoft datos de diagnóstico opcionales asociados con el dispositivo, para resolver los problemas de los productos y ayudar a mejorar los productos y servicios de Microsoft. A medida que usas características y servicios en Microsoft Edge, los datos de diagnóstico sobre cómo usas esas características se envían a Microsoft. Microsoft Edge guarda el historial de exploración (información acerca de los sitios web que visite) en su dispositivo. Dependiendo de la configuración, el historial de exploración se envía a Microsoft, lo que nos ayuda a encontrar y solucionar problemas, así como a mejorar nuestros productos y servicios para todos los usuarios. Para administrar la recopilación de datos de diagnóstico opcionales en el explorador, selecciona Configuración y más > Configuración > Privacidad, búsqueda y servicios > Privacidad y activa o desactiva Enviar datos de diagnóstico opcionales para mejorar los productos de Microsoft . Esto incluye datos sobre la prueba de nuevas experiencias. Para terminar de hacer cambios en esta opción, reinicia Microsoft Edge. Activar esta opción permite que estos datos de diagnóstico opcionales se compartan con Microsoft desde otras aplicaciones con Microsoft Edge, como una aplicación de streaming de vídeo que hospeda la plataforma web de Microsoft Edge para transmitir el vídeo. La plataforma web de Microsoft Edge enviará información sobre cómo usa la plataforma web y los sitios que visites en la aplicación para Microsoft. Esta colección de datos está determinada por la configuración de los datos de diagnóstico opcionales en la configuración de privacidad, búsqueda y servicios de Microsoft Edge. En Windows 10, esta configuración viene determinada por la opción de datos de diagnóstico de Windows. Para cambiar la configuración de los datos de diagnóstico, selecciona Inicio > Configuración > Diagnósticos> Privacidad & comentarios . A partir del 6 de marzo de 2024, los datos de diagnóstico de Microsoft Edge se recopilan por separado de los datos de diagnóstico de Windows en Windows 10 (versión 22H2 y posteriores) y en dispositivos Windows 11 (versión 23H2 y posteriores) del Espacio Económico Europeo. Para estas versiones de Windows y en todas las demás plataformas, puedes cambiar la configuración en Microsoft Edge seleccionando Configuración y más > Configuración > Privacidad, búsqueda y servicios . En algunos casos, la configuración de los datos de diagnóstico podría estar administrada por la organización. Cuando busques algo, Microsoft Edge puede ofrecer sugerencias sobre lo que estás buscando. Para activar esta característica, selecciona Configuración y más > Configuración > Privacidad, búsqueda y servicios > Experiencias de búsqueda y conexión > barra de direcciones y búsqueda > Sugerencias de búsqueda y filtros , y activa Mostrar sugerencias de búsqueda y sitios usando mis caracteres escrito . Cuando empieces a escribir, la información que escribas en la barra de direcciones se enviará a tu proveedor de búsquedas predeterminado para proporcionarle sugerencias inmediatas de búsqueda y sitios web. Al usar el modo invitado o de exploración de InPrivate , Microsoft Edge recopila información sobre cómo usas el explorador en función de la configuración de los datos de diagnóstico de Windows o de la configuración de privacidad de Microsoft Edge, pero las sugerencias automáticas están desactivadas y no se recopila información sobre los sitios web que visitas. Microsoft Edge eliminará el historial de exploración, las cookies y los datos del sitio, así como las contraseñas, las direcciones y los datos de formulario al cerrar todas las ventanas de InPrivate. Para iniciar una nueva sesión de InPrivate, selecciona Configuración y más en un equipo o Pestañas en un dispositivo móvil. Microsoft Edge también tiene funciones que colaboran a protegeros a ti y tu contenido en línea. SmartScreen de Windows Defender bloquea automáticamente las descargas de sitios web y contenido que han sido notificados como malintencionados. SmartScreen de Windows Defender comprueba la dirección de la página web que esté visitando frente a una lista de direcciones de páginas web almacenadas en tu dispositivo que Microsoft considera legítimas. Las direcciones que no se encuentren en la lista del dispositivo, así como las direcciones de los archivos descarga, se enviarán a Microsoft y se compararán con una lista de páginas web y descargas de las que se ha notificado a Microsoft por ser peligrosas o sospechosas. Microsoft Edge puede guardar información para ayudar a simplificar tareas tediosas, como rellenar formularios y escribir contraseñas. Si eliges usar esas funciones, Microsoft Edge almacena la información en el dispositivo. Si has activado la sincronización para rellenar formularios, como direcciones o contraseñas, esta información se enviará a la nube de Microsoft y se almacenará con tu cuenta de Microsoft para que se sincronice en todas las versiones con sesión iniciada de Microsoft Edge. Puedes administrar estos datos desde Configuración y más > Configuración > Perfiles > Sincronización . Para integrar tu experiencia de navegación con otras actividades que realizas en tu dispositivo, Microsoft Edge comparte tu historial de exploración con Microsoft Windows a través de su Indexador. Esta información se almacena localmente en el dispositivo. Incluye las direcciones URL, una categoría en la que la dirección URL podría ser relevante, como "más visitada", "visitada recientemente" o "cerrada recientemente", y también una frecuencia relativa o recenencia dentro de cada categoría. Los sitios web que visitas en modo InPrivate no se compartirán. Esta información estará disponible para otras aplicaciones del dispositivo, como el menú Inicio o la barra de tareas. Puedes administrar esta función seleccionando Configuración y más > Configuración > Perfiles y activando o desactivando Compartir datos de exploración con otras funciones de Windows . Si está desactivada, se eliminarán todos los datos compartidos anteriormente. Para evitar que se copien algunos contenidos de música y vídeo, algunos sitios web de streaming almacenan datos de administración de derechos digitales (DRM) en su dispositivo, incluyendo un identificador único (Id.) y licencias multimedia. Cuando vayas a uno de estos sitios web, se recuperará la información DRM para asegurarse de que tengas permiso para usar el contenido. Microsoft Edge también almacena cookies, que son pequeños archivos que se van colocando en el dispositivo conforme se navega por la Web. Muchos sitios web usan cookies para almacenar información sobre tus preferencias y configuración, como guardar los artículos en el carro de la compra para que no tengas que agregarlos cada vez que visites los sitios. Algunos sitios web también usan cookies para recopilar información sobre tu actividad en línea, para mostrarte publicidad basada en intereses. Microsoft Edge ofrece opciones para borrar las cookies y bloquear el que los sitios web guarden cookies en el futuro. Microsoft Edge enviará solicitudes de No realizar seguimiento a los sitios web cuando la opción Enviar solicitudes de No realizar seguimiento esté activada. Esta opción está disponible en Configuración y más > Configuración > Privacidad, búsqueda y servicios > Privacidad > Enviar solicitudes de "No realizar seguimiento". Pese a ello, los sitios web pueden seguir tus actividades incluso tras haber enviado una solicitud de No realizar seguimiento. Cómo borrar datos recopilados o almacenados por Microsoft Edge Para borrar la información de exploración almacenada en tu dispositivo, como las contraseñas o cookies guardadas: En Microsoft Edge, selecciona Configuración y más > Configuración > Privacidad, búsqueda y servicios > Borrar datos de exploración . Selecciona Elegir lo que se debe borrar junto a Borrar datos de exploración ahora. En Intervalo de tiempo , elige un intervalo de tiempo. Activa la casilla situada junto a cada tipo de datos que quieras borrar y, a continuación, selecciona Borrar ahora . Si lo desea, puede seleccionar Elegir qué se debe borrar cada vez que se cierra el explorador y elegir qué tipos de datos se deben borrar. Obtén más información sobre lo que se elimina de cada elemento del historial de exploración . Para borrar el historial de exploración que Microsoft recopila: Para ver el historial de exploración asociado a tu cuenta, inicia sesión en tu cuenta en account.microsoft.com . Además, también tienes la opción de borrar los datos de exploración que Microsoft ha recopilado mediante el Panel de privacidad de Microsoft . Para eliminar el historial de exploración y otros datos de diagnóstico asociados con tu dispositivo Windows 10, selecciona Inicio > Configuración > Diagnósticos> Privacidad & comentarios y, a continuación, selecciona Eliminar en Eliminar datos de diagnóstico . Para borrar el historial de exploración compartido con otras características de Microsoft en el dispositivo local: En Microsoft Edge, selecciona Configuración y más > Configuración > Perfiles . Selecciona Compartir datos de exploración con otras funciones de Windows . Cambia esta opción a desactivado . Cómo administrar la configuración de privacidad en Microsoft Edge Para revisar y personalizar la configuración de privacidad, selecciona Configuración y más > Configuración > Privacidad, búsqueda y servicios . > Privacidad. Para más información sobre la privacidad en Microsoft Edge, lee las Notas de privacidad de Microsoft Edge . SUSCRIBIRSE A FUENTES RSS ¿Necesita más ayuda? ¿Quiere más opciones? Descubrir Comunidad Póngase en contacto con nosotros Explore las ventajas de las suscripciones, examine los cursos de aprendizaje, aprenda a proteger su dispositivo y mucho más. Ventajas de la suscripción de Microsoft 365 Aprendizaje de Microsoft 365 Seguridad de Microsoft Centro de accesibilidad Las comunidades le ayudan a formular y responder preguntas, enviar comentarios y leer a expertos con conocimientos extensos. Pregunte en Microsoft Community Microsoft Tech Community Windows Insiders Microsoft 365 Insiders Encuentre soluciones a problemas comunes u obtenga ayuda de un agente de soporte técnico. Soporte en línea ¿Le ha sido útil esta información? Sí No ¡Gracias! ¿Tiene alguna otra sugerencia para Microsoft? ¿Puede ayudarnos a mejorar? (Envíe comentarios a Microsoft para que podamos ayudarle.) ¿Cuál es tu grado de satisfacción con la calidad del lenguaje? ¿Qué le aportó a su experiencia? Solucionó mi problema Borrar instrucciones Ha sido fácil de seguir No usaba jerga Las imágenes han sido de ayuda Calidad de la traducción No coincidían con mi pantalla Instrucciones incorrectas Demasiado técnico No hay suficiente información No hay suficientes imágenes Calidad de la traducción ¿Tiene algún comentario adicional? (Opcional) Enviar comentarios Si presiona Enviar, sus comentarios se usarán para mejorar los productos y servicios de Microsoft. El administrador de TI podrá recopilar estos datos. Declaración de privacidad. ¡Gracias por sus comentarios! × Novedades Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot para organizaciones Copilot para uso personal Microsoft 365 Explora los productos de Microsoft Aplicaciones de Windows 11 Microsoft Store Perfil de la cuenta Centro de descarga Soporte de Microsoft Store Devoluciones Seguimiento de pedidos Reciclar Garantías comerciales Educación Microsoft Educación Dispositivos para educación Microsoft Teams para Educación Microsoft 365 Educación Office Educación Formación y desarrollo de educadores Ofertas para estudiantes y padres Azure para estudiantes Empresas Seguridad de Microsoft Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Pequeñas empresas Desarrolladores y TI Desarrollador de Microsoft Microsoft Learn Soporte técnico para aplicaciones del marketplace de IA Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Compañía Oportunidades de empleo Acerca de Microsoft Noticias de la compañía Privacidad en Microsoft Inversores Sostenibilidad Español (España, alfabetización internacional) Icono de exclusión de opciones de privacidad Tus opciones de privacidad Icono de exclusión de opciones de privacidad Tus opciones de privacidad Privacidad de la salud del consumidor Ponte en contacto con Microsoft Privacidad Gestionar cookies Condiciones de uso Marcas registradas Sobre nuestra publicidad Docs de cumplimiento de la UE Informes regulatorios © Microsoft 2026 | 2026-01-13T09:30:34 |
https://support.microsoft.com/et-ee/windows/k%C3%BCpsiste-haldamine-microsoft-edge-is-vaatamine-lubamine-blokeerimine-kustutamine-ja-kasutamine-168dab11-0753-043d-7c16-ede5947fc64d#supArticleContent | Küpsiste haldamine Microsoft Edge’is: vaatamine, lubamine, blokeerimine, kustutamine ja kasutamine - Microsofti tugiteenus Seotud teemad × Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Põhisisu juurde Microsoft Tugi Tugi Tugi Avaleht Microsoft 365 Office Tooted Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows rohkem… Seadmed Surface Arvuti tarvikud Xbox Arvutimängud HoloLens Surface Hub Riistvara garantiid Konto ja arveldamine konto Microsoft Store ja arveldamine Ressursid Mis on uut? Kogukonnafoorumid Microsoft 365 administraatorid Väikeettevõtete portaal Arendaja Haridus Teatage tehnilise toega seotud pettusest Tooteohutus Rohkem Osta Microsoft 365 Kogu Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Tugi Tarkvara Tarkvara Windowsi rakendused AI OneDrive Outlook Üleminek Skype'ilt Teamsile OneNote Microsoft Teams Arvutid ja seadmed Arvutid ja seadmed Accessories Meelelahutus Meelelahutus PC-mängud Äri Äri Microsofti turve Azure Dynamics 365 Microsoft 365 ettevõtteversioon Microsoft Industry Microsoft Power Platform Windows 365 Arendaja ja IT Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Visual Studio Marketplace Rewards Muud Muud Tasuta allalaadimised ja turve Kuva saidikaart Otsing Spikri otsing Tulemid puuduvad Loobu Logi sisse Logige sisse Microsofti kontoga Logige sisse või looge konto. Tere! Valige mõni muu konto. Teil on mitu kontot Valige konto, millega soovite sisse logida. Seotud teemad Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Küpsiste haldamine Microsoft Edge’is: vaatamine, lubamine, blokeerimine, kustutamine ja kasutamine Rakenduskoht Windows 10 Windows 11 Microsoft Edge Küpsised on väikesed andmekildud, mida külastatavad veebisaidid teie seadmesse salvestavad. Need täidavad mitmesuguseid eesmärke, nagu sisselogimisteabe meeldejätmine, saidieelistused ja kasutaja käitumise jälgimine. Siiski võite soovida kustutada küpsised privaatsuse tagamiseks või sirvimisprobleemide lahendamiseks. Sellest artiklist leiate juhised, kuidas teha järgmist. Kuva kõik küpsised Luba kõik küpsised Kindla veebisaidi küpsiste lubamine Blokeeri kolmandate osapoolte küpsised Blokeeri kõik küpsised Kindla saidi küpsiste blokeerimine Kustuta kõik küpsised Kindlalt saidilt küpsiste kustutamine Kustutage küpsised iga kord, kui brauseri sulgete Küpsiste kasutamine lehe kiiremaks sirvimiseks eellaadimiseks Kuva kõik küpsised Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Valige Küpsised , seejärel klõpsake kõigi salvestatud küpsiste ja seotud saiditeabe kuvamiseks nuppu Kuva kõik küpsised ja saidiandmed . Luba kõik küpsised Küpsiste lubamisega saavad veebisaidid salvestada ja tuua teie brauseris andmeid, mis võivad teie sirvimiskogemust täiustada, kui jätate meelde teie eelistused ja sisselogimisteabe. Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Kõigi küpsiste lubamiseks valige Küpsised ja lubage tumblerlüliti Luba saitidel küpsiseandmeid salvestada ja lugeda (soovitatav). Kindla saidi küpsiste lubamine Küpsiste lubamisega saavad veebisaidid salvestada ja tuua teie brauseris andmeid, mis võivad teie sirvimiskogemust täiustada, kui jätate meelde teie eelistused ja sisselogimisteabe. Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Valige Küpsised ja minge jaotisse Lubatud küpsiste salvestamine. Küpsiste lubamiseks saidipõhiselt valige Lisa sait , sisestades saidi URL-i. Blokeeri kolmandate osapoolte küpsised Kui te ei soovi, et kolmandate osapoolte saidid salvestaksid teie arvutisse küpsiseid, saate küpsised blokeerida. Küpsiste blokeerimisel võib juhtuda, et mõnda lehte ei kuvata õigesti või kuvatakse mõnel saidil teade, et selle saidi vaatamiseks peate küpsised lubama. Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Valige Küpsised ja lubage tumblerlüliti Blokeeri kolmandate osapoolte küpsised. Blokeeri kõik küpsised Kui te ei soovi, et kolmandate osapoolte saidid salvestaksid teie arvutisse küpsiseid, saate küpsised blokeerida. Küpsiste blokeerimisel võib juhtuda, et mõnda lehte ei kuvata õigesti või kuvatakse mõnel saidil teade, et selle saidi vaatamiseks peate küpsised lubama. Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Küpsiste blokeerimiseks valige Küpsised ja keelake luba saitidel küpsiseandmeid salvestada ja lugeda (soovitatav). Kindla saidi küpsiste blokeerimine Microsoft Edge võimaldab teil teatud saidi küpsised blokeerida, kuid see võib takistada teatud lehtede õiget kuvamist või saate mõnelt saidilt teate, et selle saidi vaatamiseks peate küpsised lubama. Kindla saidi küpsiste blokeerimiseks tehke järgmist. Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Valige Küpsised ja minge jaotisse Pole lubatud küpsiseid salvestada ja lugeda . Küpsiste saidipõhiseks blokeerimiseks valige Lisa sait , sisestades saidi URL-i. Kustuta kõik küpsised Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Valige Sirvimisandmete kustutamine ja seejärel valige suvand Kustuta sirvimisandmete kustutamine kohe kõrvalt Valige kustutatav sisu. Valige jaotises Ajavahemik loendist ajavahemik. Märkige ruut Küpsised ja muud saidiandmed ning seejärel valige Tühjenda kohe . Märkus.: Teise võimalusena võite küpsised kustutada, vajutades koos klahvikombinatsiooni CTRL + SHIFT + DELETE ja jätkates seejärel juhistega 4 ja 5. Kõik teie küpsised ja muud saidiandmed kustutatakse nüüd valitud ajavahemiku jooksul. See logib teid enamikult saitidelt välja. Kindlalt saidilt küpsiste kustutamine Avage Brauser Edge, valige Sätted ja muud > Sätted > Privaatsus, otsing ja teenused . Valige Küpsised , seejärel klõpsake käsku Kuva kõik küpsised ja saidiandmed ning otsige saiti, mille küpsised soovite kustutada. Valige saidist, mille küpsiseid soovite kustutada, paremal olev allanool ja valige Kustuta . Teie valitud saidi küpsised kustutatakse. Korrake seda toimingut iga saidi puhul, mille küpsised soovite kustutada. Kustutage küpsised iga kord, kui brauseri sulgete Avage Brauser Edge, valige Sätted ja muud > Sätted > Privaatsus, otsing ja teenused . Valige Käsk Kustuta sirvimisandmed ja seejärel valige Käsk kustutatav sisu iga kord, kui brauseri sulgete . Lülitage tumblerlüliti Küpsised ja muud saidiandmed sisse. Kui see funktsioon on sisse lülitatud, kustutatakse iga kord, kui sulete oma Edge'i brauseri, kõik küpsised ja muud saidiandmed. See logib teid enamikult saitidelt välja. Küpsiste kasutamine lehe kiiremaks sirvimiseks eellaadimiseks Avage Brauseribrauser Edge, valige brauseriakna paremas ülanurgas Sätted ja palju muud . Valige Sätted > Privaatsus, otsing ja teenused . Valige Küpsised ja lubage lehtede kiiremaks sirvimiseks ja otsimiseks eellaadimine. TELLIGE RSS-KANALID Kas vajate veel abi? Kas soovite rohkem valikuvariante? Tutvustus Kogukonnafoorum Kontaktteave Siin saate tutvuda tellimusega kaasnevate eelistega, sirvida koolituskursusi, õppida seadet kaitsma ja teha veel palju muud. Microsoft 365 tellimuse eelised Microsoft 365 koolitus Microsofti turbeteenus Hõlbustuskeskus Kogukonnad aitavad teil küsimusi esitada ja neile vastuseid saada, anda tagasisidet ja saada nõu rikkalike teadmistega asjatundjatelt. Nõu küsimine Microsofti kogukonnafoorumis Microsofti spetsialistide kogukonnafoorum Windows Insideri programmis osalejad Microsoft 365 Insideri programmis osalejad Leidke lahendused levinud probleemidele või võtke ühendust klienditeenindajaga. Võrgutugi Kas sellest teabest oli abi? Jah Ei Aitäh! Veel tagasisidet Microsoftile? Kas saaksite aidata meil teenust paremaks muuta? (Saatke Microsoftile tagasisidet, et saaksime aidata.) Kui rahul te keelekvaliteediga olete? Mis mõjutas teie hinnangut? Leidsin oma probleemile lahenduse Juhised olid selged Tekstist oli lihtne aru saada Tekstis pole žargooni Piltidest oli abi Tõlkekvaliteet Tekst ei vastanud minu ekraanipildile Valed juhised Liiga tehniline Pole piisavalt teavet Pole piisavalt pilte Tõlkekvaliteet Kas soovite anda veel tagasisidet? (Valikuline) Saada tagasiside Kui klõpsate nuppu Edasta, kasutatakse teie tagasisidet Microsofti toodete ja teenuste täiustamiseks. IT-administraator saab neid andmeid koguda. Privaatsusavaldus. Täname tagasiside eest! × Mis on uut? Copilot organisatsioonidele Copilot isiklikuks kasutuseks Microsoft 365 Windows 11 rakendused Microsoft Store Konto profiil Allalaadimiskeskus Tagastused Tellimuse jälgimine Ringlussevõtt Commercial Warranties Haridus Microsoft Education Haridusseadmed Microsoft Teams haridusasutustele Microsoft 365 Education Office Education Haridustöötajate koolitus ja arendus Pakkumised õpilastele ja vanematele Azure õpilastele Äri Microsofti turve Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamsi jaoks Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Ettevõte Töökohad Teave Microsofti kohta Privaatsus Microsoftis Investorid Jätkusuutlikkus Eesti (Eesti) Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Tarbijaseisundi privaatsus Võtke Microsoftiga ühendust Privaatsus Halda küpsiseid Kasutustingimused Kaubamärgid Reklaamide kohta EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-testing-debugging.html | Test and debug Lambda@Edge functions - Amazon CloudFront Test and debug Lambda@Edge functions - Amazon CloudFront Documentation Amazon CloudFront Developer Guide Test your Lambda@Edge functions Identify Lambda@Edge function errors in CloudFront Troubleshoot invalid Lambda@Edge function responses (validation errors) Troubleshoot Lambda@Edge function execution errors Determine the Lambda@Edge Region Determine if your account pushes logs to CloudWatch Test and debug Lambda@Edge functions It's important to test your Lambda@Edge function code standalone, to make sure that it completes the intended task, and to do integration testing, to make sure that the function works correctly with CloudFront. During integration testing or after your function has been deployed, you might need to debug CloudFront errors, such as HTTP 5xx errors. Errors can be an invalid response returned from the Lambda function, execution errors when the function is triggered, or errors due to execution throttling by the Lambda service. Sections in this topic share strategies for determining which type of failure is the issue, and then steps you can take to correct the problem. Note When you review CloudWatch log files or metrics when you're troubleshooting errors, be aware that they are displayed or stored in the AWS Region closest to the location where the function executed. So, if you have a website or web application with users in the United Kingdom, and you have a Lambda function associated with your distribution, for example, you must change the Region to view the CloudWatch metrics or log files for the London AWS Region. For more information, see Determine the Lambda@Edge Region . Topics Test your Lambda@Edge functions Identify Lambda@Edge function errors in CloudFront Troubleshoot invalid Lambda@Edge function responses (validation errors) Troubleshoot Lambda@Edge function execution errors Determine the Lambda@Edge Region Determine if your account pushes logs to CloudWatch Test your Lambda@Edge functions There are two steps to testing your Lambda function: standalone testing and integration testing. Test standalone functionality Before you add your Lambda function to CloudFront, make sure to test the functionality first by using the testing capabilities in the Lambda console or by using other methods. For more information about testing in the Lambda console, see Invoke a Lambda function using the console in the AWS Lambda Developer Guide . Test your function's operation in CloudFront It's important to complete integration testing, where your function is associated with a distribution and runs based on a CloudFront event. Make sure that the function is triggered for the right event, and returns a response that is valid and correct for CloudFront. For example, make sure that the event structure is correct, that only valid headers are included, and so on. As you iterate on integration testing with your function in the Lambda console, refer to the steps in the Lambda@Edge tutorial as you modify your code or change the CloudFront trigger that calls your function. For example, make sure that you're working in a numbered version of your function, as described in this step of the tutorial: Step 4: Add a CloudFront trigger to run the function . As you make changes and deploy them, be aware that it will take several minutes for your updated function and CloudFront triggers to replicate across all Regions. This typically takes a few minutes but can take up to 15 minutes. You can check to see if replication is finished by going to the CloudFront console and viewing your distribution. To check if your replication has finished deploying Open the CloudFront console at https://console.aws.amazon.com/cloudfront/v4/home . Choose the distribution name. Check for the distribution status to change from In Progress back to Deployed , which means that your function has been replicated. Then follow the steps in the next section to verify that the function works. Be aware that testing in the console only validates your function's logic, and does not apply any service quotas (formerly known as limits) that are specific to Lambda@Edge. Identify Lambda@Edge function errors in CloudFront After you've verified that your function logic works correctly, you might still see HTTP 5xx errors when your function runs in CloudFront. HTTP 5xx errors can be returned for a variety of reasons, which can include Lambda function errors or other issues in CloudFront. If you use Lambda@Edge functions, you can use graphs in the CloudFront console to help track down what's causing the error, and then work to fix it. For example, you can see if HTTP 5xx errors are caused by CloudFront or by Lambda functions, and then, for specific functions, you can view related log files to investigate the issue. To troubleshoot HTTP errors in general in CloudFront, see the troubleshooting steps in the following topic: Troubleshooting error response status codes in CloudFront . What causes Lambda@Edge function errors in CloudFront There are several reasons why a Lambda function might cause an HTTP 5xx error, and the troubleshooting steps you should take depend on the type of error. Errors can be categorized as the following: A Lambda function execution error An execution error results when CloudFront doesn't get a response from Lambda because there are unhandled exceptions in the function or there's an error in the code. For example, if the code includes callback(Error). An invalid Lambda function response is returned to CloudFront After the function runs, CloudFront receives a response from Lambda. An error is returned if the object structure of the response doesn't conform to the Lambda@Edge event structure , or the response contains invalid headers or other invalid fields. The execution in CloudFront is throttled due to Lambda service quotas (formerly known as limits) The Lambda service throttles executions in each Region, and returns an error if you exceed the quota. For more information, see Quotas on Lambda@Edge . How to determine the type of failure To help you decide where to focus as you debug and work to resolve errors returned by CloudFront, it's helpful to identify why CloudFront is returning an HTTP error. To get started, you can use the graphs provided in the Monitoring section of the CloudFront console on the AWS Management Console. For more information about viewing graphs in the Monitoring section of the CloudFront console, see Monitor CloudFront metrics with Amazon CloudWatch . The following graphs can be especially helpful when you want to track down whether errors are being returned by origins or by a Lambda function, and to narrow down the type of issue when it's an error from a Lambda function. Error rates graph One of the graphs that you can view on the Overview tab for each of your distributions is an Error rates graph. This graph displays the rate of errors as a percentage of total requests coming to your distribution. The graph shows the total error rate, total 4xx errors, total 5xx errors, and total 5xx errors from Lambda functions. Based on the error type and volume, you can take steps to investigate and troubleshoot the cause. If you see Lambda errors, you can investigate further by looking at the specific types of errors that the function returns. The Lambda@Edge errors tab includes graphs that categorize function errors by type to help you pinpoint the issue for a specific function. If you see CloudFront errors, you can troubleshoot and work to fix origin errors or change your CloudFront configuration. For more information, see Troubleshooting error response status codes in CloudFront . Execution errors and invalid function responses graphs The Lambda@Edge errors tab includes graphs that categorize the Lambda@Edge errors for a specific distribution, by type. For example, one graph shows all execution errors by AWS Region. To make it easier to troubleshoot issues, you can look for specific problems by opening and examining the log files for specific functions by Region. To view log files for a specific function by Region On the Lambda@Edge errors tab, under Associated Lambda@Edge functions , choose the function name, and then choose View metrics . Next, on the page with your function name, in the upper-right corner, choose View function logs , and then choose a Region. For example, if you see issues in the Errors graph for the US West (Oregon) Region, choose that Region from the dropdown list. This opens the Amazon CloudWatch console. In the CloudWatch console for that Region, under Log streams , choose a log stream to view the events for the function. In addition, read the following sections in this chapter for more recommendations about troubleshooting and fixing errors. Throttles graph The Lambda@Edge errors tab also includes a Throttles graph. On occasion, the Lambda service throttles your function invocations on per Region basis, if you reach the regional concurrency quota (formerly known as limit). If you see a limit exceeded error, your function has reached a quota that the Lambda service imposes on executions in a Region. For more information, including how to request an increase in the quota, see Quotas on Lambda@Edge . For an example about how to use this information in troubleshooting HTTP errors, see Four steps for debugging your content delivery on AWS . Troubleshoot invalid Lambda@Edge function responses (validation errors) If you identify that your problem is a Lambda validation error, it means that your Lambda function is returning an invalid response to CloudFront. Follow the guidance in this section to take steps to review your function and make sure that your response conforms to CloudFront requirements. CloudFront validates the response from a Lambda function in two ways: The Lambda response must conform to the required object structure. Examples of bad object structure include the following: unparsable JSON, missing required fields, and an invalid object in the response. For more information, see the Lambda@Edge event structure . The response must include only valid object values. An error will occur if the response includes a valid object but has values that are not supported. Examples include the following: adding or updating disallowed or read-only headers (see Restrictions on edge functions ), exceeding the maximum body size (see Restrictions on the Size of the Generated Response in the Lambda@Edge Errors topic), and invalid characters or values (see the Lambda@Edge event structure ). When Lambda returns an invalid response to CloudFront, error messages are written to log files which CloudFront pushes to CloudWatch in the Region of where the Lambda function executed. It's the default behavior to send the log files to CloudWatch when there's an invalid response. However, if you associated a Lambda function with CloudFront before the functionality was released, it might not be enabled for your function. For more information, see Determine if Your Account Pushes Logs to CloudWatch later in the topic. CloudFront pushes log files to the Region corresponding to where your function executed, in the log group that's associated with your distribution. Log groups have the following format: /aws/cloudfront/LambdaEdge/ DistributionId , where DistributionId is your distribution's ID. To determine the Region where you can find the CloudWatch log files, see Determining the Lambda@Edge Region later in this topic. If the error is reproducible, you can create a new request that results in the error and then find the request id in a failed CloudFront response ( X-Amz-Cf-Id header) to locate a single failure in log files. The log file entry includes information that can help you identify why the error is being returned, and also lists the corresponding Lambda request id so you can analyze the root cause in the context of a single request. If an error is intermittent, you can use CloudFront access logs to find the request id for a request that has failed, and then search CloudWatch logs for the corresponding error messages. For more information, see the previous section, Determining the Type of Failure . Troubleshoot Lambda@Edge function execution errors If the problem is a Lambda execution error, it can be helpful to create logging statements for Lambda functions, to write messages to CloudWatch log files that monitor the execution of your function in CloudFront and determine if it's working as expected. Then you can search for those statements in the CloudWatch log files to verify that your function is working. Note Even if you haven't changed your Lambda@Edge function, updates to the Lambda function execution environment might affect it and could return an execution error. For information about testing and migrating to a later version, see Upcoming updates to the AWS Lambda and AWS Lambda@Edge execution environment. Determine the Lambda@Edge Region To see the Regions where your Lambda@Edge function is receiving traffic, view metrics for the function on the CloudFront console on the AWS Management Console. Metrics are displayed for each AWS Region. On the same page, you can choose a Region and view log files for that Region so you can investigate issues. You must review CloudWatch log files in the correct AWS Region to see the log files created when CloudFront executed your Lambda function. For more information about viewing graphs in the Monitoring section of the CloudFront console, see Monitor CloudFront metrics with Amazon CloudWatch . Determine if your account pushes logs to CloudWatch By default, CloudFront enables logging invalid Lambda function responses, and pushes the log files to CloudWatch by using one of the Service-linked roles for Lambda@Edge . If you have Lambda@Edge functions that you added to CloudFront before the invalid Lambda function response log feature was released, logging is enabled when you next update your Lambda@Edge configuration, for example, by adding a CloudFront trigger. You can verify that pushing the log files to CloudWatch is enabled for your account by doing the following: Check to see if the logs appear in CloudWatch – Make sure that you look in the Region where the Lambda@Edge function executed. For more information, see Determine the Lambda@Edge Region . Determine if the related service-linked role exists in your account in IAM – You must have the IAM role AWSServiceRoleForCloudFrontLogger in your account. For more information about this role, see Service-linked roles for Lambda@Edge . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Add triggers to a Lambda@Edge function Delete functions and replicas Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-generating-http-responses.html | Arbeiten mit Anforderungen und Antworten - Amazon CloudFront Arbeiten mit Anforderungen und Antworten - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch Verwenden von Funktionen mit Origin Failover Generieren von HTTP-Antworten in Anforderungsauslösern Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern Zugriff auf den Anforderungstext über die Option „Text einschließen“ Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich. Arbeiten mit Anforderungen und Antworten Informationen zur Verwendung von Lambda@Edge-Anforderungen und -Antworten finden Sie in den folgenden Themen: Themen Verwenden von Lambda@Edge-Funktionen mit Origin Failover Generieren von HTTP-Antworten in Anforderungsauslösern Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern Zugriff auf den Anforderungstext über die Option „Text einschließen“ Verwenden von Lambda@Edge-Funktionen mit Origin Failover Sie können Lambda @Edge -Funktionen mit CloudFront Verteilungen verwenden, die Sie mit Ursprungsgruppen eingerichtet haben, z. B. für Origin-Failover, das Sie konfigurieren, um eine hohe Verfügbarkeit sicherzustellen. Um eine Lambda-Funktion mit einer Ursprungsgruppe zu verwenden, geben Sie die Funktion in einem Ursprungsanfragen- oder Ursprungsantwort-Auslöser für eine Ursprungsgruppe an, wenn Sie das Zwischenspeicher-Verhalten erstellen. Weitere Informationen finden Sie hier: Erstellen von Ursprungsgruppen: Erstellen einer Ursprungsgruppe Funktionsweise von Origin Failover mit Lambda@Edge: Verwenden von Origin Failover mit Lambda@Edge-Funktionen Generieren von HTTP-Antworten in Anforderungsauslösern Wenn Sie CloudFront eine Anfrage erhalten, können Sie eine Lambda-Funktion verwenden, um eine HTTP-Antwort zu generieren, die direkt an den Betrachter CloudFront zurückkehrt, ohne die Antwort an den Ursprung weiterzuleiten. Die Generierung von HTTP-Antworten reduziert die Auslastung des Ursprungs und reduziert in der Regel auch die Latenzzeit für den Viewer. Einige häufige Szenarien für die Generierung von HTTP-Antworten sind die folgenden: Rückgabe einer kleinen Website an den Viewer. Rückgabe eines HTTP 301- oder 302-Statuscodes, um den Benutzer auf eine andere Webseite umzuleiten. Rückgabe eines HTTP 401-Statuscodes an den Viewer, wenn sich der Benutzer nicht authentifiziert hat. Eine Lambda@Edge-Funktion kann eine HTTP-Antwort generieren, wenn die folgenden CloudFront-Ereignisse auftreten: Viewer-Anforderungsereignisse Wenn eine Funktion durch ein Viewer-Anforderungsereignis ausgelöst wird, CloudFront gibt sie die Antwort an den Betrachter zurück und speichert sie nicht im Cache. Ursprungsanforderungsereignisse Wenn eine Funktion durch ein Origin-Anforderungsereignis ausgelöst wird, CloudFront wird im Edge-Cache nach einer Antwort gesucht, die zuvor von der Funktion generiert wurde. Wenn sich die Antwort im Cache befindet, wird die Funktion nicht ausgeführt und CloudFront gibt die zwischengespeicherte Antwort an den Viewer zurück. Wenn sich die Antwort nicht im Cache befindet, wird die Funktion ausgeführt, CloudFront gibt die Antwort an den Betrachter zurück und speichert sie ebenfalls im Cache. Beispiel-Code zum Generieren von HTTP-Antworten finden Sie unter Beispielfunktionen für Lambda@Edge . Sie können auch die HTTP-Antworten in Antwortauslösern ersetzen. Weitere Informationen finden Sie unter Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern . Programmiermodell Dieser Abschnitt enthält Informationen über das Programmiermodell für die Nutzung von Lambda@Edge zum Generieren von HTTP-Antworten. Themen Antwortobjekt Fehler Pflichtfelder Antwortobjekt Die Antwort, die Sie als result -Parameter der callback -Methode zurückgeben, sollte folgenden Aufbau haben (beachten Sie, dass nur das status -Feld erforderlich ist). const response = { body: 'content', bodyEncoding: 'text' | 'base64', headers: { 'header name in lowercase': [ { key: 'header name in standard case', value: 'header value' }], ... }, status: 'HTTP status code (string)', statusDescription: 'status description' }; Das Antwortobjekt kann die folgenden Werte enthalten: body Der Text, falls vorhanden, den Sie in der generierten Antwort zurückgeben CloudFront möchten. bodyEncoding Die Kodierung für den Wert, den Sie in body festgelegt haben. Die einzigen gültigen Codierungen sind text und base64 . Wenn Sie body in das response Objekt aufnehmen, aber weglassen bodyEncoding , wird der CloudFront Hauptteil als Text behandelt. Wenn Sie bodyEncoding als base64 festlegen, der Body jedoch kein gültiges base64 ist, gibt CloudFront einen Fehler zurück. headers Header, die Sie in der generierten Antwort zurückgeben möchten CloudFront . Beachten Sie Folgendes: Die Schlüssel im headers -Objekt sind kleingeschriebene Versionen von Standard-HTTP-Header-Namen. Über diese Kleinbuchstaben-Schlüssel haben Sie Zugriff auf die Headerwerte (ohne Berücksichtigung von Groß-/Kleinschreibung). Jeder Header (z. B. headers["accept"] oder headers["host"] ) ist ein Array mit Schlüssel-Wert-Paaren. Für einen bestimmten Header enthält das Array ein Schlüssel-Wert-Paar für jeden Wert in der generierten Antwort. key (optional) ist der von Groß- und Kleinschreibung unabhängige Name des Headers, wie er in einer HTTP-Anforderung erscheint (z. B. accept oder host ). Geben Sie value als Header-Wert an. Wenn Sie den Header-Schlüsselteil des Schlüssel-Wert-Paares nicht aufnehmen, fügt Lambda@Edge automatisch einen Header-Schlüssel mit dem von Ihnen angegebenen Header-Namen ein. Unabhängig davon, wie Sie den Header-Namen formatiert haben, wird der automatisch eingefügte Header-Schlüssel mit einem großen Anfangsbuchstaben für jeden Teil formatiert, wobei die einzelnen Teile durch Bindestriche (-) getrennt werden. Beispielsweise können Sie einen Header wie den folgenden ohne Header-Schlüssel hinzufügen: 'content-type': [ { value: 'text/html;charset=UTF-8' }] In diesem Beispiel erstellt Lambda@Edge den folgenden Header-Schlüssel: Content-Type . Weitere Informationen zu Einschränkungen zur Verwendung von Headern finden Sie unter Einschränkungen für Edge-Funktionen . status Den HTTP-Statuscode . Geben Sie den Statuscode als Zeichenfolge an. CloudFront verwendet den bereitgestellten Statuscode für Folgendes: Rückgabe in der Antwort Cache im CloudFront Edge-Cache, wenn die Antwort durch eine Funktion generiert wurde, die durch ein Origin-Request-Ereignis ausgelöst wurde Loggen Sie sich ein CloudFront Zugriffsprotokolle (Standardprotokolle) Wenn der status -Wert nicht zwischen 200 und 599 liegt, gibt CloudFront einen Fehler an den Betrachter zurück. statusDescription Die Beschreibung, die CloudFront Sie zusammen mit dem HTTP-Statuscode in der Antwort zurückgeben möchten. Sie müssen keine Standardbeschreibungen verwenden (z. B. OK für einen HTTP-Statuscode 200). Fehler Es folgen mögliche Fehler für generierte HTTP-Antworten. Antwort enthält einen Body und legt 204 (No Content) als Status fest Wenn eine Funktion durch eine Viewer-Anfrage ausgelöst wird, CloudFront gibt sie dem Viewer einen HTTP 502-Statuscode (Bad Gateway) zurück, wenn beide der folgenden Bedingungen zutreffen: Der Wert von status ist 204 (No Content) Die Antwort enthält einen Wert für body Der Grund hierfür ist, dass Lambda@Edge eine optionale Einschränkung aus RFC 2616 umsetzt, die besagt, dass eine HTTP 204 -Antwort keinen Nachrichtentext zu enthalten braucht. Beschränkungen für die Größe der generierten Antwort Die maximale Größe einer durch eine Lambda-Funktion generierten Antwort hängt von dem Ereignis ab, das die Funktion ausgelöst hat: Viewer-Anfrage-Ereignisse – 40 KB Ursprungsanfrageereignisse – 1 MB Wenn die Antwort größer als die zulässige Größe ist, wird ein HTTP 502-Statuscode (Bad Gateway) an den Betrachter CloudFront zurückgegeben. Pflichtfelder Das Feld status ist ein Pflichtfeld. Alle anderen Felder sind optional. Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern Wenn eine HTTP-Antwort vom Ursprungsserver CloudFront empfangen wird und ein Origin-Response-Trigger mit dem Cache-Verhalten verknüpft ist, können Sie die HTTP-Antwort so ändern, dass sie überschreibt, was vom Ursprung zurückgegeben wurde. Einige häufige Szenarien für die Aktualisierung von HTTP-Antworten sind die folgenden: Ändern des Status, um einen HTTP 200-Statuscode festzulegen, und Erstellen statischer Body-Inhalte für die Rückgabe an den Viewer, wenn ein Ursprung einen Fehlerstatuscode (4xx oder 5xx) zurückgibt. Einen Beispiel-Code finden Sie unter Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 200 aktualisieren . Ändern des Status, um einen HTTP 301- oder HTTP 302-Statuscode festzulegen, um den Benutzer auf eine andere Website umzuleiten, wenn ein Ursprung einen Fehlerstatuscode zurückgibt (4xx oder 5xx). Einen Beispiel-Code finden Sie unter Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 302 aktualisieren . Anmerkung Die Funktion muss einen Statuswert zwischen 200 und 599 (einschließlich) zurückgeben, andernfalls CloudFront gibt sie einen Fehler an den Viewer zurück. Sie können auch die HTTP-Antworten in Viewer- und Ursprungsanfrageereignissen ersetzen. Weitere Informationen finden Sie unter Generieren von HTTP-Antworten in Anforderungsauslösern . Wenn Sie mit der HTTP-Antwort arbeiten, stellt Lambda@Edge den Textkörper, der vom Ursprungsserver zurückgegeben wird, nicht für den Ursprungsantwortauslöser bereit. Sie können einen statischen Inhaltstext erzeugen, indem Sie ihn auf den gewünschten Wert setzen, oder den Text innerhalb der Funktion entfernen, indem Sie den Wert auf leer setzen. Wenn Sie das Textkörperfeld in Ihrer Funktion nicht aktualisieren, wird der ursprüngliche Textkörper, der vom Ursprungsserver zurückgegeben wird, an den Viewer zurückgegeben. Zugriff auf den Anforderungstext über die Option „Text einschließen“ Sie können jetzt auswählen, ob Lambda@Edge den Textkörper in einer Anforderung für eine nicht schreibgeschützte HTTP-Methode (POST, PUT, DELETE etc.) weitergeben soll, sodass Sie in Ihrer Lambda-Funktion darauf zugreifen können. Sie können den Lesezugriff wählen oder angeben, dass Sie den Textkörper ersetzen möchten. Um diese Option zu aktivieren, wählen Sie Include Body (Body einbeziehen) aus, wenn Sie einen CloudFront -Auslöser für Ihre für ein Betrachteranforderungs- oder Ursprungsanforderungsereignis vorgesehene Funktion erstellen. Weitere Informationen finden Sie unter Hinzufügen von Auslösern für eine Lambda@Edge-Funktion . Mehr zur Nutzung von Include Body (Textkörper einbeziehen) mit Ihrer Funktion finden Sie unter Lambda@Edge-Ereignisstruktur . Sie können dieses Feature in den folgenden Szenarien nutzen: Verarbeitung von Webformularen (z. B. "Kontakt"-Formulare) ohne Rückgabe von Kundeneingabedaten an den Ursprungs-Server Erfassen von Web-Beacon-Daten, die von Viewer-Browsern gesendet werden, und Verarbeiten am Edge Einen Beispiel-Code finden Sie unter Beispielfunktionen für Lambda@Edge . Anmerkung Wenn der Anforderungs-Body groß ist, wird er von Lambda@Edge abgeschnitten. Ausführliche Informationen zur maximalen Größe und Kürzung finden Sie unter Einschränkungen für Anforderungstext mit der Option „Text einschließen“ . JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert. Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers. Dokumentkonventionen Ereignisstruktur Beispielfunktionen Hat Ihnen diese Seite geholfen? – Ja Vielen Dank, dass Sie uns mitgeteilt haben, dass wir gute Arbeit geleistet haben! Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, was wir richtig gemacht haben, damit wir noch besser werden? Hat Ihnen diese Seite geholfen? – Nein Vielen Dank, dass Sie uns mitgeteilt haben, dass diese Seite überarbeitet werden muss. Es tut uns Leid, dass wir Ihnen nicht weiterhelfen konnten. Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, wie wir die Dokumentation verbessern können? | 2026-01-13T09:30:34 |
https://support.microsoft.com/et-ee/microsoft-edge/brauseriajaloo-vaatamine-ja-kustutamine-microsoft-edge-is-00cf7943-a9e1-975a-a33d-ac10ce454ca4 | Brauseriajaloo vaatamine ja kustutamine Microsoft Edge’is - Microsofti tugiteenus Seotud teemad × Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Põhisisu juurde Microsoft Tugi Tugi Tugi Avaleht Microsoft 365 Office Tooted Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows rohkem… Seadmed Surface Arvuti tarvikud Xbox Arvutimängud HoloLens Surface Hub Riistvara garantiid Edge’i teemad Impordi lemmikud InPrivate-sirvimine Laienduste lisamine Ressursid Kogukonnafoorumid Microsoft 365 administraatorid Väikeettevõtete portaal Arendaja Haridus Teatage tehnilise toega seotud pettusest Tooteohutus Rohkem Osta Microsoft 365 Kogu Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Tugi Tarkvara Tarkvara Windowsi rakendused AI OneDrive Outlook Üleminek Skype'ilt Teamsile OneNote Microsoft Teams Arvutid ja seadmed Arvutid ja seadmed Accessories Meelelahutus Meelelahutus PC-mängud Äri Äri Microsofti turve Azure Dynamics 365 Microsoft 365 ettevõtteversioon Microsoft Industry Microsoft Power Platform Windows 365 Arendaja ja IT Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Visual Studio Marketplace Rewards Muud Muud Tasuta allalaadimised ja turve Kuva saidikaart Otsing Spikri otsing Tulemid puuduvad Loobu Logi sisse Logige sisse Microsofti kontoga Logige sisse või looge konto. Tere! Valige mõni muu konto. Teil on mitu kontot Valige konto, millega soovite sisse logida. Seotud teemad Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Brauseriajaloo vaatamine ja kustutamine Microsoft Edge’is Rakenduskoht Microsoft Edge Windows 11 Windows 10 Saate vaadata ja kustutada oma Microsoft Edge sirvimisajalugu, mis on talletatud ühes seadmes, kõigis sünkroonitud seadmetes ja pilves. Võite igal ajal sirvimisajaloo kustutada. Seadmesse salvestatud sirvimisandmete kustutamine Microsoft Edge sirvimisandmete kustutamiseks otsustage esmalt, kas soovite kustutada andmed ainult parajasti kasutatavas seadmes või kõigis sünkroonitud seadmetes. Sirvimisandmete kustutamiseks ainult seadmest, mida parajasti kasutate, veenduge, et sünkroonimine oleks välja lülitatud. Kui soovite kustutada sirvimisandmed kõigis sünkroonitud seadmetes, veenduge, et olete sisse logitud ja sünkroonimine on sisse lülitatud. Sünkroonitud üksused kustutatakse kõigis sünkroonitud seadmetes. Sünkroonimise väljalülitamiseks tehke järgmist. Valige Sätted ja muud . Avage Jaotis Sätted > Profiilid > Sünkroonimine ja valige Lülita sünkroonimine välja . Sirvimisandmete kustutamiseks Microsoft Edge tehke järgmist. Valige Sätted ja muud > Sätted > Privaatsus, otsing ja teenused . Valige Sirvimisandmete kustutamine ja seejärel valige suvand Kustuta sirvimisandmete kustutamine kohe kõrvalt Valige kustutatav sisu. Valige jaotises Ajavahemik rippmenüüst ajavahemik. Valige kustutatavate sirvimisandmete tüübid (kirjeldused leiate allolevast tabelist ). Näiteks võite soovida eemaldada sirvimisajaloo ja küpsised, kuid säilitada paroolid ja vormitäite andmed. Valige suvand Tühjenda kohe . Kustutage pilves talletatavad sirvimisandmed (kui olete sisse lülitanud sünkroonimise või isikupärastamise) Microsofti pilvteenusesse salvestatud andmete haldamiseks ja kustutamiseks vaadake privaatsussätete ja -teabe armatuurlauda . Privaatsussätete armatuurlaual saate vaadata või kustutada oma andmeid. Privaatsuse armatuurlaualt kustutatud andmeid ei kustutada teie seadmest. Lisateavet selle kohta, kuidas lõpetada andmete jagamine Microsoftiga, leiate teemast Microsoft Edge, sirvimisandmed ja privaatsus . Sirvimisandmed, mille saate kustutada Microsoft Edge Teabetüübid Kustutatav teave Salvestuskoht Sirvimisajalugu Külastatud saitide URL-id ja iga külastuse kuupäev ja kellaaeg. Seadmes (või kui sünkroonimine on sisse lülitatud, siis kõigis sünkroonitud seadmetes) Allalaadimisajalugu Veebist alla laaditud failide loend. Sellega kustutatakse ainult loend, mitte reaalselt alla laaditud failid. Seadmes Küpsised ja muud saidiandmed Teave ja andmed, mida veebisaidid teie eelistuste meeldejätmiseks teie seadmesse salvestavad (nt sisselogimisteave, teie asukoht või meediumilitsentsid). Seadmes Vahemälus olevad pildid ja failid Lehtede, piltide ja muu teie seadmesse salvestatud meediumisisu koopiad. Brauser kasutab neid koopiaid, et laadida nende saitide sisu järgmisel kasutuskorral kiiremini. Seadmes Paroolid Salvestatud saidiparoolid. Seadmes (või kui sünkroonimine on sisse lülitatud, siis kõigis sünkroonitud seadmetes) Automaattäite vormiandmed (sh vormid ja kaardid) Vormidesse sisestatud teave (nt meili- või postiaadress või krediitkaardiandmed). Seadmes (või kui sünkroonimine on sisse lülitatud, siis kõigis sünkroonitud seadmetes) Saidi õigused Avage jaotis Sätted ja muud > Sätted > Privaatsus, otsing ja teenused > Saidiõigused , et kuvada iga veebisaidi loend (sh asukoht, küpsised, hüpikud ja meediumi automaatesitus). Seadmes Kõik Microsoft Edge'i eelmise versiooni andmed Kõik andmed (sh ajalugu, lemmikud, paroolid ja muud andmed) pärinevad Microsoft Edge pärandversioonist. Seadmes (või kui sünkroonimine on sisse lülitatud, siis kõigis sünkroonitud seadmetes) Media Foundationi andmed Sisaldab litsentse, serte, võtmeid ja palju muud. Andmed kustutatakse pärast Microsoft Edge brauseri taaskäivitamist. Seadmes (või kui sünkroonimine on sisse lülitatud, siis kõigis sünkroonitud seadmetes) Seotud teemad Logige sisse, et sünkroonida Microsoft Edge’i kõigis seadmetes Hüpikakende blokeerimine Microsoft Edge ’is Veebisaidi teatiste haldamine Microsoft Edge'is Microsoft Edge, sirvimisandmed ja privaatsus Abi Microsofti konto taastamise vormiga TELLIGE RSS-KANALID Kas vajate veel abi? Kas soovite rohkem valikuvariante? Tutvustus Kogukonnafoorum Kontaktteave Siin saate tutvuda tellimusega kaasnevate eelistega, sirvida koolituskursusi, õppida seadet kaitsma ja teha veel palju muud. Microsoft 365 tellimuse eelised Microsoft 365 koolitus Microsofti turbeteenus Hõlbustuskeskus Kogukonnad aitavad teil küsimusi esitada ja neile vastuseid saada, anda tagasisidet ja saada nõu rikkalike teadmistega asjatundjatelt. Nõu küsimine Microsofti kogukonnafoorumis Microsofti spetsialistide kogukonnafoorum Windows Insideri programmis osalejad Microsoft 365 Insideri programmis osalejad Leidke lahendused levinud probleemidele või võtke ühendust klienditeenindajaga. Võrgutugi Kas sellest teabest oli abi? Jah Ei Aitäh! Veel tagasisidet Microsoftile? Kas saaksite aidata meil teenust paremaks muuta? (Saatke Microsoftile tagasisidet, et saaksime aidata.) Kui rahul te keelekvaliteediga olete? Mis mõjutas teie hinnangut? Leidsin oma probleemile lahenduse Juhised olid selged Tekstist oli lihtne aru saada Tekstis pole žargooni Piltidest oli abi Tõlkekvaliteet Tekst ei vastanud minu ekraanipildile Valed juhised Liiga tehniline Pole piisavalt teavet Pole piisavalt pilte Tõlkekvaliteet Kas soovite anda veel tagasisidet? (Valikuline) Saada tagasiside Kui klõpsate nuppu Edasta, kasutatakse teie tagasisidet Microsofti toodete ja teenuste täiustamiseks. IT-administraator saab neid andmeid koguda. Privaatsusavaldus. Täname tagasiside eest! × Mis on uut? Copilot organisatsioonidele Copilot isiklikuks kasutuseks Microsoft 365 Windows 11 rakendused Microsoft Store Konto profiil Allalaadimiskeskus Tagastused Tellimuse jälgimine Ringlussevõtt Commercial Warranties Haridus Microsoft Education Haridusseadmed Microsoft Teams haridusasutustele Microsoft 365 Education Office Education Haridustöötajate koolitus ja arendus Pakkumised õpilastele ja vanematele Azure õpilastele Äri Microsofti turve Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamsi jaoks Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Ettevõte Töökohad Teave Microsofti kohta Privaatsus Microsoftis Investorid Jätkusuutlikkus Eesti (Eesti) Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Tarbijaseisundi privaatsus Võtke Microsoftiga ühendust Privaatsus Halda küpsiseid Kasutustingimused Kaubamärgid Reklaamide kohta EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://www.php.net/manual/es/function.session-regenerate-id.php | PHP: session_regenerate_id - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_register_shutdown » « session_name Manual de PHP Referencia de funciones Extensiones de sesiones Sesiones Funciones de sesión Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_regenerate_id (PHP 4 >= 4.3.2, PHP 5, PHP 7, PHP 8) session_regenerate_id — Reemplaza el identificador de sesión actual por uno nuevo Descripción session_regenerate_id ( bool $delete_old_session = false ): bool session_regenerate_id() reemplazará el identificador de sesión actual por uno nuevo, generado automáticamente, manteniendo los valores de sesión. Cuando la opción session.use_trans_sid está activa, la salida para visualización debe comenzar después de la llamada a la función session_regenerate_id() . De lo contrario, se utilizará el antiguo ID de sesión. Advertencia Actualmente, session_regenerate_id no maneja adecuadamente una red inestable. Por ejemplo, redes móviles y WiFi. Por lo tanto, puede encontrarse una pérdida de sesión al llamar a session_regenerate_id. No se deben destruir los antiguos datos de sesión inmediatamente, sino que se debe utilizar el timestamp de destrucción y controlar el acceso al antiguo ID de sesión. De lo contrario, el acceso simultáneo a la página puede provocar un estado inconsistente, o quizás se haya perdido la sesión, o puede provocar un acceso concurrente lado-cliente (navegador) y puede crear muchos ID de sesión innecesariamente. La eliminación inmediata de datos de sesión también desactiva la detección y prevención de ataques de secuestro de sesión. Parámetros delete_old_session Si se debe borrar el antiguo archivo de sesión asociado o no. No se debe eliminar la antigua sesión si se necesita evitar accesos concurrentes causados por la eliminación o detectar/evitar ataques de secuestro de sesión. Valores devueltos Esta función retorna true en caso de éxito o false si ocurre un error. Ejemplos Ejemplo #1 Ejemplo con session_regenerate_id() <?php // Nota: este código no funciona completamente, es un ejemplo! session_start (); // Verificar el timestamp de destrucción if (isset( $_SESSION [ 'destroyed' ]) && $_SESSION [ 'destroyed' ] < time () - 300 ) { // No debería ocurrir habitualmente. Esto podría ser una ataque // o debido a una red inestable. Elimine todo el estado de // autenticación de esta sesión de usuario. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } $old_sessionid = session_id (); // Definir el timestamp de destrucción $_SESSION [ 'destroyed' ] = time (); // session_regenerate_id () registra los antiguos datos de sesión // Simplemente llamar a session_regenerate_id() puede provocar pérdida de sesión, etc. // Ver el ejemplo siguiente. session_regenerate_id (); // La nueva sesión no necesita el timestamp de destrucción unset( $_SESSION [ 'destroyed' ]); $new_sessionid = session_id (); echo "Sesión antigua: $old_sessionid <br />" ; echo "Sesión nueva: $new_sessionid <br />" ; print_r ( $_SESSION ); ?> El módulo de sesión actual no maneja adecuadamente una red inestable. Se debe gestionar el ID de sesión para evitar la pérdida de sesión por session_regenerate_id. Ejemplo #2 Evitar la pérdida de sesión por session_regenerate_id() <?php // Nota: este código no funciona completamente, es un ejemplo! // my_session_start() y my_session_regenerate_id() evitan sesiones perdidas // por red inestable. Además, este código puede evitar la explotación de // sesión robada por atacantes. function my_session_start () { session_start (); if (isset( $_SESSION [ 'destroyed' ])) { if ( $_SESSION [ 'destroyed' ] < time ()- 300 ) { // No debería ocurrir habitualmente. Esto podría ser una // ataque o debido a una red inestable. Elimine todo el estado // de autenticación de esta sesión de usuario. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } if (isset( $_SESSION [ 'new_session_id' ])) { // No ha expirado completamente. Podría ser pérdida de cookie por red inestable. // Intente nuevamente definir la cookie de ID de sesión adecuada. // Nota: no intente redefinir el ID de sesión si // desea eliminar el estado de autenticación. session_commit (); session_id ( $_SESSION [ 'new_session_id' ]); // El nuevo ID de sesión debe existir session_start (); return; } } } function my_session_regenerate_id () { // El nuevo ID de sesión es requerido para definir el ID de sesión adecuado // cuando el ID de sesión no está definido debido a una red inestable. $new_session_id = session_create_id (); $_SESSION [ 'new_session_id' ] = $new_session_id ; // Define el timestamp de destrucción $_SESSION [ 'destroyed' ] = time (); // Escribe y cierra la sesión actual session_commit (); // Inicia la sesión con un nuevo ID session_id ( $new_session_id ); ini_set ( 'session.use_strict_mode' , 0 ); session_start (); ini_set ( 'session.use_strict_mode' , 1 ); // La nueva sesión no lo necesita unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Ver también session_id() - Lee y/o modifica el identificador de sesión actual session_create_id() - Crear un nuevo ID de sesión session_start() - Inicia una nueva sesión o reanuda una sesión existente session_destroy() - Destruye una sesión session_reset() - Restablece el array de sesión con los valores originales session_name() - Lee y/o modifica el nombre de la sesión Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 22 notes up down 42 tedivm at tedivm dot com ¶ 9 years ago I wrote the current top voted comment on this and wanted to add something. The existing code from my previous comment generates it's nonces in an insecure way- <?php $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); ?> Since "microtime" is predictable it makes brute forcing the nonce much easier. A better option would be something that utilizes randomness, such as- <?php bin2hex ( openssl_random_pseudo_bytes ( 32 )) ?> up down 42 tedivm at tedivm dot com ¶ 17 years ago I wrote the following code for a project I'm working on- it attempts to resolve the regenerate issue, as well as deal with a couple of other session related things. I tried to make it a little more generic and usable (for instance, in the full version it throws different types of exceptions for the different types of session issues), so hopefully someone might find it useful. <?php function regenerateSession ( $reload = false ) { // This token is used by forms to prevent cross site forgery attempts if(!isset( $_SESSION [ 'nonce' ]) || $reload ) $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); if(!isset( $_SESSION [ 'IPaddress' ]) || $reload ) $_SESSION [ 'IPaddress' ] = $_SERVER [ 'REMOTE_ADDR' ]; if(!isset( $_SESSION [ 'userAgent' ]) || $reload ) $_SESSION [ 'userAgent' ] = $_SERVER [ 'HTTP_USER_AGENT' ]; //$_SESSION['user_id'] = $this->user->getId(); // Set current session to expire in 1 minute $_SESSION [ 'OBSOLETE' ] = true ; $_SESSION [ 'EXPIRES' ] = time () + 60 ; // Create new session without destroying the old one session_regenerate_id ( false ); // Grab current session ID and close both sessions to allow other scripts to use them $newSession = session_id (); session_write_close (); // Set session ID to the new one, and start it back up again session_id ( $newSession ); session_start (); // Don't want this one to expire unset( $_SESSION [ 'OBSOLETE' ]); unset( $_SESSION [ 'EXPIRES' ]); } function checkSession () { try{ if( $_SESSION [ 'OBSOLETE' ] && ( $_SESSION [ 'EXPIRES' ] < time ())) throw new Exception ( 'Attempt to use expired session.' ); if(! is_numeric ( $_SESSION [ 'user_id' ])) throw new Exception ( 'No session started.' ); if( $_SESSION [ 'IPaddress' ] != $_SERVER [ 'REMOTE_ADDR' ]) throw new Exception ( 'IP Address mixmatch (possible session hijacking attempt).' ); if( $_SESSION [ 'userAgent' ] != $_SERVER [ 'HTTP_USER_AGENT' ]) throw new Exception ( 'Useragent mixmatch (possible session hijacking attempt).' ); if(! $this -> loadUser ( $_SESSION [ 'user_id' ])) throw new Exception ( 'Attempted to log in user that does not exist with ID: ' . $_SESSION [ 'user_id' ]); if(! $_SESSION [ 'OBSOLETE' ] && mt_rand ( 1 , 100 ) == 1 ) { $this -> regenerateSession (); } return true ; }catch( Exception $e ){ return false ; } } ?> up down 3 Rumour ¶ 2 years ago The code example provided of my_session_regenerate_id() DOES NOT work and DESTROYS all session variables. Plus the second ini_set gives an error. The code for regenerating (only that part, the rest seems fine) should simply be this: <?php function my_session_regenerate_id () { $new_session_id = session_create_id (); // backup session variables $keepSession = $_SESSION ; // add info for users with bad connection not receiving the new session id $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit () ; // Start session with new session ID ini_set ( 'session.use_strict_mode' , 0 ); session_id ( $new_session_id ); session_start (); $_SESSION = $keepSession ; } ?> up down 13 ei dot rik dot ops dot tad at gmail dot com ¶ 9 years ago In PHP 5.6 (and probably older versions), session_regenerate_id(true) do not trigger a read() call to the session handler for the new session id. In PHP 7, read() is triggered during session_regenerate_id(true). Nice to know when working with custom session handlers. up down 8 gr at gr5 dot org ¶ 14 years ago If you are trying to maintain 2 active sessions don't use session_regenerate_id(). Especially if the first session is closed and it's time to open the second. Because the session id is cached you also have to explicitly set it the second time. <?php session_name ( 'PHPSESSID' ); // redundant - here for clarity session_start (); // ...do stuff session_write_close (); // now switch to session 2... session_name ( 'PHPSESSID_2' ); if (isset( $_COOKIE [ 'phpsessid_2' ])) session_id ( $_COOKIE [ 'phpsessid_2' ]); // not doing this will simply reopen the first session again else session_id ( sha1 ( mt_rand ()); // dont use session_regenerate_id() here. Not creating a new id will create two cookies with same session id and same session variables session_start (); // ... do stuff with session 2 session_write_close (); ?> up down 13 ross at kndr dot org ¶ 21 years ago In a previous note, php at 5mm de describes how to prevent session hijacking by ensuring that the session id provided matches the HTTP_USER_AGENT and REMOTE_ADDR fields that were present when the session id was first issued. It should be noted that HTTP_USER_AGENT is supplied by the client, and so can be easily modified by a malicious user. Also, the client IP addresses can be spoofed, although that's a bit more difficult. Care should be taken when relying on the session for authentication. up down 4 babel at nosqamplease sympatico ca ¶ 21 years ago To add to php at 5mm de's comments: If the session is held over https, it's even better to save the client's cert or ssl session id instead of the hostname or ip, as it's proxy-transparent and more secure. up down 10 spmtrap at yahoo dot com ¶ 13 years ago `session_regenerate_id` sends a new cookie but doesn't overwrite the value stored in `$_COOKIE`. After calling `session_destroy`, the open session ID is discarded, so simply restarting the session with `session_start` (as done in Ben Johnson's code) will re-open the original, though now empty, session for the current request (subsequent requests will use the new session ID). Instead of `session_destroy`+`session_start`, use the `$delete_old_session` parameter to `session_regenerate_id` to delete the previous session data. <?php session_start (); /* Create a new session, deleting the previous session data. */ session_regenerate_id ( TRUE ); /* erase data carried over from previous session */ $_SESSION =array(); ?> To start a new session and leave the old untouched, simply leave out the argument to `session_regenerate_id`. up down 6 php at cny dot de ¶ 21 years ago Also note that REMOTE_ADDR may change on every request if the user comes through a proxy farm. Most AOL-users do. up down 2 k-gun !! mail ¶ 9 years ago Document example is wrong with usage of "session.use_strict_mode" according to RFC (says: "warning error for session_id() when use_strice_mode=1" on https://wiki.php.net/rfc/strict_sessions ). So, this directive affects "session_id()" not "session_start()". So usage must be like this; <?php // first set ini ini_set ( 'session.use_strict_mode' , '0' ); // and session_id ( $sid ); // then // maybe run this: ini_restore('session.use_strict_mode'); // then go on... ?> Refs (ctrl+f & use_strict_mode); https://wiki.php.net/rfc/strict_sessions https://wiki.php.net/rfc/session-create-id http://php.net/manual/en/function.session-id.php#119997 up down 3 madsen at sjovedyr.dk ¶ 22 years ago I had problems with a proxy changing a visitors session_id-cookie, so he'd get a LOT of errors when visiting my site. I handled the bogus session-id's like this. (Note: It only works in versions > 4.3.2.) <?php // Start a session and suppress error-messages. @ session_start (); // Catch bogus session-id's. if (! preg_match ( "/^[0-9a-z]*$/i" , session_id ())) { // Output a warning about the messed up session-id. $error -> handleError ( "WARN" , "Your session id is messed up, you might not be able to use some features on this site." ); // Generate a fresh session-id. session_regenerate_id (); } // Site contents. ?> Hope someone can use it. up down 1 Nicolas dot Chachereau at Infomaniak dot ch ¶ 20 years ago Session_destroy() does not only destroy the data associated with the current session_id (i.e. the file if you use the default session save handler), but also the session itself: if you call session_destroy() and then session_regenerate_id(), it will return false, and session_id() won't return anything. In order to manipulate a session after destroying it, you need to restart it. So in fact, the code mentionned by chris won't work. If you want to destroy the file associated with the old session_id, try the following: <?php session_start (); $old_sessid = session_id (); session_regenerate_id (); $new_sessid = session_id (); session_id ( $old_sessid ); session_destroy (); //If you don't copy the $_SESSION array, you won't be able to use the data associated with the old session id. $old_session = $_SESSION ; session_id ( $new_sessid ); session_start (); $_SESSION = $old_session ; //... ?> Note: this technique will send 3 Set-Cookie headers (one on each session_start() and one on session_regenerate_id()). I don't think this is a problem, but if it appears to be one, you could either leave it alone and wait for the garbage collector to catch the file associated with the old session, or try to delete the file with unlink(). up down 1 soapergem at gmail dot com ¶ 17 years ago This can be a very dangerous function if you're not careful about how you handle things, because even though it generates a whole new set of session data, it keeps the old data "open" until the script terminates, locking out any other scripts trying to run concurrently with the old session id. Recently I came across a situation where I wanted to explicitly pass in a session ID, copy the data from that session into a *new* session, and then continue operating under that new session, thereby allowing other scripts to use the old one concurrently. But I quickly found that these "other scripts" would not execute until the first script finished--even though it had already started a new session--because it kept the old session open. So if you're trying to copy over session data to a new session to free up the old session for continued, concurrent use, here's some code to ensure nobody's feet get stepped on: <?php // get session id of an existing session $sid = $_GET [ 'sid' ]; // start the old session to retrieve $_SESSION data session_id ( $sid ); session_start (); // start a new session; this copies the $_SESSION data over session_regenerate_id (); // hang on to the new session id $sid = session_id (); // close the old and new sessions session_write_close (); // re-open the new session session_id ( $sid ); session_start (); /* main code here */ ?> This could probably be encapsulated into a function with one parameter as well to save space if it was a repeated thing. up down 0 primenetworkzx at gmail dot com ¶ 17 years ago If you are storing your session data in a database you have to manually update the session_id in the database. The session_set_save_handler() will not do it for you. function UpdateSessID() { $old_sess_id = session_id(); session_regenerate_id(false); $new_sess_id = session_id(); $query = "UPDATE `session_table` SET `session_id` = '$new_sess_id' WHERE session_id = '$old_sess_id'"; mysql_query($query); } Be sure to set session_regenerate_id() to FALSE since it's not really necessary to delete the whole record from MySQL and add it again. That's unnecessary overhead. Only changing the id matters. up down 0 dyer85 at gmail dot com ¶ 20 years ago There could be a potential problem with elger at NOSPAM dot yellowbee dot nl's a few posts below. In the code, was used the REQUEST_URI server variable, which, in some cases might already contain the query string. Therefore, always apending '?whatever=foo' would occasionally cause the script to malfunction. I suggest using PHP_SELF, which will not contain the query string after the file. up down -2 mikebranttx at gmail dot com ¶ 8 years ago Note that in current PHP 7.2 nightly builds example #2 above will not work as shown. You will get following error upon trying to turn strict mode back on after session_start(): "ini_set(): A session is active. You cannot change the session module's ini settings at this time" I suppose this means that for any session where you perform session ID regeneration or session ID forwarding (from a session for which a recent session ID regeneration was performed to the new session ID). That you will just have to live with strict mode being disabled for the remainder of that active session. I don't know that this is really a security concern so long as you are following a single-session per request design (i.e. you are not working with multiple concurrent sessions). up down -2 chris at knowledge dot tee-vee ¶ 20 years ago licp - no, session_regenerate_id() does not destroy any saved session data. elger, I prefer the following order [code] // populate $_SESSION with any previously saved session data for the current session_id session_start(); ... // delete any saved data associated with current session_id, $_SESSION is not changed session_destroy(); // change session_id, $_SESSION not altered session_regenerate_id(); ... // save any $_SESSION data under the current session_id session_close(); [/code] up down -1 antomsa at hotmail dot it ¶ 4 years ago <?php function my_session_regenerate_id () { ... session_start (); ... unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Within my_session_regenerate_id(), unset($_SESSION['destroyed']) and unset($_SESSION['new_session_id']) are useless because session_start() will open an empty session. They would be needed if built-in session_regenerate_id() was called. up down -4 kgm_india at yahoo dot co dot in ¶ 12 years ago as far as I have understood reading this online notes, session_name() is the name which is identified as session a through the cookies or http links. session_id is like a transaction within a session_name() and one session_name may have many session_id each session_id has the corresponding data stored. session_id are used in read and write callback under a session_name whatever it is, first call the session_name(), then call session_id () and then call start_session() start_session will open the session_name, then check the session_id called before and use it in the read or write call back for storing or retrieving data calling start_session() without session_name or session_id will use the default session_name and the default session_id in that order I hope if the order is followed there should not be any problems. do not call session_name or session_id after start_session(), if you are specific on using them. thank you for others note. up down -5 raido dot aasoja at gmail dot com ¶ 15 years ago A note on lost sessions and trying to fix it with session_regenerate_id: Make sure that you're not trying to push SimpleXML object to the session. It just won't go without first converting it to array. :) up down -3 sopel ¶ 20 years ago for php 5.1> user probably worth visiting is http://ilia.ws/archives/47-session_regenerate_id-Improvement.html up down -4 Alamin ¶ 7 years ago In the second example provided by php.net, should it call my_session_start inside the session regenerate method instead of directly calling session_start? I think it is an error. ＋ add a note Funciones de sesión session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://support.microsoft.com/ru-ru/microsoft-edge/%D0%B1%D1%80%D0%B0%D1%83%D0%B7%D0%B5%D1%80-microsoft-edge-%D0%B4%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D0%B1%D1%80%D0%B0%D1%83%D0%B7%D0%B5%D1%80%D0%B0-%D0%B8-%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B4%D0%B5%D0%BD%D1%86%D0%B8%D0%B0%D0%BB%D1%8C%D0%BD%D0%BE%D1%81%D1%82%D1%8C-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Браузер Microsoft Edge, данные браузера и конфиденциальность - Служба поддержки Майкрософт Перейти к основному контенту Microsoft Поддержка Поддержка Поддержка Главная Microsoft 365 Office Продукты Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows еще... Устройства Surface Периферийные устройства для компьютера Xbox Компьютерные игры HoloLens Surface Hub Гарантии на оборудование Учетная запись и выставление счетов Учетная запись Microsoft Store и выставление счетов Ресурсы Новые возможности Форумы сообщества Администраторы Microsoft 365 Портал для малого бизнеса Для разработчиков Образование Сообщить о мошенничестве с поддержкой Безопасность продуктов Еще Покупка Microsoft 365 Продукты Майкрософт Global Microsoft 365 Teams Windows Xbox Поддержка ПО ПО Приложения для Windows ИИ OneDrive Outlook Переход от Skype в Teams OneNote Microsoft Teams Компьютеры и устройства Компьютеры и устройства Купите Xbox Аксессуары Развлечения Развлечения Xbox Game Pass Ultimate Xbox и игры Компьютерные игры Для бизнеса Для бизнеса Microsoft Security Azure Dynamics 365 Microsoft 365 для бизнеса Microsoft для промышленности Microsoft Power Platform Windows 365 Для разработчиков и ИТ Для разработчиков и ИТ Программа Майкрософт для разработчиков Microsoft Learn Поддержка ИИ-приложений на Marketplace Сообщество Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards Другое Другое Бесплатная загрузка и средства безопасности Образование Лицензирование Посмотреть карту сайта Поиск Поиск справки Нет результатов Отмена Войти Войдите с помощью учетной записи Майкрософт Войдите или создайте учетную запись. Здравствуйте, Выберите другую учетную запись. У вас несколько учетных записей Выберите учетную запись, с помощью которой нужно войти. Браузер Microsoft Edge, данные браузера и конфиденциальность Применяется к Privacy Microsoft Edge Windows 10 Windows 11 Microsoft Edge помогает просматривать, искать, совершать покупки в Интернете и многое другое. Как и все современные браузеры Microsoft Edge позволяет собирать и сохранять на устройстве определенные данные, например файлы cookie, а также отправлять в корпорацию Майкрософт сведения, такие как журнал браузера, чтобы улучшить, ускорить и персонализировать ваше взаимодействие с браузером. Всякий раз, когда мы собираем данные, мы хотим убедиться, что это правильный выбор для вас. Некоторые пользователи опасаются предоставлять доступ к данным журнала браузера. Именно поэтому мы сообщаем, какие данные хранятся на вашем устройстве или собираются нами. Вы можете сами выбрать, какие ваши данные будут собираться. Для получения дополнительных сведений о конфиденциальности в Microsoft Edge рекомендуем прочитать наше заявление о конфиденциальности . Какие данные собираются и хранятся и почему Корпорация Майкрософт использует диагностические данные для улучшения своих продуктов и служб. Мы используем эти данные, чтобы лучше понять, как работают наши продукты и какие улучшения необходимо внести. Microsoft Edge собирает набор обязательных диагностических данных, чтобы обеспечить ожидаемую безопасность, актуальность и производительность Microsoft Edge. Корпорация Майкрософт привержена принципу минимизации сбора информации и реализует этот принцип на практике. Мы стремимся собирать только нужную информацию и хранить ее только до тех пор, пока она необходима для предоставления службы или для анализа. Кроме того, вы можете управлять тем, будет ли корпорации Майкрософт предоставляться доступ к дополнительным диагностическим данным, связанным с вашим устройством, для решения проблем с продуктами и улучшения качества продуктов и служб Майкрософт. Когда вы используете функции и службы в Microsoft Edge, диагностические сведения об использовании этих функций отправляются в корпорацию Майкрософт. Microsoft Edge сохраняет на вашем устройстве журнал браузера, который содержит сведения о посещаемых вами сайтах. В зависимости от заданных вами параметров журнал браузера может отправляться в корпорацию Майкрософт. Это помогает нам находить и устранять неполадки, а также улучшать наши продукты и службы для всех пользователей. Вы можете управлять сбором необязательных диагностических данных в браузере, выбрав Параметры и другие > Параметры > Конфиденциальность, поиск и службы > Конфиденциальность , а также включите или отключите отправку необязательных диагностических данных для улучшения продуктов Майкрософт . К этим данным относятся сведения, связанные с тестированием новых возможностей. Чтобы сохранить изменения этого параметра, перезапустите Microsoft Edge. При включении этого параметра корпорация Майкрософт также будет получать необязательные диагностические данные из других приложений, использующих Microsoft Edge, таких как приложения для потоковой передачи видео, в котором размещена веб-платформа Microsoft Edge для потоковой передачи видео. Веб-платформа Microsoft Edge будет отправлять в корпорацию Майкрософт информацию об использовании веб-платформы и сайтов, которые вы посещаете в таких приложениях. Сбор этих данных определяется параметрами необязательных диагностических данных в настройках конфиденциальности, поиска и служб в Microsoft Edge. В Windows 10 предоставление этой информации определяется параметром диагностических данных Windows. Чтобы изменить параметр диагностических данных, выберите Пуск > Параметры > конфиденциальность > диагностика & отзыв . С 6 марта 2024 г. диагностические данные Microsoft Edge собираются отдельно от диагностических данных Windows на устройствах Windows 10 (версии 22H2 и более поздних версий) и Windows 11 (версии 23H2 и более поздних) в Европейской экономической зоне. Для этих версий Windows и на всех других платформах вы можете изменить параметры в Microsoft Edge, выбрав Параметры и другие > Параметры > конфиденциальность, поиск и службы . В некоторых случаях ваши настройки диагностических данных могут управляться вашей организацией. Когда вы ищете что-то, Microsoft Edge может дать рекомендации о том, что вы ищете. Чтобы включить эту функцию, выберите Параметры и другие > Параметры > Конфиденциальность, поиск и службы , > Поиск и подключенные интерфейсы > адресной строке и поиске > Варианты и фильтры поиска , а затем включите параметр Показывать варианты поиска и сайта с помощью моих введенных символов . Когда вы начинаете вводить текст, сведения, введенные в адресной строке отправляются в службу поиска, выбранную вами по умолчанию, для мгновенного предоставления вам результатов поиска и рекомендаций по веб-сайтам При использовании режима просмотра InPrivate или гостевого режима Microsoft Edge собирает некоторые сведения о том, как вы используете браузер в зависимости от параметра диагностических данных Windows или параметров конфиденциальности Microsoft Edge, но автоматические предложения отключаются, а сведения о веб-сайтах, которые вы посещаете, не собираются. Microsoft Edge удаляет ваш журнал браузера, файлы cookie и данные сайтов, а также пароли, адреса и данные форм при закрытии всех окон режима InPrivate. Вы можете запустить новый сеанс в режиме InPrivate, перейдя в раздел Параметры и прочее на компьютере или Вкладки на мобильном устройстве. В Microsoft Edge также есть функции, помогающие защитить вас и ваше содержимое в Интернете. SmartScreen Защитника Windows автоматически блокирует веб-сайты и скачивание содержимого, которые, как сообщается, являются вредоносными. Фильтр SmartScreen в Защитнике Windows проверяет адрес посещаемой веб-страницы по хранящемуся на вашем устройстве списку адресов веб-сайтов, известных корпорации Майкрософт как подлинные. Адреса, отсутствующие в списке вашего устройства, а также адреса скачиваемых файлов отправляются в Microsoft и сверяются с часто обновляемым списком веб-страниц и скачиваний, которые Microsoft считает опасными или подозрительными. Чтобы ускорить выполнение утомительных задач, таких как заполнение форм и ввод паролей, Microsoft Edge может сохранять введенные данные. Если вы решите использовать эти функции, Microsoft Edge сохранит информацию на вашем устройстве. Если вы включили синхронизацию для заполнения форм, например адресов или паролей, эти сведения будут отправлены в облако Майкрософт и сохранены с учетной записью Майкрософт для синхронизации во всех версиях Microsoft Edge для входа. Эти данные можно управлять с помощью параметров и других > параметров > профилей > синхронизации . Чтобы интегрировать возможности браузера с другими действиями, которые вы выполняете на устройстве, Microsoft Edge предоставляет общий доступ к журналу браузера с Microsoft Windows через индексатор. Эти сведения хранятся локально на устройстве. Он включает URL-адреса, категорию, в которой URL-адрес может быть релевантным, например "наиболее посещенный", "недавно посещенный" или "недавно закрытый", а также относительную частоту или повторность в каждой категории. Веб-сайты, которые вы посещаете в режиме InPrivate, не будут предоставляться. Затем эти сведения будут доступны другим приложениям на устройстве, например меню "Пуск" или панели задач. Вы можете управлять этой функцией, выбрав Параметры и другие > Параметры > Профили , а также включите или отключите общий доступ к данным браузера с другими функциями Windows. Если этот параметр отключен, все ранее общие данные будут удалены. Для защиты от копирования музыкального и видеоконтента некоторые веб-сайты, выполняющие потоковую передачу содержимого, хранят на вашем устройстве сведения об управлении цифровыми правами (DRM), включая уникальный идентификатор и полученные лицензии на мультимедиа. При переходе на любой из этих веб-сайтов он получает данные о DRM, чтобы определить, что у вас есть разрешение на использование содержимого. Microsoft Edge также сохраняет файлы cookie — файлы небольшого размера, которые размещаются на устройстве при работе в Интернете. Многие веб-сайты используют файлы cookie для хранения информации о ваших предпочтениях и заданных параметрах, например сведения о товарах в корзине интернет-магазинов, чтобы вам не приходилось добавлять их повторно в корзину при каждом посещении интерне-магазина. Некоторые веб-сайты также используют файлы cookie для сбора информации о ваших действиях в Интернете для показа рекламы на основе интересов. Microsoft Edge предоставляет возможность удалить файлы cookie и блокировать сохранение файлов cookie с веб-сайтов в будущем. Microsoft Edge отправляет веб-сайтам запросы "Не отслеживать", если включен параметр Отправлять запросы "Не отслеживать" . Этот параметр доступен в разделе Параметры и другие > Параметры > конфиденциальность, поиск и службы , > конфиденциальность > отправлять запросы "Не отслеживать". Однако веб-сайты могут продолжать отслеживать ваши действия, даже если отправлен запрос "Не отслеживать". Удаление данных, собранных или сохраненных в Microsoft Edge Чтобы удалить сохраненные на устройстве сведений о ваших действиях в Интернете, таких как пароли и файлы cookie В Microsoft Edge выберите Параметры и другие > Параметры > Конфиденциальность, поиск и службы > Очистить данные браузера . Выберите Выбрать, что нужно очистить рядом с пунктом Очистить данные браузера сейчас. В разделе Диапазон времени выберите временной промежуток. Выберите поле проверка рядом с каждым типом данных, который вы хотите очистить, а затем нажмите кнопку Очистить. При желании можно выбрать Выбрать, что следует очищать при каждом закрытии браузера , и выбрать типы данных, которые следует очистить. Подробнее о том, что удаляется для каждого элемента журнала браузера . Чтобы очистить журнал браузера, собираемый корпорацией Майкрософт Для просмотра журнала браузера, связанного с вашей учетной записью, войдите в свою учетную запись на странице account.microsoft.com . Кроме того, у вас также есть возможность очистить данные браузера, собранные Майкрософт, с помощью Панели мониторинга конфиденциальности (Майкрософт) . Чтобы удалить журнал браузера и другие диагностические данные, связанные с Windows 10 устройством, выберите Запустить > Параметры > Конфиденциальность > диагностика & отзыве , а затем в разделе Удалить диагностические данные выберите Удалить . Чтобы очистить журнал браузера, к которым предоставлен доступ другим функциям Майкрософт на локальном устройстве, выполните следующие действия: В Microsoft Edge выберите Параметры и другие > Параметры > Профили . Выберите Общий доступ к данным браузера с другими функциями Windows. Отключите этот параметр. Управление параметрами конфиденциальности в Microsoft Edge Чтобы просмотреть и настроить параметры конфиденциальности, выберите Параметры и другие > Параметры > Конфиденциальность, поиск и службы . конфиденциальность > . Чтобы узнать больше о конфиденциальности в Microsoft Edge, прочитайте Официальный документ о конфиденциальности Microsoft Edge . ПОДПИСКА НА RSS-КАНАЛЫ Нужна дополнительная помощь? Нужны дополнительные параметры? Обнаружение Сообщества Свяжитесь с нами Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д. Преимущества подписки на Microsoft 365 Обучение работе с Microsoft 365 Microsoft Security Центр специальных возможностей В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей. Задайте вопрос сообществу Microsoft Сообщество Microsoft Tech Community Участники программы предварительной оценки Windows Участники программы предварительной оценки Microsoft 365 Найдите решения распространенных проблем или получите помощь от агента поддержки. Поддержка в сети Были ли сведения полезными? Да Нет Спасибо! Хотите отправить другие отзывы для Майкрософт? Что мы могли бы сделать лучше? (Отправьте отзыв в корпорацию Майкрософт, чтобы мы могли помочь.) Насколько вы удовлетворены качеством перевода? Что повлияло на вашу оценку? Моя проблема решена Понятные инструкции Понятные сведения Без профессиональной лексики Полезные изображения Качество перевода Не соответствует интерфейсу Неверные инструкции Слишком техническая информация Недостаточно информации Недостаточно изображений Качество перевода Добавите что-нибудь? Это необязательно Отправить отзыв После нажатия кнопки "Отправить" ваш отзыв будет использован для улучшения продуктов и служб Майкрософт. Эти данные будут доступны для сбора ИТ-администратору. Заявление о конфиденциальности. Спасибо за ваш отзыв! × Что нового? Copilot для организаций Microsoft 365 Узнайте больше о продуктах Microsoft Приложения Windows 11 Microsoft Store Профиль учетной записи Центр загрузки Поддержка Microsoft Store Возврат товаров Отслеживание заказа Для образования Microsoft для образования Устройства для образования Microsoft Teams для образования Microsoft 365 для образования Office для образования Подготовка и профессиональное развитие преподавателей Специальные предложения для учащихся и родителей Azure для учащихся Для бизнеса Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Разработчики и ИТ Программа Майкрософт для разработчиков Microsoft Learn Поддержка ИИ-приложений на Marketplace Сообщество Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Компания Вакансии О корпорации Майкрософт Новости компании Политика конфиденциальности Майкрософт Инвесторы Экологическая устойчивость Русский (Россия) Значок отказа для ваших вариантов выбора параметров конфиденциальности Ваши варианты выбора параметров конфиденциальности Значок отказа для ваших вариантов выбора параметров конфиденциальности Ваши варианты выбора параметров конфиденциальности Конфиденциальность медицинских сведений потребителей Связаться с Майкрософт Конфиденциальность Управление файлами cookie Условия использования Товарные знаки Сведения о рекламе © Microsoft 2026 | 2026-01-13T09:30:34 |
https://www.iso.org/es/perspectivas/lista-filtrada-asistencia-sanitaria | ISO - Salud Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Salud Transformación digital de la asistencia sanitaria: telemedicina, protección de datos y ciberseguridad Todos tenemos en común la salud. Protegida, la salud empodera a las personas para prosperar; descuidada, puede tener consecuencias devastadoras, no solo para los individuos y sus familias, sino para comunidades enteras. Últimos artículos Ciberseguridad en la asistencia sanitaria: diagnosticar riesgos, recetar soluciones Los fundamentos de los equipos de telemedicina Monitoreo remoto de pacientes: Una guía para especialistas en asistencia sanitaria Transformación digital de la asistencia sanitaria: telemedicina, protección de datos y ciberseguridad La historia clínica electrónica explicada Guía sencilla para entender el análisis de datos sanitarios Le damos la bienvenida al mundo de la telemedicina: comprender los fundamentos Cargar más Suscríbase para recibir actualizaciones por correo electrónico ¡Regístrese para obtener más recursos y actualizaciones sobre normas sanitarias y afines! Website Suscribirse * ¡Ya casi está! Sólo le falta un paso para unirse a la lista de suscriptores de ISO. Confirme su suscripción haciendo clic en el correo electrónico que acabamos de enviarle. No estará registrado hasta que confirme su suscripción. Si no encuentra el correo electrónico, compruebe su carpeta de correo no deseado y/o la pestaña de promociones (si utiliza Gmail). * Boletín de noticias en inglés Para saber cómo se utilizarán sus datos, consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Cómo se utilizarán sus datos Consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Perspectivas y actualidad Perspectivas Salud Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0ODBxi9Ky_q5Zd-o4dYpnmHyfX6cU94o0TSebfXayTVSpJVZhsLNiaEOYJD4tF5NyHmlhcHvBZpujDEdp7WEIct_OsB2vtYxvgex9BobCz0QD-I7CT9qU5M2_9NMDpfEnKNwsIMtWszByH | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:34 |
https://support.microsoft.com/hu-hu/windows/cookie-k-kezel%C3%A9se-a-microsoft-edge-ben-megtekint%C3%A9s-enged%C3%A9lyez%C3%A9s-letilt%C3%A1s-t%C3%B6rl%C3%A9s-%C3%A9s-haszn%C3%A1lat-168dab11-0753-043d-7c16-ede5947fc64d | Cookie-k kezelése a Microsoft Edge-ben: Megtekintés, engedélyezés, letiltás, törlés és használat - A Microsoft ügyfélszolgálata Kapcsolódó témakörök × Windows biztonság, védettség és adatvédelem Áttekintés Biztonság, védettség és adatvédelem – áttekintés Biztonság a Windowsban Segítség kérése a Windows biztonság alkalmazással Védelem a Windows biztonság alkalmazással Mielőtt újrahasznosítja, eladja vagy elajándékozza az Xbox vagy Windows rendszerű PC-jét Kártevők eltávolítása windowsos PC-ről Windows biztonság Segítség kérése a Windows biztonság alkalmazással A Microsoft Edge böngészőben megtekintheti és törölheti a böngészési előzményeket Cookie-k törlése és kezelése Értékes tartalom biztonságos eltávolítása a Windows újratelepítésekor Elveszett windowsos eszköz megkeresése és zárolása Windows-adatvédelem A Windows-adatvédelemmel kapcsolatos segítség kérése Az alkalmazások által használt Windows adatvédelmi beállítások Adatok megtekintése az adatvédelmi irányítópulton Ugrás a tartalomtörzsre Microsoft Terméktámogatás Terméktámogatás Terméktámogatás Kezdőlap Microsoft 365 Office Termékek Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows egyebek ... Eszközök Surface PC-tartozékok Xbox PC-s játékok HoloLens Surface Hub Hardvergaranciák Fiók & számlázás Fiók Microsoft Store és számlázás Források Újdonságok Forumi zajednice Microsoft 365 rendszergazdák Kisvállalati portál Fejlesztő Oktatás Támogatási csalás bejelentése Termékbiztonság Több A Microsoft 365 megvásárlása Minden ami Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Támogatás Szoftverek Szoftverek Windows-alkalmazások Mesterséges intelligencia OneDrive Outlook Áttérés a Skype-ról a Teamsre OneNote Microsoft Teams Számítógépek és eszközök Számítógépek és eszközök Xbox vásárlása Tartozékok Szórakozás Szórakozás Xbox Game Pass Ultimate Xbox és játékok PC játékok Üzlet Üzlet Microsoft-biztonság Azure Dynamics 365 Microsoft 365 vállalatok számára Microsoft Ipar Microsoft Power Platform Windows 365 Fejlesztők és IT Fejlesztők és IT Microsoft-fejlesztő Microsoft Learn AI piactéri alkalmazások támogatása Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Egyéb Egyéb Díjmentes letöltések és biztonság Oktatás Ajándékkártyák Oldaltérkép megtekintése Keresés Segítség keresése Nincs találat Mégse Bejelentkezés Bejelentkezés Microsoft-fiókkal Jelentkezzen be, vagy hozzon létre egy fiókot. Üdvözöljük! Válasszon másik fiókot. Több fiókja van Válassza ki a bejelentkezéshez használni kívánt fiókot. Kapcsolódó témakörök Windows biztonság, védettség és adatvédelem Áttekintés Biztonság, védettség és adatvédelem – áttekintés Biztonság a Windowsban Segítség kérése a Windows biztonság alkalmazással Védelem a Windows biztonság alkalmazással Mielőtt újrahasznosítja, eladja vagy elajándékozza az Xbox vagy Windows rendszerű PC-jét Kártevők eltávolítása windowsos PC-ről Windows biztonság Segítség kérése a Windows biztonság alkalmazással A Microsoft Edge böngészőben megtekintheti és törölheti a böngészési előzményeket Cookie-k törlése és kezelése Értékes tartalom biztonságos eltávolítása a Windows újratelepítésekor Elveszett windowsos eszköz megkeresése és zárolása Windows-adatvédelem A Windows-adatvédelemmel kapcsolatos segítség kérése Az alkalmazások által használt Windows adatvédelmi beállítások Adatok megtekintése az adatvédelmi irányítópulton Cookie-k kezelése a Microsoft Edge-ben: Megtekintés, engedélyezés, letiltás, törlés és használat Hatókör Windows 10 Windows 11 Microsoft Edge A cookie-k olyan kis méretű adatok, amelyeket a felkeresett webhelyek tárolnak az eszközön. Különböző célokat szolgálnak, például a bejelentkezési hitelesítő adatok megjegyzését, a webhelybeállításokat és a felhasználói viselkedés nyomon követését. Előfordulhat azonban, hogy adatvédelmi okokból vagy a böngészési problémák megoldása érdekében törölni szeretné a cookie-kat. Ez a cikk a következő útmutatást nyújtja: Az összes cookie megtekintése Az összes cookie engedélyezése Cookie-k engedélyezése egy adott webhelyről Harmadik féltől származó cookie-k letiltása Az összes cookie blokkolása: Cookie-k letiltása egy adott webhelyről Az összes cookie törlése Cookie-k törlése adott webhelyről Cookie-k törlése a böngésző minden egyes bezárásakor Cookie-k használata az oldal előzetes betöltéséhez a gyorsabb böngészés érdekében Az összes cookie megtekintése Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, majd kattintson az Összes cookie és webhelyadat megtekintése elemre az összes tárolt cookie és a kapcsolódó webhelyadatok megtekintéséhez. Az összes cookie engedélyezése A cookie-k engedélyezésével a webhelyek adatokat menthetnek és lekérhetnek a böngészőben, ami a beállítások és a bejelentkezési adatok megjegyzésével javíthatja a böngészési élményt. Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, és engedélyezze a Cookie-adatok mentésének és olvasásának engedélyezése a webhelyek számára (ajánlott) kapcsolót az összes cookie engedélyezéséhez. Cookie-k engedélyezése egy adott webhelyről A cookie-k engedélyezésével a webhelyek adatokat menthetnek és lekérhetnek a böngészőben, ami a beállítások és a bejelentkezési adatok megjegyzésével javíthatja a böngészési élményt. Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, majd a Cookie-k mentéséhez válassza az Engedélyezett lehetőséget. Válassza a Webhely hozzáadása lehetőséget a cookie-k webhelyenkénti engedélyezéséhez a webhely URL-címének megadásával. Harmadik féltől származó cookie-k letiltása Ha nem szeretné, hogy a harmadik felek webhelyei cookie-kat tároljanak a számítógépén, letilthatja a cookie-kat. Ha ezt teszi, akkor előfordulhat, hogy egyes weblapok nem jelennek meg megfelelően, illetve a webhely üzenetben tájékoztatja, hogy megtekintéséhez engedélyeznie kell a cookie-kat. Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, és engedélyezze a Külső cookie-k letiltása kapcsolót. Az összes cookie blokkolása: Ha nem szeretné, hogy a harmadik felek webhelyei cookie-kat tároljanak a számítógépén, letilthatja a cookie-kat. Ha ezt teszi, akkor előfordulhat, hogy egyes weblapok nem jelennek meg megfelelően, illetve a webhely üzenetben tájékoztatja, hogy megtekintéséhez engedélyeznie kell a cookie-kat. Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, és tiltsa le a Cookie-adatok mentésének és olvasásának engedélyezése a webhelyek számára (ajánlott) beállítást az összes cookie letiltásához. Cookie-k letiltása egy adott webhelyről A Microsoft Edge lehetővé teszi, hogy letiltsa a cookie-kat egy adott webhelyről, de ez megakadályozhatja, hogy egyes lapok megfelelően jelenjenek meg, vagy egy webhely üzenete tájékoztatja Arról, hogy engedélyeznie kell a cookie-kat a webhely megtekintéséhez. Cookie-k letiltása egy adott webhelyről: Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, és lépjen a Nem engedélyezett a cookie-k mentéséhez és olvasásához . Válassza a Webhely hozzáadása lehetőséget a cookie-k webhelyenkénti letiltásához a webhely URL-címének megadásával. Az összes cookie törlése Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget. Válassza a Böngészési adatok törlése lehetőséget, majd válassza a Böngészési adatok törlése elem mellett található törlési elemet. Az Időtartomány listában jelöljön ki egy időtartományt. Jelölje be a Cookie-k és egyéb webhelyadatok jelölőnégyzetet, és válassza a Törlés most gombot. Megjegyzés: Másik lehetőségként törölheti a cookie-kat a CTRL + SHIFT + DELETE billentyűkombináció együttes lenyomásával, majd a 4. és 5. lépéssel. A cookie-k és az egyéb webhelyadatok mostantól törlődnek a kiválasztott időtartományban. Ez kijelentkezteti a legtöbb webhelyről. Cookie-k törlése adott webhelyről Nyissa meg az Edge böngészőt, válassza a Beállítások és egyebek > Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Cookie-k lehetőséget, majd kattintson az Összes cookie és webhelyadat megtekintése elemre, és keresse meg azt a webhelyet, amelynek a cookie-ját törölni szeretné. Válassza a lefelé mutató nyilat annak a webhelynek a jobb oldalán, amelynek a cookie-jait törölni szeretné, majd válassza a Törlés lehetőséget. A kiválasztott webhely cookie-jának törlése megtörtént. Ismételje meg ezt a lépést minden olyan webhely esetében, amelynek a cookie-jait törölni szeretné. Cookie-k törlése a böngésző minden egyes bezárásakor Nyissa meg az Edge böngészőt, válassza a Beállítások és egyebek > Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget . Válassza a Böngészési adatok törlése lehetőséget, majd válassza a Válassza ki, hogy mit töröljön a böngésző minden egyes bezárásakor . Kapcsolja be a Cookie-k és egyéb webhelyadatok váltógombot. Ha ez a funkció be van kapcsolva, minden alkalommal, amikor bezárja az Edge böngészőt, a cookie-k és más webhelyadatok törlődnek. Ez kijelentkezteti a legtöbb webhelyről. Cookie-k használata az oldal előzetes betöltéséhez a gyorsabb böngészés érdekében Nyissa meg az Edge böngészőt, és válassza a Beállítások és egyebek elemet a böngészőablak jobb felső sarkában. Válassza a Beállítások > Adatvédelem, keresés és szolgáltatások lehetőséget. Válassza a Cookie-k lehetőséget, és engedélyezze az Oldalak előzetes betöltése váltógombot a gyorsabb böngészéshez és kereséshez. FELIRATKOZÁS RSS-HÍRCSATORNÁKRA További segítségre van szüksége? További lehetőségeket szeretne? Felfedezés Közösség Kapcsolatfelvétel Fedezze fel az előfizetés előnyeit, böngésszen az oktatóanyagok között, ismerje meg, hogyan teheti biztonságossá eszközét, és így tovább. A Microsoft 365-előfizetés előnyei Microsoft 365-képzés Microsoft Biztonság Akadálymentességi központ A közösségek segítségével kérdéseket tehet fel és válaszolhat meg, visszajelzést adhat, és részletes ismeretekkel rendelkező szakértőktől hallhat. Kérdezze meg a Microsoft-közösséget Microsoft technikai közösség Windows Insider-résztvevők Microsoft 365 Insider-résztvevők Megoldást találhat gyakori problémákra, vagy segítséget kaphat egy támogatási szakembertől. Online támogatás Hasznos volt ez az információ? Igen Nem Köszönjük! Van további visszajelzése a Microsoft számára? Segítene nekünk a fejlesztésben? (Küldjön visszajelzést a Microsoftnak, hogy segíthessünk.) Mennyire elégedett a fordítás minőségével? Mi volt hatással a felhasználói élményére? Megoldódott a probléma Világos útmutatás Könnyen követhető Zsargon nélküli szöveg A képek segítettek A fordítás minősége Nem jelent meg megfelelően a képernyőmön Helytelen utasítások Túl technikai Nincs elég információ Nincs elég kép A fordítás minősége Szeretne további visszajelzést küldeni? (Nem kötelező) Visszajelzés küldése Ha elküldi a visszajelzést, a Microsoft felhasználja azt a termékei és szolgáltatásai továbbfejlesztéséhez. Az informatikai rendszergazda képes lesz ezeket az adatokat összegyűjteni. Adatvédelmi nyilatkozat. Köszönjük a visszajelzését! × Újdonságok Copilot szervezeteknek Copilot személyes használatra Microsoft 365 Fedezze fel a Microsoft termékeit Windows 11-alkalmazások Microsoft Store Fiókprofil Letöltőközpont Microsoft Store-támogatás Visszaküldés Rendeléskövetés Újrahasznosítás Commercial Warranties Oktatás Microsoft Education Oktatási eszközök Microsoft Teams oktatáshoz Microsoft 365 Education Office oktatási verzió Oktatóképzés és -fejlesztés Ajánlatok diákoknak és szülőknek Azure diákoknak Üzlet Microsoft-biztonság Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamshez készült Fejlesztők és IT Microsoft-fejlesztő Microsoft Learn AI piactéri alkalmazások támogatása Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Vállalat Karrier A Microsoft bemutatása Vállalati hírek Adatvédelem a Microsoftnál Befektetők Korrupció- és Vesztegetésellenes Elkötelezettségünk Fenntarthatóság Magyar (Magyarország) Adatvédelmi beállítások elutasítása ikon Adatvédelemmel kapcsolatos választási lehetőségek Adatvédelmi beállítások elutasítása ikon Adatvédelemmel kapcsolatos választási lehetőségek Fogyasztói állapot adatainak védelme Kapcsolatfelvétel a Microsofttal Adatvédelem Cookie-k kezelése Használati feltételek Védjegyek A hirdetéseinkről EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://support.microsoft.com/pt-pt/windows/gerir-cookies-no-microsoft-edge-ver-permitir-bloquear-eliminar-e-utilizar-168dab11-0753-043d-7c16-ede5947fc64d | Gerir cookies no Microsoft Edge: ver, permitir, bloquear, eliminar e utilizar - Suporte da Microsoft Tópicos relacionados × Segurança e privacidade do Windows Descrição geral Descrição geral da segurança e privacidade Segurança do Windows Obtenha ajuda com a segurança do Windows Mantenha a proteção com a Segurança do Windows Antes de reciclar, vender ou oferecer a sua Xbox ou PC Windows Remover software malicioso do seu PC Windows Segurança do Windows Obtenha ajuda com a segurança do Windows Ver e eliminar o histórico do browser no Microsoft Edge Eliminar e gerir cookies Remova com segurança os seus conteúdos valiosos ao reinstalar o Windows Localizar e bloquear um dispositivo Windows perdido Privacidade do Windows Obtenha ajuda com a privacidade do Windows Definições de privacidade do Windows utilizadas pelas aplicações Ver os seus dados no dashboard de privacidade Avançar para o conteúdo principal Microsoft Suporte Suporte Suporte Home Page Microsoft 365 Office Produtos Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mais... Dispositivos Surface Acessórios para PC Xbox Jogos de PC HoloLens Surface Hub Garantias de hardware Conta e faturação Conta Microsoft Store e faturação Recursos Novidades Fóruns da comunidade Administradores do Microsoft 365 Portal para Pequenas Empresas Programador Educação Comunicar uma fraude de suporte técnico Segurança do produto Mais Comprar o Microsoft 365 Toda a Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Promoções Pequena Empresa Suporte Software Software Aplicações do Windows IA OneDrive Outlook Mudança do Skype para o Teams OneNote Microsoft Teams PCs e dispositivos PCs e dispositivos Comprar a Xbox Acessórios Entretenimento Entretenimento Xbox Game Pass Ultimate Xbox e jogos Jogos para PC Negócios Negócios Microsoft Security Azure Dynamics 365 Microsoft 365 para empresas Microsoft Industry Microsoft Power Platform Windows 365 Desenvolvedor & it Desenvolvedor & it Programador Microsoft Microsoft Learn Suporte para aplicações do marketplace de IA Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Outros Outros Transferências gratuitas e segurança Educação Cartões de oferta da Microsoft Licenciamento Ver mapa do Site Procurar Procurar ajuda Sem resultados Cancelar Iniciar sessão Iniciar sessão com a Microsoft Iniciar sessão ou criar uma conta. Olá, Selecione uma conta diferente. Tem várias contas Selecione a conta com a qual pretende iniciar sessão. Tópicos relacionados Segurança e privacidade do Windows Descrição geral Descrição geral da segurança e privacidade Segurança do Windows Obtenha ajuda com a segurança do Windows Mantenha a proteção com a Segurança do Windows Antes de reciclar, vender ou oferecer a sua Xbox ou PC Windows Remover software malicioso do seu PC Windows Segurança do Windows Obtenha ajuda com a segurança do Windows Ver e eliminar o histórico do browser no Microsoft Edge Eliminar e gerir cookies Remova com segurança os seus conteúdos valiosos ao reinstalar o Windows Localizar e bloquear um dispositivo Windows perdido Privacidade do Windows Obtenha ajuda com a privacidade do Windows Definições de privacidade do Windows utilizadas pelas aplicações Ver os seus dados no dashboard de privacidade Gerir cookies no Microsoft Edge: ver, permitir, bloquear, eliminar e utilizar Aplica-se A Windows 10 Windows 11 Microsoft Edge Os cookies são pequenos pedaços de dados armazenados no seu dispositivo por sites que visita. Servem várias finalidades, como memorizar credenciais de início de sessão, preferências de site e controlar o comportamento dos utilizadores. No entanto, poderá querer eliminar cookies por motivos de privacidade ou resolver problemas de navegação. Este artigo fornece instruções sobre como: Ver todos os cookies Permitir todos os cookies Permitir cookies a partir de um site específico Bloquear cookies de terceiros Bloquear todos os cookies Bloquear cookies de um site específico Eliminar todos os cookies Eliminar cookies de um site específico Eliminar cookies sempre que fechar o browser Utilizar cookies para pré-carregar a página para uma navegação mais rápida Ver todos os cookies Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e, em seguida, clique em Ver todos os cookies e dados do site para ver todos os cookies armazenados e informações relacionadas do site. Permitir todos os cookies Ao permitir cookies, os sites poderão guardar e obter dados no browser, o que pode melhorar a sua experiência de navegação ao memorizar as suas preferências e informações de início de sessão. Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e ative o botão de alternar Permitir que os sites guardem e leiam dados de cookies (recomendado) para permitir todos os cookies. Permitir cookies de um site específico Ao permitir cookies, os sites poderão guardar e obter dados no browser, o que pode melhorar a sua experiência de navegação ao memorizar as suas preferências e informações de início de sessão. Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e aceda a Permitido para guardar cookies. Selecione Adicionar site para permitir cookies por site ao introduzir o URL do site. Bloquear cookies de terceiros Se não quiser que sites de terceiros armazenem cookies no seu PC, pode bloquear cookies. Mas o bloqueio dos cookies poderá impedir que determinadas páginas sejam apresentadas corretamente ou poderá receber uma mensagem de um site a informá-lo de que terá de aceitar cookies para poder ver o site. Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e ative o botão de alternar Bloquear cookies de terceiros. Bloquear todos os cookies Se não quiser que sites de terceiros armazenem cookies no seu PC, pode bloquear cookies. Mas o bloqueio dos cookies poderá impedir que determinadas páginas sejam apresentadas corretamente ou poderá receber uma mensagem de um site a informá-lo de que terá de aceitar cookies para poder ver o site. Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e desative Permitir que os sites guardem e leiam dados de cookies (recomendado) para bloquear todos os cookies. Bloquear cookies de um site específico O Microsoft Edge permite-lhe bloquear cookies de um site específico. No entanto, fazê-lo poderá impedir que algumas páginas sejam apresentadas corretamente ou poderá receber uma mensagem de um site a informá-lo de que precisa de permitir que os cookies vejam esse site. Para bloquear cookies de um site específico: Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e aceda a Não permitido guardar e ler cookies . Selecione Adicionar site para bloquear cookies por site ao introduzir o URL do site. Eliminar todos os cookies Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Limpar dados de navegação e, em seguida, selecione Escolher o que limpar localizado junto a Limpar dados de navegação agora . Em Intervalo de tempo , selecione um intervalo de tempo na lista. Selecione Cookies e outros dados do site e, em seguida, selecione Limpar agora . Nota: Em alternativa, pode eliminar os cookies ao premir CTRL + SHIFT + DELETE em conjunto e, em seguida, prosseguir com os passos 4 e 5. Todos os cookies e outros dados do site serão eliminados para o intervalo de tempo que selecionou. Este procedimento termina a sua sessão na maioria dos sites. Eliminar cookies de um site específico Abra o browser Edge, selecione Definições e muito mais > Definições > Privacidade, pesquisa e serviços . Selecione Cookies e, em seguida, clique em Ver todos os cookies e dados do site e procure o site cujos cookies pretende eliminar. Selecione a seta para baixo à direita do site cujos cookies pretende eliminar e selecione Eliminar . Os cookies do site que selecionou são agora eliminados. Repita este passo para qualquer site cujos cookies pretende eliminar. Eliminar cookies sempre que fechar o browser Abra o browser Edge, selecione Definições e muito mais > Definições > Privacidade, pesquisa e serviços . Selecione Limpar dados de navegação e, em seguida, selecione Escolher o que limpar sempre que fechar o browser . Ative a definição Cookies e outros dados do site com o botão de alternar. Assim que esta funcionalidade estiver ativada, sempre que fechar o browser Edge, todos os cookies e outros dados do site são eliminados. Este procedimento termina a sua sessão na maioria dos sites. Utilizar cookies para pré-carregar a página para uma navegação mais rápida Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Definições > Privacidade, pesquisa e serviços . Selecione Cookies e ative o botão de alternar Pré-carregar páginas para uma navegação e pesquisa mais rápidas. SUBSCREVER FEEDS RSS Precisa de mais ajuda? Quer mais opções? Descobrir Comunidade Contacte-nos Explore os benefícios da subscrição, navegue em cursos de formação, saiba como proteger o seu dispositivo e muito mais. Benefícios da subscrição do Microsoft 365 Formação do Microsoft 365 Segurança da Microsoft Centro de acessibilidade As comunidades ajudam-no a colocar e a responder perguntas, a dar feedback e a ouvir especialistas com conhecimentos abrangentes. Pergunte à Comunidade Microsoft Microsoft Tech Community (Comunidade Tecnológica Microsoft) Utilizadores do Windows Insider Microsoft 365 Insiders Encontre soluções para problemas comuns ou obtenha ajuda de um agente de suporte. Suporte online Estas informações foram úteis? Sim Não Obrigado! Tem mais comentários para a Microsoft? Pode ajudar-nos a melhorar? (Enviar comentários à Microsoft para que possamos ajudar.) Quão satisfeito está com a qualidade do idioma? O que afetou a sua experiência? Resolveu o meu problema Instruções claras Fácil de seguir Sem linguagem incompreensível As imagens ajudaram Qualidade da tradução Não correspondia ao meu ecrã Instruções incorretas Demasiado técnico Informações insuficientes Imagens insuficientes Qualidade da tradução Tem feedback adicional? (Opcional) Submeter feedback Ao selecionar submeter, o seu feedback será utilizado para melhorar os produtos e serviços da Microsoft. O seu administrador de TI poderá recolher estes dados. Declaração de Privacidade. Obrigado pelo seu feedback! × Novidades Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot para organizações Copilot para uso pessoal Microsoft 365 Explorar produtos Microsoft Aplicações do Windows 11 Microsoft Store Perfil da conta Centro de Transferências Suporte da Microsoft Store Devoluções Controlo de encomendas Reciclagem Garantias Comercias Educação Microsoft Educação Dispositivos para educação Microsoft Teams para Educação Microsoft 365 Educação Office Educação Formação e desenvolvimento de educadores Promoções para estudantes e pais Azure para estudantes Empresa Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Pequena Empresa Programador e TI Programador Microsoft Microsoft Learn Suporte para aplicações do marketplace de IA Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Empresa Carreiras Acerca da Microsoft Notícias da empresa Privacidade na Microsoft Investidores Sustentabilidade Português (Portugal) Ícone de Optar por Não Participar em As Suas Opções de Privacidade As suas Escolhas de Privacidade Ícone de Optar por Não Participar em As Suas Opções de Privacidade As suas Escolhas de Privacidade Privacidade da Saúde do Consumidor Contactar a Microsoft Privacidade Gerir cookies Termos de utilização Marcas Registadas Acerca dos nossos anúncios EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://support.microsoft.com/ar-sa/windows/%D8%B9%D8%B1%D8%B6-%D8%A8%D9%8A%D8%A7%D9%86%D8%A7%D8%AA%D9%83-%D8%B9%D9%84%D9%89-%D9%84%D9%88%D8%AD%D8%A9-%D9%85%D8%B9%D9%84%D9%88%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%AE%D8%B5%D9%88%D8%B5%D9%8A%D8%A9-03d3e27f-1981-5ff4-ba1c-d6b1031ae433 | عرض بياناتك على لوحة معلومات الخصوصية - دعم Microsoft المواضيع ذات الصلة × الأمن والأمان والخصوصية في Windows نظرة عامة نظرة عامة على الأمان والسلامة والخصوصية أمان Windows الحصول على تعليمات حول أمان Windows المحافظة على الحماية باستخدام أمان Windows قبل إعادة تدوير أو بيع أو إهداء جهاز Xbox أو جهاز الكمبيوتر الشخصي الذي يعمل بنظام Windows إزالة البرامج الضارة من كمبيوتر Windows أمان Windows الحصول على تعليمات حول أمان Windows عرض محفوظات المستعرض وحذفها في Microsoft Edge حذف ملفات تعريف الارتباط وإدارتها إزالة المحتوى القيم بأمان عند إعادة تثبيت Windows البحث عن جهاز Windows مفقود وتأمينه خصوصية Windows الحصول على تعليمات حول خصوصية Windows إعدادات الخصوصية في Windows التي تستخدمها التطبيقات عرض بياناتك على لوحة معلومات الخصوصية تخطي إلى المحتوى الرئيسي Microsoft الدعم الدعم الدعم الصفحة الرئيسية Microsoft 365 Office المنتجات Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows المزيد ... الأجهزة Surface ملحقات الكمبيوتر Xbox ألعاب الكمبيوتر HoloLens Surface Hub ضمانات الأجهزة الحساب & والفوترة حساب Microsoft Store &والفوترة الموارد أحدث الميزات منتديات المجتمعات Microsoft 365 للمسؤولين مدخل الشركات الصغيرة المطور التعليم الإبلاغ عن دعم احتيالي أمان المنتج المزيد شراء Microsoft 365 Microsoft بالكامل Global Microsoft 365 Office Copilot Windows Surface Xbox الدعم Software Software تطبيقات Windows الذكاء الاصطناعي OneDrive Outlook انتقال من Skype إلى Teams OneNote Microsoft Teams PCs & Devices PCs & Devices تسوق للحصول على Xbox Accessories Entertainment Entertainment Xbox Game Pass Ultimate Xbox Game Pass Essential Xbox والألعاب ألعاب الكمبيوتر الشخصي اعمال اعمال الأمان من Microsoft Azure Dynamics 365 Microsoft 365 for business صناعة Microsoft Microsoft Power Platform Windows 365 المطور وذلك المطور وذلك مطور Microsoft Microsoft Learn دعم تطبيقات مواقع تسوق الذكاء الاصطناعي مجتمع Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards أخرى أخرى الأمان والتنزيلات المجانية التعليم بطاقات الهدايا عرض خريطة الموقع بحث بحث عن التعليمات لا نتائج إلغاء تسجيل الدخول تسجيل الدخول باستخدام حساب Microsoft تسجيل الدخول أو إنشاء حساب. مرحباً، تحديد استخدام حساب مختلف! لديك حسابات متعددة اختر الحساب الذي تريد تسجيل الدخول باستخدامه. المواضيع ذات الصلة الأمن والأمان والخصوصية في Windows نظرة عامة نظرة عامة على الأمان والسلامة والخصوصية أمان Windows الحصول على تعليمات حول أمان Windows المحافظة على الحماية باستخدام أمان Windows قبل إعادة تدوير أو بيع أو إهداء جهاز Xbox أو جهاز الكمبيوتر الشخصي الذي يعمل بنظام Windows إزالة البرامج الضارة من كمبيوتر Windows أمان Windows الحصول على تعليمات حول أمان Windows عرض محفوظات المستعرض وحذفها في Microsoft Edge حذف ملفات تعريف الارتباط وإدارتها إزالة المحتوى القيم بأمان عند إعادة تثبيت Windows البحث عن جهاز Windows مفقود وتأمينه خصوصية Windows الحصول على تعليمات حول خصوصية Windows إعدادات الخصوصية في Windows التي تستخدمها التطبيقات عرض بياناتك على لوحة معلومات الخصوصية عرض بياناتك على لوحة معلومات الخصوصية ينطبق على Privacy Windows 10 Windows 11 لوحة معلومات حساب Microsoft ملاحظة: تعمل Microsoft على تحديث الطريقة التي نطلب بها إذن استخدام بياناتك الصوتية لتحسين منتجات Microsoft التي تستخدم تقنية التعرف على الكلام لدينا. قد يؤثر هذا على البيانات التي تراها على لوحة معلومات الخصوصية الخاصة بك. لمعرفة المزيد حول هذه التغييرات، راجع كيف تحمي Microsoft خصوصيتي مع تحسين تقنية التعرف على الكلام؟ عند استخدام منتجات Microsoft وخدماتها عند تسجيل الدخول باستخدام حساب Microsoft الخاص بك، يمكنك اختيار حفظ البيانات إلى السحابة لمساعدتك في تحسين تجربتك. توفر لك لوحة معلومات الخصوصية أدوات لعرض هذه البيانات ومسحها ولإدارة إعدادات الخصوصية للمنتجات التي تستخدمها. يمكن أن تتضمن البيانات التي تظهر على لوحة المعلومات البيانات المتعلقة بعمليات البحث في Bing وCortana، واستعراض Microsoft Edge والموقع والصوت والوسائط والتطبيقات والخدمات ونشاط الخدمات. بعد مسح بياناتك، سنحذفها من لوحة المعلومات ونبدأ إزالتها من أنظمتنا. قد تتم مشاركة التطبيق والخدمة مع موفري الخدمات وتطبيقات الجهات الخارجية التي تقوم بتسجيل الدخول إليها باستخدام حساب Microsoft الخاص بك. إذا اخترت مسح هذه المعلومات، فسوف نمسح جميع بيانات النشاط حول التطبيقات المعنية وتفاصيل حول وقت تشغيل التطبيق أو إغلاقه والفترة التي استخدمت خلالها التطبيق ومعلومات تشخيصية أخرى. إذا كنت ترغب أيضًا في إزالة أي بيانات نشاط مقترنة بملفات تعريف الارتباط في المستعرض الخاص بك، فيجب مسح ملفات تعريف الارتباط في Microsoft Edge أو Internet Explorer. إذا كنت تستخدم مستعرضًا آخر، فراجع إرشاداته. يمكنك إدارة البيانات والإعدادات علي الصفحات التالية للوحة معلومات الخصوصية: لإدارة سجل الأنشطة الخاص بحسابك، انتقل إلى صفحة الصفحة الرئيسية للوحة معلومات الخصوصية . لإدارة إعدادات الإعلانات، انتقل إلى صفحة إعدادات الإعلانات . إذا كنت تستخدم Microsoft Edge الجديد، فتصفح يظهر النشاط إذا كنت: لقد قمت بتشغيل المزامنة لمحفوظات التصفح. تعرّف على المزيد لقد قمت بتشغيل إعلانات وتجارب مخصصة لـ Bing والأخبار من Microsoft وخدمات Microsoft الأخرى. تعرّف على المزيد إذا كنت تستخدم Microsoft Edge القديم، فسيظهر نشاط الاستعراض إذا كنت: قد قمت بتسجيل الدخول إلى Windows باستخدام حساب Microsoft الخاص بك أثناء التصفح. حدد كامل لإعداد البيانات التشخيصية . قم بتشغيل Cortana في Windows، وفي Microsoft Edge. تشغيل محفوظات الاستعراض في Cortana. لمزيد من المعلومات حول Microsoft Edge، راجع التعرف على المزيد حول Microsoft Edge بيانات الاستعراض والخصوصية و استعراض InPrivate في Microsoft Edge . يظهر نشاط البحث فقط في الحالات التالية: أجريت عمليات بحث باستخدام Bing ولكنك لم تسجل دخولك إلى Bing باستخدام حساب Microsoft الخاص بك — على الرغم من أنه ما زال باستطاعتك عرض نشاط البحث على صفحة محفوظات البحث على Bing.com. وصلت إلى صفحات Bing عند البحث من Cortana. لا يظهر نشاط البحث إذا أجريت البحث من تطبيق Cortana على هاتف يستخدم نظام التشغيل iOS أو Android. راجع بيان الخصوصية Microsoft لمعرفة المزيد حول البيانات التي نجمعها أو اعرف المزيد حول الخصوصية في Windows . إدارة البيانات التي يتم جمعها تستخدم البيانات التي يجمعها Microsoft لإضفاء طابع شخصي على تجاربك، والمساعدة في الحفاظ على سلامتك، وتحسين برامجنا وخدماتنا وأجهزتنا. يمكنك اختيار البيانات التي تريد مشاركتها. لتغيير إعدادات الخصوصية على جهاز Windows 10، حدد زر البدء > الإعدادات > الخصوصية . لتغيير إعدادات الخصوصية على جهاز Windows 11، حدد زر البدء > الإعدادات > الخصوصية والأمان . تلميحات تتعلق بعرض بياناتك إذا استغرق ظهور بياناتك في لوحة معلومات الخصوصية وقتًا طويلاً، فتحقق مما يلي: جهازك موصول وقيد التشغيل. جهازك متصل بالإنترنت بشكل متواصل—لا تستخدم اتصالاً محدودًا بالإنترنت. موفر البطارية متوقف عن التشغيل إذا كان جهازك يعمل باستخدام طاقة البطارية. للتحقق، حدد بدء > الإعدادات > النظام ثم حدد البطارية في Windows 10 أو الطاقة و البطارية في Windows 11. تأكد من أن إعداد موفر البطارية متوقف . إذا لم تظهر البيانات التي كنت تتوقعها، فقد يكون السبب: لم تسجل دخولك باستخدام حساب Microsoft. قمت مؤخرًا بمسح بياناتك وأوقفت تشغيل الإعدادات التي تسمح لشركة Microsoft بجمع البيانات. أنت لا تستخدم الميزة أو الخدمة التي تحاول رؤية البيانات المتعلقة بها. قد يعود سبب ذلك إلى احتمال أن يكون عمرك ما زال صغيرًا لاستخدامها، أو الميزة أو الخدمة غير متوفرة في بلدك أو منطقتك. لا يمكن عرض البيانات الآن. سوف تعرضها Microsoft عندما تصبح متوفرة. البيانات غير متوفرة على لوحة معلومات الخصوصية. لمعرفة كيفية العثور على مزيد من البيانات حول المنتجات التي تستخدمها، تفضل بزيارة صفحة زيارة الخصوصية في Microsoft وتحديد المنتجات التي تهتم بها، مثل Windows أو Xbox. فيما يتعلق بالبيانات الشخصية التي لا نقوم بتضمينها على لوحة المعلومات، اتصل بفريق الخصوصية . ملاحظات: تعرض لوحة معلومات الخصوصية البيانات التي قمنا بجمعها. إذا أردت رؤية نشاط تسجيل الدخول إلى حساب Microsoft، فيمكنك عرض النشاط الأخير . إذا ساورك القلق بشأن دخول شخص غير مصرح له إلى حسابك، فراجع استرداد حساب Microsoft . قد لا يتم عرض بعض البيانات أو حذفها وفقا لبيان الخصوصية — علي سبيل المثال، بعض القوانين تمنعنا من الكشف عن بيانات مثل أرقام الحسابات المالية أو أرقام تحديد الهوية الصادرة من الحكومة أو البيانات التي قد تؤثر سلبًا علي الحقوق والحريات الخاصة بالآخرين. للحصول علي مزيد من المعلومات، راجع قسم "كيفية الوصول إلى بياناتك الشخصية والتحكم فيها" في بيان الخصوصية . الاشتراك في موجز ويب لـ RSS هل تحتاج إلى مزيد من المساعدة؟ الخروج من الخيارات إضافية؟ اكتشاف المجتمع الاتصال بنا استكشف مزايا الاشتراك، واستعرض الدورات التدريبية، وتعرف على كيفية تأمين جهازك، والمزيد. ميزات اشتراك Microsoft 365 تدريب Microsoft 365 أمان من Microsoft مركز إمكانية وصول ذوي الاحتياجات الخاصة تساعدك المجتمعات على طرح الأسئلة والإجابة عليها، وتقديم الملاحظات، وسماعها من الخبراء ذوي الاطلاع الواسع. طرح أسئلة في Microsoft Community مجتمع Microsoft التقني مشتركو Windows Insider المشاركون في برنامج Microsoft 365 Insider ابحث عن حلول للمشاكل الشائعة أو احصل على المساعدة من وكيل دعم. الدعم عبر الإنترنت هل كانت المعلومات مفيدة؟ نعم لا شكراً لك! هل لديك أي ملاحظات إضافية لـ Microsoft? هل يمكنك مساعدتنا على التحسين؟ (أرسل ملاحظات إلى Microsoft حتى نتمكن من المساعدة.) ما مدى رضاك عن جودة اللغة؟ ما الذي أثّر في تجربتك؟ ساعد على حل مشكلتي مسح الإرشادات سهل المتابعة لا توجد لغة غير مفهومة كانت الصور مساعِدة جودة الترجمة غير متطابق مع شاشتي إرشادات غير صحيحة تقني بدرجة كبيرة معلومات غير كافية صور غير كافية جودة الترجمة هل لديك أي ملاحظات إضافية؟ (اختياري) إرسال الملاحظات بالضغط على "إرسال"، سيتم استخدام ملاحظاتك لتحسين منتجات Microsoft وخدماتها. سيتمكن مسؤول تكنولوجيا المعلومات لديك من جمع هذه البيانات. بيان الخصوصية. نشكرك على ملاحظاتك! × الجديد Surface Pro Surface Laptop Copilot للمؤسسات Copilot للاستخدام الشخصي Microsoft 365 استكشف منتجات Microsoft Microsoft Store ملف تعريف الحساب مركز التنزيل تعقب الطلب التعليم Microsoft Education أجهزة التعليم Microsoft Teams للتعليم Microsoft 365 Education Office Education تدريب المعلمين وتطويرهم عروض للطلاب وأولياء الأمور Azure للطلاب الأعمال الأمان من Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams المطور وتكنولوجيا المعلومات مطور Microsoft Microsoft Learn دعم تطبيقات مواقع تسوق الذكاء الاصطناعي مجتمع Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio الشركة الوظائف نبذة عن Microsoft الخصوصية في Microsoft المستثمرون الاستدامة العربية (المملكة العربية السعودية) أيقونة إلغاء الاشتراك في اختيارات خصوصيتك خيارات خصوصيتك أيقونة إلغاء الاشتراك في اختيارات خصوصيتك خيارات خصوصيتك خصوصية صحة المستهلك الاتصال بشركة Microsoft الخصوصية إدارة ملفات تعريف الارتباط بنود الاستخدام العلامات التجارية حول إعلاناتنا © Microsoft 2026 | 2026-01-13T09:30:34 |
https://www.php.net/manual/it/function.session-regenerate-id.php | PHP: session_regenerate_id - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_register_shutdown » « session_name Manuale PHP Guida Funzioni Estensioni di sessione Sessions Session Funzioni Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_regenerate_id (PHP 4 >= 4.3.2, PHP 5, PHP 7, PHP 8) session_regenerate_id — Update the current session id with a newly generated one Descrizione session_regenerate_id ( bool $delete_old_session = false ): bool session_regenerate_id() will replace the current session id with a new one, and keep the current session information. When session.use_trans_sid is enabled, output must be started after session_regenerate_id() call. Otherwise, old session ID is used. Avviso Currently, session_regenerate_id does not handle an unstable network well, e.g. Mobile and WiFi network. Therefore, you may experience a lost session by calling session_regenerate_id. You should not destroy old session data immediately, but should use destroy time-stamp and control access to old session ID. Otherwise, concurrent access to page may result in inconsistent state, or you may have lost session, or it may cause client (browser) side race condition and may create many session ID needlessly. Immediate session data deletion disables session hijack attack detection and prevention also. Elenco dei parametri delete_old_session Whether to delete the old associated session file or not. You should not delete old session if you need to avoid races caused by deletion or detect/avoid session hijack attacks. Valori restituiti Restituisce true in caso di successo, false in caso di fallimento. Esempi Example #1 A session_regenerate_id() example <?php // NOTE: This code is not fully working code, but an example! session_start (); // Check destroyed time-stamp if (isset( $_SESSION [ 'destroyed' ]) && $_SESSION [ 'destroyed' ] < time () - 300 ) { // Should not happen usually. This could be attack or due to unstable network. // Remove all authentication status of this users session. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } $old_sessionid = session_id (); // Set destroyed timestamp $_SESSION [ 'destroyed' ] = time (); // session_regenerate_id() saves old session data // Simply calling session_regenerate_id() may result in lost session, etc. // See next example. session_regenerate_id (); // New session does not need destroyed timestamp unset( $_SESSION [ 'destroyed' ]); $new_sessionid = session_id (); echo "Old Session: $old_sessionid <br />" ; echo "New Session: $new_sessionid <br />" ; print_r ( $_SESSION ); ?> Current session module does not handle unstable network well. You should manage session ID to avoid lost session by session_regenerate_id. Example #2 Avoiding lost session by session_regenerate_id() <?php // NOTE: This code is not fully working code, but an example! // my_session_start() and my_session_regenerate_id() avoid lost sessions by // unstable network. In addition, this code may prevent exploiting stolen // session by attackers. function my_session_start () { session_start (); if (isset( $_SESSION [ 'destroyed' ])) { if ( $_SESSION [ 'destroyed' ] < time ()- 300 ) { // Should not happen usually. This could be attack or due to unstable network. // Remove all authentication status of this users session. remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } if (isset( $_SESSION [ 'new_session_id' ])) { // Not fully expired yet. Could be lost cookie by unstable network. // Try again to set proper session ID cookie. // NOTE: Do not try to set session ID again if you would like to remove // authentication flag. session_commit (); session_id ( $_SESSION [ 'new_session_id' ]); // New session ID should exist session_start (); return; } } } function my_session_regenerate_id () { // New session ID is required to set proper session ID // when session ID is not set due to unstable network. $new_session_id = session_create_id (); $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit (); // Start session with new session ID session_id ( $new_session_id ); ini_set ( 'session.use_strict_mode' , 0 ); session_start (); ini_set ( 'session.use_strict_mode' , 1 ); // New session does not need them unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Vedere anche: session_id() - Assume o imposta l'id di sessione corrente session_create_id() - Create new session id session_start() - Inizializza i dati di sessione session_destroy() - Distrugge tutti i dati registrati in una sessione session_reset() - Re-initialize session array with original values session_name() - Recupera e/o imposta il nome della sessione corrente Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 22 notes up down 42 tedivm at tedivm dot com ¶ 9 years ago I wrote the current top voted comment on this and wanted to add something. The existing code from my previous comment generates it's nonces in an insecure way- <?php $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); ?> Since "microtime" is predictable it makes brute forcing the nonce much easier. A better option would be something that utilizes randomness, such as- <?php bin2hex ( openssl_random_pseudo_bytes ( 32 )) ?> up down 42 tedivm at tedivm dot com ¶ 17 years ago I wrote the following code for a project I'm working on- it attempts to resolve the regenerate issue, as well as deal with a couple of other session related things. I tried to make it a little more generic and usable (for instance, in the full version it throws different types of exceptions for the different types of session issues), so hopefully someone might find it useful. <?php function regenerateSession ( $reload = false ) { // This token is used by forms to prevent cross site forgery attempts if(!isset( $_SESSION [ 'nonce' ]) || $reload ) $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); if(!isset( $_SESSION [ 'IPaddress' ]) || $reload ) $_SESSION [ 'IPaddress' ] = $_SERVER [ 'REMOTE_ADDR' ]; if(!isset( $_SESSION [ 'userAgent' ]) || $reload ) $_SESSION [ 'userAgent' ] = $_SERVER [ 'HTTP_USER_AGENT' ]; //$_SESSION['user_id'] = $this->user->getId(); // Set current session to expire in 1 minute $_SESSION [ 'OBSOLETE' ] = true ; $_SESSION [ 'EXPIRES' ] = time () + 60 ; // Create new session without destroying the old one session_regenerate_id ( false ); // Grab current session ID and close both sessions to allow other scripts to use them $newSession = session_id (); session_write_close (); // Set session ID to the new one, and start it back up again session_id ( $newSession ); session_start (); // Don't want this one to expire unset( $_SESSION [ 'OBSOLETE' ]); unset( $_SESSION [ 'EXPIRES' ]); } function checkSession () { try{ if( $_SESSION [ 'OBSOLETE' ] && ( $_SESSION [ 'EXPIRES' ] < time ())) throw new Exception ( 'Attempt to use expired session.' ); if(! is_numeric ( $_SESSION [ 'user_id' ])) throw new Exception ( 'No session started.' ); if( $_SESSION [ 'IPaddress' ] != $_SERVER [ 'REMOTE_ADDR' ]) throw new Exception ( 'IP Address mixmatch (possible session hijacking attempt).' ); if( $_SESSION [ 'userAgent' ] != $_SERVER [ 'HTTP_USER_AGENT' ]) throw new Exception ( 'Useragent mixmatch (possible session hijacking attempt).' ); if(! $this -> loadUser ( $_SESSION [ 'user_id' ])) throw new Exception ( 'Attempted to log in user that does not exist with ID: ' . $_SESSION [ 'user_id' ]); if(! $_SESSION [ 'OBSOLETE' ] && mt_rand ( 1 , 100 ) == 1 ) { $this -> regenerateSession (); } return true ; }catch( Exception $e ){ return false ; } } ?> up down 3 Rumour ¶ 2 years ago The code example provided of my_session_regenerate_id() DOES NOT work and DESTROYS all session variables. Plus the second ini_set gives an error. The code for regenerating (only that part, the rest seems fine) should simply be this: <?php function my_session_regenerate_id () { $new_session_id = session_create_id (); // backup session variables $keepSession = $_SESSION ; // add info for users with bad connection not receiving the new session id $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit () ; // Start session with new session ID ini_set ( 'session.use_strict_mode' , 0 ); session_id ( $new_session_id ); session_start (); $_SESSION = $keepSession ; } ?> up down 13 ei dot rik dot ops dot tad at gmail dot com ¶ 9 years ago In PHP 5.6 (and probably older versions), session_regenerate_id(true) do not trigger a read() call to the session handler for the new session id. In PHP 7, read() is triggered during session_regenerate_id(true). Nice to know when working with custom session handlers. up down 8 gr at gr5 dot org ¶ 14 years ago If you are trying to maintain 2 active sessions don't use session_regenerate_id(). Especially if the first session is closed and it's time to open the second. Because the session id is cached you also have to explicitly set it the second time. <?php session_name ( 'PHPSESSID' ); // redundant - here for clarity session_start (); // ...do stuff session_write_close (); // now switch to session 2... session_name ( 'PHPSESSID_2' ); if (isset( $_COOKIE [ 'phpsessid_2' ])) session_id ( $_COOKIE [ 'phpsessid_2' ]); // not doing this will simply reopen the first session again else session_id ( sha1 ( mt_rand ()); // dont use session_regenerate_id() here. Not creating a new id will create two cookies with same session id and same session variables session_start (); // ... do stuff with session 2 session_write_close (); ?> up down 13 ross at kndr dot org ¶ 21 years ago In a previous note, php at 5mm de describes how to prevent session hijacking by ensuring that the session id provided matches the HTTP_USER_AGENT and REMOTE_ADDR fields that were present when the session id was first issued. It should be noted that HTTP_USER_AGENT is supplied by the client, and so can be easily modified by a malicious user. Also, the client IP addresses can be spoofed, although that's a bit more difficult. Care should be taken when relying on the session for authentication. up down 4 babel at nosqamplease sympatico ca ¶ 21 years ago To add to php at 5mm de's comments: If the session is held over https, it's even better to save the client's cert or ssl session id instead of the hostname or ip, as it's proxy-transparent and more secure. up down 10 spmtrap at yahoo dot com ¶ 13 years ago `session_regenerate_id` sends a new cookie but doesn't overwrite the value stored in `$_COOKIE`. After calling `session_destroy`, the open session ID is discarded, so simply restarting the session with `session_start` (as done in Ben Johnson's code) will re-open the original, though now empty, session for the current request (subsequent requests will use the new session ID). Instead of `session_destroy`+`session_start`, use the `$delete_old_session` parameter to `session_regenerate_id` to delete the previous session data. <?php session_start (); /* Create a new session, deleting the previous session data. */ session_regenerate_id ( TRUE ); /* erase data carried over from previous session */ $_SESSION =array(); ?> To start a new session and leave the old untouched, simply leave out the argument to `session_regenerate_id`. up down 6 php at cny dot de ¶ 21 years ago Also note that REMOTE_ADDR may change on every request if the user comes through a proxy farm. Most AOL-users do. up down 2 k-gun !! mail ¶ 9 years ago Document example is wrong with usage of "session.use_strict_mode" according to RFC (says: "warning error for session_id() when use_strice_mode=1" on https://wiki.php.net/rfc/strict_sessions ). So, this directive affects "session_id()" not "session_start()". So usage must be like this; <?php // first set ini ini_set ( 'session.use_strict_mode' , '0' ); // and session_id ( $sid ); // then // maybe run this: ini_restore('session.use_strict_mode'); // then go on... ?> Refs (ctrl+f & use_strict_mode); https://wiki.php.net/rfc/strict_sessions https://wiki.php.net/rfc/session-create-id http://php.net/manual/en/function.session-id.php#119997 up down 3 madsen at sjovedyr.dk ¶ 22 years ago I had problems with a proxy changing a visitors session_id-cookie, so he'd get a LOT of errors when visiting my site. I handled the bogus session-id's like this. (Note: It only works in versions > 4.3.2.) <?php // Start a session and suppress error-messages. @ session_start (); // Catch bogus session-id's. if (! preg_match ( "/^[0-9a-z]*$/i" , session_id ())) { // Output a warning about the messed up session-id. $error -> handleError ( "WARN" , "Your session id is messed up, you might not be able to use some features on this site." ); // Generate a fresh session-id. session_regenerate_id (); } // Site contents. ?> Hope someone can use it. up down 1 Nicolas dot Chachereau at Infomaniak dot ch ¶ 20 years ago Session_destroy() does not only destroy the data associated with the current session_id (i.e. the file if you use the default session save handler), but also the session itself: if you call session_destroy() and then session_regenerate_id(), it will return false, and session_id() won't return anything. In order to manipulate a session after destroying it, you need to restart it. So in fact, the code mentionned by chris won't work. If you want to destroy the file associated with the old session_id, try the following: <?php session_start (); $old_sessid = session_id (); session_regenerate_id (); $new_sessid = session_id (); session_id ( $old_sessid ); session_destroy (); //If you don't copy the $_SESSION array, you won't be able to use the data associated with the old session id. $old_session = $_SESSION ; session_id ( $new_sessid ); session_start (); $_SESSION = $old_session ; //... ?> Note: this technique will send 3 Set-Cookie headers (one on each session_start() and one on session_regenerate_id()). I don't think this is a problem, but if it appears to be one, you could either leave it alone and wait for the garbage collector to catch the file associated with the old session, or try to delete the file with unlink(). up down 1 soapergem at gmail dot com ¶ 17 years ago This can be a very dangerous function if you're not careful about how you handle things, because even though it generates a whole new set of session data, it keeps the old data "open" until the script terminates, locking out any other scripts trying to run concurrently with the old session id. Recently I came across a situation where I wanted to explicitly pass in a session ID, copy the data from that session into a *new* session, and then continue operating under that new session, thereby allowing other scripts to use the old one concurrently. But I quickly found that these "other scripts" would not execute until the first script finished--even though it had already started a new session--because it kept the old session open. So if you're trying to copy over session data to a new session to free up the old session for continued, concurrent use, here's some code to ensure nobody's feet get stepped on: <?php // get session id of an existing session $sid = $_GET [ 'sid' ]; // start the old session to retrieve $_SESSION data session_id ( $sid ); session_start (); // start a new session; this copies the $_SESSION data over session_regenerate_id (); // hang on to the new session id $sid = session_id (); // close the old and new sessions session_write_close (); // re-open the new session session_id ( $sid ); session_start (); /* main code here */ ?> This could probably be encapsulated into a function with one parameter as well to save space if it was a repeated thing. up down 0 primenetworkzx at gmail dot com ¶ 17 years ago If you are storing your session data in a database you have to manually update the session_id in the database. The session_set_save_handler() will not do it for you. function UpdateSessID() { $old_sess_id = session_id(); session_regenerate_id(false); $new_sess_id = session_id(); $query = "UPDATE `session_table` SET `session_id` = '$new_sess_id' WHERE session_id = '$old_sess_id'"; mysql_query($query); } Be sure to set session_regenerate_id() to FALSE since it's not really necessary to delete the whole record from MySQL and add it again. That's unnecessary overhead. Only changing the id matters. up down 0 dyer85 at gmail dot com ¶ 20 years ago There could be a potential problem with elger at NOSPAM dot yellowbee dot nl's a few posts below. In the code, was used the REQUEST_URI server variable, which, in some cases might already contain the query string. Therefore, always apending '?whatever=foo' would occasionally cause the script to malfunction. I suggest using PHP_SELF, which will not contain the query string after the file. up down -2 mikebranttx at gmail dot com ¶ 8 years ago Note that in current PHP 7.2 nightly builds example #2 above will not work as shown. You will get following error upon trying to turn strict mode back on after session_start(): "ini_set(): A session is active. You cannot change the session module's ini settings at this time" I suppose this means that for any session where you perform session ID regeneration or session ID forwarding (from a session for which a recent session ID regeneration was performed to the new session ID). That you will just have to live with strict mode being disabled for the remainder of that active session. I don't know that this is really a security concern so long as you are following a single-session per request design (i.e. you are not working with multiple concurrent sessions). up down -2 chris at knowledge dot tee-vee ¶ 20 years ago licp - no, session_regenerate_id() does not destroy any saved session data. elger, I prefer the following order [code] // populate $_SESSION with any previously saved session data for the current session_id session_start(); ... // delete any saved data associated with current session_id, $_SESSION is not changed session_destroy(); // change session_id, $_SESSION not altered session_regenerate_id(); ... // save any $_SESSION data under the current session_id session_close(); [/code] up down -1 antomsa at hotmail dot it ¶ 4 years ago <?php function my_session_regenerate_id () { ... session_start (); ... unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Within my_session_regenerate_id(), unset($_SESSION['destroyed']) and unset($_SESSION['new_session_id']) are useless because session_start() will open an empty session. They would be needed if built-in session_regenerate_id() was called. up down -4 kgm_india at yahoo dot co dot in ¶ 12 years ago as far as I have understood reading this online notes, session_name() is the name which is identified as session a through the cookies or http links. session_id is like a transaction within a session_name() and one session_name may have many session_id each session_id has the corresponding data stored. session_id are used in read and write callback under a session_name whatever it is, first call the session_name(), then call session_id () and then call start_session() start_session will open the session_name, then check the session_id called before and use it in the read or write call back for storing or retrieving data calling start_session() without session_name or session_id will use the default session_name and the default session_id in that order I hope if the order is followed there should not be any problems. do not call session_name or session_id after start_session(), if you are specific on using them. thank you for others note. up down -5 raido dot aasoja at gmail dot com ¶ 15 years ago A note on lost sessions and trying to fix it with session_regenerate_id: Make sure that you're not trying to push SimpleXML object to the session. It just won't go without first converting it to array. :) up down -3 sopel ¶ 20 years ago for php 5.1> user probably worth visiting is http://ilia.ws/archives/47-session_regenerate_id-Improvement.html up down -4 Alamin ¶ 7 years ago In the second example provided by php.net, should it call my_session_start inside the session regenerate method instead of directly calling session_start? I think it is an error. ＋ add a note Session Funzioni session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://support.microsoft.com/nb-no/windows/behandle-informasjonskapsler-i-microsoft-edge-vise-tillate-blokkere-slette-og-bruke-168dab11-0753-043d-7c16-ede5947fc64d | Behandle informasjonskapsler i Microsoft Edge: Vise, tillate, blokkere, slette og bruke - Støtte for Microsoft Relaterte emner × Windows Sikkerhet, trygghet og personvern Oversikt Oversikt over sikkerhet, trygghet og personvern Windows Sikkerhet Få hjelp med Windows Sikkerhet Hold deg beskyttet med Windows Sikkerhet Før du gjenvinner, selger eller gir Windows-PC-en eller Xbox-en i gave Fjerne skadelig programvare fra Windows-PC-en Windows Sikkerhet Få hjelp med Windows Sikkerhet Vise og slette nettleserloggen i Microsoft Edge Slette og administrere informasjonskapsler Fjern verdifullt innhold på en trygg måte når du installerer Windows på nytt Finne og låse en mistet Windows-enhet Personvern for Windows Få hjelp med personvern for Windows Personverninnstillinger for Windows som apper bruker Se opplysningene dine på instrumentbordet for personvern Gå til hovedinnhold Microsoft Støtte Støtte Støtte Hjem Microsoft 365 Office Produkter Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mer... Enheter Surface PC-tilbehør Xbox PC-spill HoloLens Surface Hub Maskinvaregaranti Konto & fakturering Konto Microsoft Store og fakturering Ressurser Nyheter Fellesskapsforum Microsoft 365-administratorer Portal for små bedrifter Utvikler Utdanning Rapporter en kundestøttesvindel Produktsikkerhet Mer Kjøp Microsoft 365 Alt fra Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Spesialtilbud Liten bedrift Kundestøtte Programvare Programvare Windows-apper AI OneDrive Outlook Overgang fra Skype til Teams OneNote Microsoft Teams PCer og enheter PCer og enheter Kjøp Xbox Tilbehør Underholdning Underholdning Xbox Game Pass Ultimate Xbox og spill PC-spill Bedrift Bedrift Microsoft Sikkerhet Azure Dynamics 365 Microsoft 365 for bedrifter Microsoft Industry Microsoft Power Platform Windows 365 Utvikler og IT Utvikler og IT Microsoft Developer Microsoft Learn Støtte for KI-apper på markedsplassen Microsoft Tech-fellesskap Microsoft Marketplace Visual Studio Marketplace Rewards Annen Annen Microsoft Rewards Gratis nedlastinger og sikkerhet Utdanning Gavekort Lisensiering Vis områdekart Søk Søk etter hjelp Ingen resultater Avbryt Logg på Logg på med Microsoft Logg på, eller opprett en konto. Hei, Velg en annen konto. Du har flere kontoer Velg kontoen du vil logge på med. Relaterte emner Windows Sikkerhet, trygghet og personvern Oversikt Oversikt over sikkerhet, trygghet og personvern Windows Sikkerhet Få hjelp med Windows Sikkerhet Hold deg beskyttet med Windows Sikkerhet Før du gjenvinner, selger eller gir Windows-PC-en eller Xbox-en i gave Fjerne skadelig programvare fra Windows-PC-en Windows Sikkerhet Få hjelp med Windows Sikkerhet Vise og slette nettleserloggen i Microsoft Edge Slette og administrere informasjonskapsler Fjern verdifullt innhold på en trygg måte når du installerer Windows på nytt Finne og låse en mistet Windows-enhet Personvern for Windows Få hjelp med personvern for Windows Personverninnstillinger for Windows som apper bruker Se opplysningene dine på instrumentbordet for personvern Behandle informasjonskapsler i Microsoft Edge: Vise, tillate, blokkere, slette og bruke Gjelder for Windows 10 Windows 11 Microsoft Edge Informasjonskapsler er små datadeler som lagres på enheten av nettsteder du besøker. De tjener ulike formål, for eksempel å huske påloggingslegitimasjon, områdeinnstillinger og sporing av brukeratferd. Det kan imidlertid hende du vil slette informasjonskapsler av personvernhensyn eller for å løse problemer med nettlesing. Denne artikkelen inneholder instruksjoner om hvordan du gjør følgende: Vis alle informasjonskapsler Tillat alle informasjonskapsler Tillat informasjonskapsler fra et bestemt nettsted Blokker informasjonskapsler fra tredjeparter Blokker alle informasjonskapsler Blokkere informasjonskapsler fra et bestemt nettsted Slett alle informasjonskapsler Slett informasjonskapsler fra et bestemt nettsted Slette informasjonskapsler hver gang du lukker nettleseren Bruke informasjonskapsler til å forhåndslaste siden for raskere nettlesing Vis alle informasjonskapsler Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > Personvern, søk og tjenester . Velg Informasjonskapsler , og klikk deretter Se alle informasjonskapsler og områdedata for å vise alle lagrede informasjonskapsler og relatert områdeinformasjon. Tillat alle informasjonskapsler Ved å tillate informasjonskapsler kan nettsteder lagre og hente data i nettleseren, noe som kan forbedre nettleseropplevelsen ved å huske innstillingene og påloggingsinformasjonen. Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > personvern, søk og tjenester . Velg Informasjonskapsler, og aktiver veksleknappen Tillat områder å lagre og lese informasjonskapseldata (anbefales) for å tillate alle informasjonskapsler. Tillat informasjonskapsler fra et bestemt nettsted Ved å tillate informasjonskapsler kan nettsteder lagre og hente data i nettleseren, noe som kan forbedre nettleseropplevelsen ved å huske innstillingene og påloggingsinformasjonen. Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > Personvern, søk og tjenester . Velg Informasjonskapsler , og gå til Tillat å lagre informasjonskapsler. Velg Legg til område for å tillate informasjonskapsler per område ved å skrive inn nettadressen for området. Blokker informasjonskapsler fra tredjeparter Hvis du ikke vil at tredjepartsnettsteder skal lagre informasjonskapsler på PC-en, kan du blokkere informasjonskapsler. Men når du gjør dette, kan det imidlertid hende at enkelte sider ikke vises på riktig måte, eller du kan få en melding fra et nettsted om at du må tillate informasjonskapsler for å vise nettstedet. Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > personvern, søk og tjenester . Velg Informasjonskapsler , og aktiver veksleknappen Blokker informasjonskapsler fra tredjeparter. Blokker alle informasjonskapsler Hvis du ikke vil at tredjepartsnettsteder skal lagre informasjonskapsler på PC-en, kan du blokkere informasjonskapsler. Men når du gjør dette, kan det imidlertid hende at enkelte sider ikke vises på riktig måte, eller du kan få en melding fra et nettsted om at du må tillate informasjonskapsler for å vise nettstedet. Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > Personvern, søk og tjenester . Velg Informasjonskapsler , og deaktiver Tillat områder å lagre og lese informasjonskapseldata (anbefales) for å blokkere alle informasjonskapsler. Blokkere informasjonskapsler fra et bestemt nettsted Microsoft Edge lar deg blokkere informasjonskapsler fra et bestemt nettsted, men dette kan hindre at enkelte sider vises riktig, eller du kan få en melding fra et nettsted som forteller deg at du må tillate informasjonskapsler for å vise dette nettstedet. Slik blokkerer du informasjonskapsler fra et bestemt område: Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > Personvern, søk og tjenester . Velg Informasjonskapsler , og gå til Ikke tillatt å lagre og lese informasjonskapseler . Velg Legg til område for å blokkere informasjonskapsler per område ved å skrive inn nettadressen for området. Slett alle informasjonskapsler Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > Personvern, søk og tjenester . Velg Fjern nettleserdata , og velg deretter Velg hva du vil fjerne ved siden av Fjern nettleserdata nå . Velg et tidsintervall fra listen under Tidsintervall . Velg informasjonskapsler og andre nettstedsdata , og velg deretter Slett nå . Obs!: Alternativt kan du slette informasjonskapslene ved å trykke CTRL + SKIFT + DELETE sammen og deretter fortsette med trinn 4 og 5. Alle informasjonskapsler og andre nettstedsdata slettes nå for tidsintervallet du valgte. Dette logger deg av de fleste nettsteder. Slett informasjonskapsler fra et bestemt nettsted Åpne Edge-nettleseren, velg Innstillinger og mer > Innstillinger > Personvern, søk og tjenester . Velg Informasjonskapsler , klikk deretter Vis alle informasjonskapsler og nettstedsdata , og søk etter området du vil slette informasjonskapsler for. Velg pil ned til høyre for nettstedet med informasjonskapsler du vil slette, og velg Slett . Informasjonskapsler for området du valgte, slettes nå. Gjenta dette trinnet for alle nettsteder med informasjonskapsler du vil slette. Slette informasjonskapsler hver gang du lukker nettleseren Åpne Edge-nettleseren, velg Innstillinger og mer > Innstillinger > personvern, søk og tjenester . Velg Fjern nettleserdata , og velg deretter Velg hva du vil fjerne hver gang du lukker nettleseren . Aktiver veksleknappen for Informasjonskapsler og andre nettstedsdata . Når denne funksjonen er aktivert, slettes alle informasjonskapsler og andre nettstedsdata hver gang du lukker Edge-nettleseren. Dette logger deg av de fleste nettsteder. Bruke informasjonskapsler til å forhåndslaste siden for raskere nettlesing Åpne Edge-nettleseren, velg Innstillinger og mer øverst til høyre i nettleservinduet. Velg Innstillinger > Personvern, søk og tjenester . Velg Informasjonskapsler , og aktiver vekslesidene for forhåndslasting for raskere nettlesing og søking. ABONNER PÅ RSS-FEEDER Trenger du mer hjelp? Vil du ha flere alternativer? Oppdag Community Kontakt oss Utforsk abonnementsfordeler, bla gjennom opplæringskurs, finn ut hvordan du sikrer enheten og mer. Abonnementsfordeler for Microsoft 365 Microsoft 365-opplæring Microsoft Sikkerhet Tilgjengelighetssenter Fellesskap hjelper deg med å stille og svare på spørsmål, gi tilbakemelding og høre fra eksperter med stor kunnskap. Spør Microsoft-fellesskapet Teknisk fellesskap for Microsoft Windows Insider-medlemmer Microsoft 365 Insiders Finn løsninger på vanlige problemer, eller få hjelp fra en kundestøtterepresentant. Nettbasert støtte Var denne informasjonen nyttig? Ja Nei Takk! Har du flere tilbakemeldinger til Microsoft? Kan du hjelpe oss med å bli bedre? (Send tilbakemelding til Microsoft, slik at vi kan hjelpe deg.) Hvor fornøyd er du med språkkvaliteten? Hva påvirket opplevelsen din? Løste problemet mitt Tydelige instruksjoner Enkelt å følge Ingen sjargong Bilder hjalp Oversettelseskvalitet Samsvarte ikke med skjermen min Feil instruksjoner For teknisk Ikke nok informasjon Ikke nok bilder Oversettelseskvalitet Har du ytterligere tilbakemeldinger? (Valgfritt) Send tilbakemelding Når du trykker på Send inn, blir tilbakemeldingen brukt til å forbedre Microsoft-produkter og -tjenester. IT-administratoren kan samle inn disse dataene. Personvernerklæring. Takk for tilbakemeldingen! × Nyheter Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organisasjoner Copilot til personlig bruk Microsoft 365 Utforsk Microsoft-produkter Windows 11-apper Microsoft Store Kontoprofil Nedlastingssenter Kundestøtte for Microsoft Store Returer Ordresporing Gjenvinning Kommersielle garantier Utdanning Microsoft Education Enheter for utdanning Microsoft Teams for utdanning Microsoft 365 Education Office Education Lærerutdanning og -utvikling Tilbud for elever og foreldre Azure for students Bedrift Microsoft Sikkerhet Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Liten bedrift Utvikler og IT Microsoft Developer Microsoft Learn Støtte for KI-apper på markedsplassen Microsoft Tech-fellesskap Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Selskap Karriere Om Microsoft Microsoft og personvern Investorer Bærekraft Norsk bokmål (Norge) Ikon for å velge bort personvernvalg Dine personvernvalg Ikon for å velge bort personvernvalg Dine personvernvalg Personvern for forbrukerhelse Kontakt Microsoft Personvern Behandle informasjonskapsler Vilkår for bruk Varemerker Om annonsene © Microsoft 2026 | 2026-01-13T09:30:34 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1KY84hKm_-by-YRr4vpnWKQpQpwSlqcHtHuJaVKw1bW8wItTohGpLUCnyGOFaKEl24B0RlP8zqhkc8lgjUOBrHeD_3-x2x1wAeaDTMaMg12_UywdHBUwoulr3RtwamghKKTr5Z0_NPtXeL | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/tools/clang/tools/extra/docs/index.html | Welcome to Extra Clang Tools's documentation! — Extra Clang Tools 18.1.8 documentation Extra Clang Tools 18.1.8 documentation Welcome to Extra Clang Tools's documentation! Contents   ::   Extra Clang Tools 18.1.8 Release Notes   » Introduction ¶ Welcome to the clang-tools-extra project which contains extra tools built using Clang’s tooling APIs. Extra Clang Tools 18.1.8 Release Notes Contents ¶ Clang-Tidy The list of clang-tidy checks Clang-tidy IDE/Editor Integrations Getting Involved Using clang-tidy Suppressing Undesired Diagnostics Clang-Include-Fixer Setup How it Works Modularize User’s Manual Getting Started What Modularize Checks Module Map Coverage Check Module Map Generation pp-trace User’s Manual pp-trace Usage pp-trace Output Format Building pp-trace Clang-Rename Using Clang-Rename Vim Integration Emacs Integration clangd Clang-Doc Use Output Configuration Doxygen Documentation ¶ The Doxygen documentation describes the internal software that makes up the tools of clang-tools-extra, not the external use of these tools. The Doxygen documentation contains no instructions about how to use the tools, only the APIs that make up the software. For usage instructions, please see the user’s guide or reference manual for each tool. Doxygen documentation Note This documentation is generated directly from the source code with doxygen. Since the tools of clang-tools-extra are constantly under active development, what you’re about to read is out of date! Indices and tables ¶ Index Search Page Contents   ::   Extra Clang Tools 18.1.8 Release Notes   » © Copyright 2007-2024, The Clang Team. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://support.microsoft.com/pl-pl/microsoft-edge/program-microsoft-edge-i-przegl%C4%85danie-danych-a-prywatno%C5%9B%C4%87-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Program Microsoft Edge i przeglądanie danych a prywatność - Pomoc techniczna firmy Microsoft Przejdź do głównej zawartości Microsoft Pomoc techniczna Pomoc techniczna Pomoc techniczna Strona główna Microsoft 365 Office Produkty Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows więcej... Urządzenia Surface Akcesoria komputerowe Xbox Gry komputerowe HoloLens Surface Hub Gwarancje sprzętowe Konto i rozliczenia klient Sklep Microsoft Store & rozliczenia Zasoby Co nowego Fora społeczności Administratorzy platformy Microsoft 365 Portal dla małych firm Deweloper Edukacja Zgłoś oszustwo związane z pomocą techniczną Bezpieczeństwo produktu Więcej Kup platformę Microsoft 365 Wszystkie produkty Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Promocje i zniżki Pomoc techniczna Oprogramowanie Oprogramowanie Aplikacje systemu Windows AI OneDrive Outlook Przejście ze Skype do Teams OneNote Microsoft Teams Komputery i urządzenia Komputery i urządzenia Kup Xbox Akcesoria Rozrywka Rozrywka Xbox Game Pass Ultimate Xbox i gry Gry PC Sklep dla firm Sklep dla firm Rozwiązania zabezpieczające firmy Microsoft Azure Dynamics 365 Microsoft 365 dla firm Rozwiązania Microsoft dla przedsiębiorstw Microsoft Power Platform Windows 365 Dla programistów i specjalistów IT Dla programistów i specjalistów IT Deweloper Microsoft Microsoft Learn Pomoc techniczna do aplikacji z platformy handlowej opartych na AI Społeczność Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards Inny Inny Bezpłatne pliki do pobrania i zabezpieczenia Edukacja Bony upominkowe Licencjonowanie Wyświetl mapę witryny Wyszukaj Wyszukaj, aby uzyskać pomoc Brak wyników Anuluj Zaloguj się Zaloguj się przy użyciu konta Microsoft Zaloguj się lub utwórz konto. Witaj, Wybierz inne konto. Masz wiele kont Wybierz konto, za pomocą którego chcesz się zalogować. Program Microsoft Edge i przeglądanie danych a prywatność Dotyczy Privacy Microsoft Edge Windows 10 Windows 11 Przeglądarka Microsoft Edge ułatwia przeglądanie, wyszukiwanie, robienie zakupów online i nie tylko. Jak wszystkie nowoczesne przeglądarki, program Microsoft Edge umożliwia zbieranie i przechowywanie danych na Twoim urządzeniu, takich jak pliki cookie, oraz wysyłanie informacji do firmy Microsoft, takich jak historia przeglądania, aby program był tak bogaty w funkcje, szybki i spersonalizowany, jak to tylko możliwe. Zawsze, gdy zbieramy dane, chcemy mieć pewność, że jest to właściwy wybór dla Ciebie. Niektóre osoby niepokoi fakt zbierania historii przeglądania Internetu. Dlatego informujemy Cię, jakie dane są przechowywane na Twoim urządzeniu lub które są przez nas zbierane. Dajemy Ci możliwość kontrolowania, które dane są zbierane. Aby uzyskać więcej informacji na temat prywatności w programie Microsoft Edge, radzimy zapoznać się z Oświadczeniem o ochronie prywatności . Jakie dane są zbierane lub przechowywane i dlaczego Firma Microsoft używa danych diagnostycznych do ulepszania produktów i usług. Korzystamy z tych danych, aby lepiej zrozumieć, jak działają nasze produkty i gdzie należy wprowadzić ulepszenia. Przeglądarka Microsoft Edge zbiera zestaw wymaganych danych diagnostycznych, aby zapewnić bezpieczeństwo przeglądarki Microsoft Edge, jej aktualność i działanie zgodnie z oczekiwaniami. Firma Microsoft wierzy w minimalizację zakresu gromadzonych informacji i stosuje ją w praktyce. Dokładamy wszelkich starań, aby zbierać tylko te informacje, których potrzebujemy, i przechowywać je tylko tak długo, jak jest to potrzebne do świadczenia usługi lub analizy. Ponadto możesz kontrolować, czy opcjonalne dane diagnostyczne skojarzone z urządzeniem są udostępniane firmie Microsoft w celu rozwiązywania problemów z produktem i ulepszania produktów i usług Microsoft. Podczas korzystania z funkcji i usług w programie Microsoft Edge dane diagnostyczne dotyczące sposobu korzystania z tych funkcji są wysyłane do firmy Microsoft. Przeglądarka Microsoft Edge zapisuje na urządzeniu historię przeglądania — informacje na temat odwiedzanych witryn internetowych. W zależności od ustawień ta historia przeglądania jest wysyłana do firmy Microsoft, co ułatwia nam znajdowanie i rozwiązywanie problemów oraz usprawnianie naszych produktów i usług dla wszystkich użytkowników. Możesz zarządzać gromadzeniem opcjonalnych danych diagnostycznych w przeglądarce, wybierając pozycję Ustawienia i nie tylko > Ustawienia > prywatność, wyszukiwanie i usługi > prywatność i włączając lub wyłączając pozycję Wysyłaj opcjonalne dane diagnostyczne w celu ulepszania produktów firmy Microsoft . Obejmuje to również dane dotyczące testowania nowych rozwiązań. Aby zakończyć wprowadzanie zmian tego ustawienia, uruchom ponownie program Microsoft Edge. Włączenie tego ustawienia umożliwi udostępnianie tych opcjonalnych danych diagnostycznych firmie Microsoft przez inne aplikacje używające przeglądarki Microsoft Edge, takie jak aplikacje do przesyłania strumieniowego wideo hostujące platformę internetową Microsoft Edge w celu strumieniowego przesyłania wideo. Ta platforma internetowa Microsoft Edge będzie wysyłać do firmy Microsoft informacje dotyczące sposobu używania platformy internetowej przez Ciebie i odwiedzane witryny w aplikacji. To gromadzenie danych jest określane przez ustawienie opcjonalnych danych diagnostycznych w ustawieniach prywatności, wyszukiwania i usług w przeglądarce Microsoft Edge. W przypadku systemu Windows 10 te ustawienia są wyznaczane na podstawie ustawień danych diagnostycznych systemu Windows. Aby zmienić ustawienie danych diagnostycznych, wybierz pozycję Rozpocznij > Ustawienia > opinię dotyczącą prywatności> diagnostyki & . Od 6 marca 2024 r. dane diagnostyczne przeglądarki Microsoft Edge są zbierane oddzielnie od danych diagnostycznych systemu Windows na urządzeniach z systemem Windows 10 (wersja 22H2 i nowsza) oraz urządzeniach Windows 11 (wersja 23H2 i nowsze) w Europejskim Obszarze Ekonomicznym. W tych wersjach systemu Windows i na wszystkich innych platformach możesz zmienić ustawienia w programie Microsoft Edge, wybierając pozycję Ustawienia i nie tylko > Ustawienia > Prywatność, wyszukiwanie i usługi . W niektórych przypadkach ustawienia danych diagnostycznych mogą być zarządzane przez organizację. Podczas wyszukiwania czegoś przeglądarka Microsoft Edge może przekazywać sugestie dotyczące tego, czego szukasz. Aby włączyć tę funkcję, wybierz pozycję Ustawienia i nie tylko > Ustawienia > Prywatność, wyszukiwanie i usługi > Wyszukiwanie i połączone środowiska > pasek adresu i wyszukiwanie > Sugestie i filtry wyszukiwania oraz włącz opcję Pokazuj sugestie wyszukiwania i witryn przy użyciu wpisanych przeze mnie znaków . W momencie rozpoczęcia pisania informacje wprowadzane w pasku adresu będą wysyłane do domyślnego dostawcy wyszukiwania, aby zapewnić Ci natychmiastowe sugestie wyszukiwania i sugerowane witryny internetowe. Podczas korzystania z trybu przeglądania InPrivate lub trybu gościa przeglądarka Microsoft Edge zbiera pewne informacje na temat sposobu korzystania z przeglądarki w zależności od ustawień danych diagnostycznych systemu Windows lub ustawień prywatności przeglądarki Microsoft Edge, ale automatyczne sugestie są wyłączone, a informacje o odwiedzanych witrynach internetowych nie są zbierane. W momencie zamknięcia wszystkich okien InPrivate program Microsoft Edge usunie Twoją historię przeglądania, pliki cookie, dane witryn, hasła, adresy i dane dotyczące formularzy. Nową sesję InPrivate możesz uruchomić, wybierając pozycję Ustawienia i nie tylko na komputerze lub pozycję Karty na urządzeniu mobilnym. Program Microsoft Edge zawiera również funkcje zwiększające bezpieczeństwo Twoje i Twojej zawartości w Internecie. Filtr Windows Defender SmartScreen automatycznie blokuje witryny internetowe i pobieraną zawartość, które są zgłaszane jako złośliwe. Windows Defender SmartScreen porównuje adres odwiedzanej strony internetowej z zapisaną na urządzeniu listą adresów stron internetowych uważanych przez firmę Microsoft za wiarygodne. Adresy, które nie znajdują się na liście na urządzeniu, oraz adresy pobieranych plików zostaną wysłane do firmy Microsoft i porównane z często aktualizowaną listą stron internetowych i plików do pobrania, które zostały zgłoszone firmie Microsoft jako niebezpieczne lub podejrzane. Aby przyspieszyć i ułatwić wykonywanie męczących zadań, takich jak wypełnianie formularzy czy wpisywanie haseł, program Microsoft Edge może zapisywać odpowiednie informacje. Jeśli zdecydujesz się na korzystanie z tych funkcji, program Microsoft Edge będzie przechowywał te informacje na Twoim urządzeniu. Jeśli włączono synchronizację na potrzeby wypełniania formularzy, takich jak adresy lub hasła, te informacje zostaną wysłane do chmury Firmy Microsoft i przechowywane razem z Twoim kontem Microsoft, aby były synchronizowane we wszystkich wersjach przeglądarki Microsoft Edge, do których się zalogowano. Możesz zarządzać tymi danymi z poziomu obszaru Ustawienia i innych > Ustawienia > Profile > Synchronizacja . Aby zintegrować środowisko przeglądania z innymi działaniami wykonywanymi na urządzeniu, przeglądarka Microsoft Edge udostępnia historię przeglądania w systemie Microsoft Windows za pośrednictwem indeksatora. Te informacje są przechowywane lokalnie na urządzeniu. Obejmuje ona adresy URL, kategorię, w której adres URL może być istotny, na przykład "najczęściej odwiedzane", "ostatnio odwiedzone" lub "ostatnio zamknięte", a także względną częstotliwość lub odwrotność w obrębie każdej kategorii. Witryny internetowe odwiedzane w trybie InPrivate nie będą udostępniane. Te informacje są następnie dostępne dla innych aplikacji na urządzeniu, takich jak menu Start lub pasek zadań. Możesz zarządzać tą funkcją, wybierając pozycję Ustawienia i nie tylko > Ustawienia > Profile i włączając lub wyłączając opcję Udostępnij dane przeglądania innym funkcjom systemu Windows. Jeśli ta opcja jest wyłączona, wszystkie udostępnione wcześniej dane zostaną usunięte. Aby zapobiec kopiowaniu niektórych materiałów muzycznych i wideo, niektóre witryny internetowe korzystające z przesyłania strumieniowego przechowują dane zarządzania prawami cyfrowymi (DRM) na Twoim urządzeniu, w tym unikatowe identyfikatory (ID) i licencje multimediów. Gdy przejdziesz do jednej z tych witryn internetowych, pobierze ona informacje DRM, aby upewnić się, że masz uprawnienia do korzystania z zawartości. Program Microsoft Edge również przechowuje pliki cookie, czyli niewielkie pliki zapisywane na urządzeniu podczas przeglądania Internetu. Wiele witryn internetowych korzysta z plików cookie do przechowywania informacji na temat Twoich preferencji i ustawień, takich jak elementy w koszyku zakupowym, aby nie trzeba było za każdym razem ich dodawać, gdy odwiedzasz witrynę. Niektóre witryny internetowe również korzystają z plików cookie do zbierania informacji na temat Twojej aktywności w Internecie, aby wyświetlać reklamy zgodne z Twoimi zainteresowaniami. W programie Microsoft Edge możesz wyczyścić pliki cookie i uniemożliwić witrynom internetowym zapisywanie plików cookie w przyszłości. Microsoft Edge będzie wysyłać żądania „Nie śledź” do witryn internetowych, kiedy ustawienie Wysyłaj żądania „Nie śledź” będzie włączone. To ustawienie jest dostępne na stronie Ustawienia i nie tylko > Ustawienia > Prywatność, wyszukiwanie i usługi > prywatność > Wysyłaj żądania "Nie śledź". Jednak mimo wysłania żądania „Nie śledź” witryny internetowe nadal będą mogły śledzić Twoją aktywność. Czyszczenie danych zebranych i przechowywanych przez program Microsoft Edge Aby wyczyścić przechowywane na urządzeniu informacje dotyczące przeglądania, takie jak zapisane hasła czy pliki cookie, wykonaj następujące czynności: W programie Microsoft Edge wybierz pozycję Ustawienia i nie tylko > Ustawienia > Prywatność, wyszukiwanie i usługi > Wyczyść dane przeglądania . Wybierz pozycję Wybierz elementy do wyczyszczenia obok pozycji Wyczyść dane przeglądania teraz. W obszarze Zakres czasu wybierz zakres czasu. Zaznacz pole wyboru obok każdego typu danych, które chcesz wyczyścić, a następnie wybierz pozycję Wyczyść teraz . Jeśli chcesz, możesz wybrać pozycję Wybierz elementy do wyczyszczenia przy każdym zamknięciu przeglądarki i wybrać typy danych, które mają zostać wyczyszczone. Dowiedz się więcej na temat tego, co jest usuwane wraz z każdym elementem historii przeglądarki . Aby wyczyścić historię przeglądania gromadzoną przez Microsoft: Aby zobaczyć historię przeglądania skojarzoną z Twoim kontem, zaloguj się do swojego konta na stronie account.microsoft.com . Ponadto dostępna jest również opcja wyczyszczenia danych przeglądania, które firma Microsoft zgromadziła za pomocą pulpitu nawigacyjnego prywatności Microsoft . Aby usunąć historię przeglądania i inne dane diagnostyczne skojarzone z urządzeniem Windows 10, wybierz pozycję Rozpocznij > Ustawienia > Prywatność > Diagnostyka & opinii , a następnie wybierz pozycję Usuń w obszarze Usuń dane diagnostyczne . Aby wyczyścić historię przeglądania udostępnioną innym funkcjom firmy Microsoft na urządzeniu lokalnym: W programie Microsoft Edge wybierz pozycję Ustawienia i nie tylko > Ustawienia > Profile . Wybierz pozycję Udostępnij dane przeglądania innym funkcjom systemu Windows . Przełącz to ustawienie na wyłączone . Jak zarządzać ustawieniami prywatności w programie Microsoft Edge Aby przejrzeć i dostosować ustawienia prywatności, wybierz pozycję Ustawienia i nie tylko > Ustawienia > Prywatność, wyszukiwanie i usługi . > Prywatność. Aby dowiedzieć się więcej na temat ochrony prywatności w programie Microsoft Edge, przeczytaj oficjalny dokument dotyczący ochrony prywatności w programie Microsoft Edge . ZASUBSKRYBUJ KANAŁY INFORMACYJNE RSS Potrzebujesz dalszej pomocy? Chcesz uzyskać więcej opcji? Odkryj Społeczność Skontaktuj się z nami Poznaj korzyści z subskrypcji, przeglądaj kursy szkoleniowe, dowiedz się, jak zabezpieczyć urządzenie i nie tylko. Korzyści z subskrypcji platformy Microsoft 365 Szkolenia dotyczące platformy Microsoft 365 Rozwiązania dotyczące zabezpieczeń firmy Microsoft Centrum ułatwień dostępu Społeczności pomagają zadawać i odpowiadać na pytania, przekazywać opinie i słuchać ekspertów z bogatą wiedzą. Zapytaj społeczność firmy Microsoft Społeczność techniczna firmy Microsoft Niejawny program testów systemu Windows Microsoft 365 Insiders Znajdź rozwiązania typowych problemów lub uzyskaj pomoc od agenta pomocy technicznej. Pomoc techniczna online Czy te informacje były pomocne? Tak Nie Dziękujemy! Chcesz przekazać więcej opinii firmie Microsoft? Czy możesz nam pomóc w ulepszaniu? (Wysyłanie opinii do firmy Microsoft, abyśmy mogli zapewnić pomoc.) Jaka jest jakość języka? Co wpłynęło na Twoje wrażenia? Rozwiązał mój problem Zrozumiałe instrukcje Łatwy do zrozumienia Brak żargonu Pomocne ilustracje Jakość tłumaczenia Niedopasowane do mojego ekranu Niepoprawne instrukcje Zbyt techniczne Za mało informacji Za mało ilustracji Jakość tłumaczenia Czy chcesz przekazać jakieś inne uwagi? (Opcjonalnie) Prześlij opinię Jeśli naciśniesz pozycję „Wyślij”, Twoja opinia zostanie użyta do ulepszania produktów i usług firmy Microsoft. Twój administrator IT będzie mógł gromadzić te dane. Oświadczenie o ochronie prywatności. Dziękujemy za opinię! × Co nowego Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot dla organizacji Copilot do użytku osobistego Microsoft 365 Poznaj produkty Microsoft Microsoft Store Profil konta Centrum pobierania Pomoc techniczna Microsoft Store Zwroty Śledzenie zamówienia Recykling Gwarancje handlowe Edukacja Microsoft Education Urządzenia dla instytucji edukacyjnych Microsoft Teams dla Instytucji Edukacyjnych Microsoft 365 Education Office Education Szkolenia i możliwości rozwoju dla nauczycieli Oferty dla uczniów i rodziców Azure dla uczniów Dla firm Rozwiązania zabezpieczające firmy Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Dla programistów i specjalistów IT Deweloper Microsoft Microsoft Learn Pomoc techniczna do aplikacji z platformy handlowej opartych na AI Społeczność Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Firma Praca Informacje o firmie Microsoft Aktualności Ochrona prywatności Inwestorzy Zrównoważony rozwój Polski (Polska) Ikona rezygnacji z opcji prywatności Twoje opcje wyboru dotyczące prywatności Ikona rezygnacji z opcji prywatności Twoje opcje wyboru dotyczące prywatności Zasady prywatności dotyczące zdrowia użytkowników Skontaktuj się z Microsoft Ochrona prywatności Zarządzaj plikami cookie Zasady użytkowania Znaki towarowe Informacje o naszych reklamach EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://penneo.com/da/use-cases/automation-signing-processes/ | Automatisér komplekse underskriftsprocesser - Penneo Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Brancher Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus LOG PÅ Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ BOOK ET MØDE GRATIS PRØVEPERIODE DA EN NO FR NL Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus BOOK ET MØDE GRATIS PRØVEPERIODE LOG PÅ DA EN NO FR NL Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ Automatisér komplekse underskriftsprocesser Gør arbejdet lettere og hurtigere ved at automatisere selv de mest komplekse dokumentflows . Vores løsning bliver nemt integreret med dine eksisterende systemer, så du kan gennemføre dit arbejde hurtigere, eliminere manuel indtastning af data og minimere administrativt arbejde. BOOK ET MØDE Hvorfor vælge Penneo? Hurtigere underskriftsprocesser, mindre manuelt arbejde Integrér Penneo med dine eksisterende systemer Brug vores åbne API til at integrere Penneo direkte med dine nuværende systemer og effektivisér dine underskriftsflows. Du slipper for at skifte mellem forskellige systemer og minimer den manuelle indtastning af data — det sparer tid og øger effektiviteten. Automatisér komplekse underskriftsprocesser fra start til slut Penneo sørger automatisk for, at dokumenter sendes til de rette personer i den rigtige rækkefølge . Der er ingen begrænsninger på antallet af underskrivere, dokumenter eller underskriftsrunder. Bevar overblikket over tidsfrister og følg fremdriften i realtid Hold dine workflows i gang med automatiske e-mailpåmindelser og opdateringer i realtid om dokumentstatus — så slipper du for manuelle opfølgninger. 3.000+ virksomheder – herunder de fire største revisionshuse – bruger Penneo. 60 % af alle dokumenter, der sendes via Penneo, bliver underskrevet inden for 24 timer. 81 % af alle årsrapporter i Danmark bliver underskrevet med Penneo. Hvordan automatiserer Penneo underskriftsprocesser? Penneo automatiserer dine underskriftsprocesser ved hjælp af såkaldte underskriftsflows. Her defineres rollerne for de enkelte underskrivere, hvilke dokumenter de skal skrive under på, samt rækkefølgen for, hvornår og hvordan underskrifterne skal indhentes . Det sikrer, at alle dokumenter bliver underskrevet i den korrekte rækkefølge — helt uden manuel indgriben. Selv de mest komplekse processer kan automatiseres med Penneo. Det gælder fx underskrivelse af årsrapporter, som ofte involverer flere underskrivere, flere dokumenter og flere underskriftsrunder. Med Penneo kan du sætte hele processen op én gang og lade systemet klare resten. Læs mere Se, hvorfor dokumenter bliver underskrevet på under 24 timer med Penneo Underskriv selv et testdokument. Oplev hvor nemt det er og se, hvorfor det hjælper dine underskrivere med at færdiggøre dokumenter hurtigere. Company Dette felt er til validering og bør ikke ændres. E-mail * Jeg vil gerne modtage nyheder om Penneo og dets produkter. Jeg kan til enhver tid afmelde mig. Dette felt er skjult, når du får vist formularen Country Åland Islands Albania Andorra Australia Austria Belarus Belgium Bosnia and Herzegovina Bulgaria Canada China Croatia Cyprus Czech Republic Denmark Estonia Faroe Islands Finland France Georgia Germany Greece Greenland Hong Kong Hungary Iceland India Indonesia Ireland Isle of Man Israel Italy Japan Latvia Liechtenstein Lithuania Luxembourg Macau Macedonia Moldova Monaco Montenegro Netherlands New Zealand Norway Poland Portugal Romania Russia San Marino Serbia Singapore Slovakia Slovenia Spain Sweden Switzerland Taiwan Turkey Ukraine United Kingdom United States Land Skabt til selv de mest komplekse underskriftsprocesser Uanset om du arbejder med revision, regnskab, ejendomshandel, finans eller HR, gør Penneo det nemt og sikkert for dit team at håndtere underskrifter digitalt. Platformen er udviklet til at automatisere selv de mest komplekse forløb, så I kan fokusere på det, der virkelig tæller. Revision og regnskab Send aftalebreve, revisionspåtegninger og årsrapporter til underskrift med få klik. Læs mere Ejendomshandel Gør ejendomshandler hurtigere og nemmere ved at fjerne behovet for fysiske møder og papirarbejde. Læs mere Juridisk sektor Lad dine klienter underskrive dokumenter på afstand med sikre digitale signaturer, der overholder eIDAS-forordningen. Læs mere Finans og bank Reducer papirarbejde og manuelle processer – uden at gå på kompromis med en smidig og professionel kundeoplevelse. Læs mere HR og rekruttering Forkort ansættelsesprocessen ved at sende ansættelseskontrakter til digital underskrift på få minutter. Læs mere Arbejd hurtigere med integrationer og åben API Forbind dine systemer på få minutter. Med vores integrationer og åbne API kan du automatisere arbejdsgange og få mere fra hånden. Få overblik over alle integrationer Agri Nord sparer tid og ressourcer med digital underskrift fra Penneo Der er ofte flere personer, der skal underskrive dokumenter i en bestemt rækkefølge. Rækkefølgen og underskriverne varierer fra dokument til dokument. Penneos digitale underskriftssystem giver os mulighed for at automatisere underskriftsrækkefølgen og sparer os for det manuelle arbejde. — Anders Hummelmose, Økonomi- og IT-chef hos Agri Nord Læs mere om samarbejdet Ofte stillede spørgsmål Hvad er underskriftsflows i Penneo? I Penneo bruges underskriftsflows til at styre rækkefølgen, dokumenter bliver underskrevet i. Det gør det muligt at automatisere selv komplekse forløb med flere dokumenter, modtagere og underskriftsrunder. Med underskriftsflows sikrer du, at alle parter underskriver i den rigtige rækkefølge – helt automatisk og uden manuel opfølgning. Læs mere om, hvordan underskriftsflows fungerer Hvilke systemer kan Penneo integreres med? Penneo kan integreres med en lang række værktøjer som fx Instaclause, CaseWare, Silverfin, M-Files og AdminPulse. Derudover har du mulighed for at bygge dine egne integrationer til eksisterende systemer ved hjælp af Penneos åbne API. Se den fulde liste over integrationer her Er digitale signaturer oprettet via Penneo juridisk bindende? Ja, digitale signaturer oprettet via Penneo er juridisk bindende. Penneo understøtter både avancerede elektroniske signaturer (AdES) og kvalificerede elektroniske signaturer (QES) i overensstemmelse med eIDAS-forordningen (EU nr. 910/2014). Kan jeg planlægge automatisk sletning af dokumenter i Penneo? Ja, i Penneo kan du aktivere funktionen Automatisk databehandling for automatisk at få slettet sager efter en bestemt periode. Det hjælper dig med at overholde GDPR og sikre, at personoplysninger ikke opbevares længere end nødvendigt. Læs mere om automatisk datasletning her Tilbyder Penneo kvalificerede elektroniske signaturer (QES)? Ja, Penneo tilbyder kvalificerede elektroniske signaturer via pas, norsk BankID, itsme® og. beID . Disse signaturer har samme retsgyldighed som en håndskrevet underskrift i hele EU. Tilbyder Penneo avancerede elektroniske signaturer (AdES)? Ja, Penneo gør det muligt at oprette avancerede elektroniske signaturer med MitID, MitID Erhverv og svensk BankID . Disse signaturer er unikt knyttet til underskriveren og beskytter dokumentet mod ændringer. Hvordan sikrer jeg, at en digital signatur er gyldig? Du kan verificere en digital signaturs gyldighed på flere måder: Åbn dokumentet i en PDF-læser og brug det indbyggede valideringsværktøj Upload dokumentet til Penneo Validator Upload dokumentet til EU-Kommissionens valideringsplatform Læs mere om validering af Penneo-signaturer Kan jeg planlægge automatiske e-mailpåmindelser til underskrivere i Penneo? Ja, med Penneo kan du opsætte automatiske påmindelser til underskrivere. Systemet sender selv e-mailpåmindelser til dem, der endnu ikke har underskrevet – så du undgår unødvendige forsinkelser og holder processen i gang helt automatisk. Hvad koster Penneo? Penneo tilbyder fleksible prismodeller, der tager højde for din organisations behov. Se vores priser og find den løsning, der passer til jer . Udforsk dine muligheder Ny til digitale underskrifter? Overvej disse 9 punkter først Læs mere Sådan starter du en digitaliseringsproces i din virksomhed Læs mere Penneo er nu integreret med Caseware Læs mere Se hvad du kan opnå med Penneo BOOK ET MØDE Se hvordan det fungerer Produkter Penneo Sign Priser Integrationer Åben API Validator Hvorfor Penneo Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Ressourcer Vidensunivers Trust Center Produktopdateringer SUPPORT SIGN Hjælpecenter KYC Hjælpecenter Systemstatus Virksomhed Om os Karriere Privatlivspolitik Vilkår Brug af cookies Accessibility Statement Whistleblower Policy Kontakt os PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
https://www.php.net/manual/ja/function.session-regenerate-id.php | PHP: session_regenerate_id - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_register_shutdown » « session_name PHP マニュアル 関数リファレンス セッション関連 Sessions セッション関数 Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_regenerate_id (PHP 4 >= 4.3.2, PHP 5, PHP 7, PHP 8) session_regenerate_id — 現在のセッションIDを新しく生成したものと置き換える 説明 session_regenerate_id ( bool $delete_old_session = false ): bool session_regenerate_id() は現在のセッションIDを 新しいものと置き換えます。その際、現在のセッション情報は維持されます。 session.use_trans_sid が有効な場合は、 session_regenerate_id() を呼んでから出力を始めなければいけません。 そうしないと、古いセッション ID が使われます。 警告 現在の session_regenerate_id は、モバイルネットワークや WiFi ネットワークなどの 不安定なネットワークをうまく扱えません。 そのため、 session_regenerate_id を 呼ぶと、セッションが消失する恐れがあります。 すぐに古いセッションデータを破棄すべきではありませんが、 古いセッションID のタイムスタンプと、 アクセス制御は破棄すべきでしょう。 さもないと、ページへの同時アクセスによって、 状態の不整合が発生したり、セッションが失われたり、 クライアント(ブラウザ) 側のレースコンディションが発生したり、 不必要なセッションIDをたくさん作らなければならなくなるかもしれません。 セッションデータをすぐに破棄してしまうと、 セッションハイジャックの検出だけでなく、 防止もできなくしてしまいます。 パラメータ delete_old_session 関連付けられた古いセッションを削除するかどうか。 削除による競合を防いだり、セッションハイジャックを 検出/防ぐ 必要がある場合には、古いセッションを削除すべきではありません。 戻り値 成功した場合に true を、失敗した場合に false を返します。 例 例1 session_regenerate_id() の使用例 <?php // 注意: このコードは完全に動作するわけではありません。一例です！ session_start (); // 破棄されたタイムスタンプをチェック if (isset( $_SESSION [ 'destroyed' ]) && $_SESSION [ 'destroyed' ] < time () - 300 ) { // 通常は起こるべきではない。攻撃や不安定なネットワークによる可能性がある // このユーザーのセッションから、全ての認証ステータスを削除 remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } $old_sessionid = session_id (); // 破棄されたタイムスタンプを設定 $_SESSION [ 'destroyed' ] = time (); // session_regenerate_id() は古いセッションデータを保存します。 // 単に session_regenerate_id() を呼ぶだけでは、セッションの消失などに繋がる可能性があります。 // 次の例を見てください。 session_regenerate_id (); // 新しいセッションには、破棄されたタイムスタンプは不要 unset( $_SESSION [ 'destroyed' ]); $new_sessionid = session_id (); echo "古いセッション: $old_sessionid <br />" ; echo "新しいセッション: $new_sessionid <br />" ; print_r ( $_SESSION ); ?> 現在のセッションモジュールは、不安定なネットワークをうまく扱えません。 session_regenerate_id によるセッションの消失を避けるために、 セッションIDを管理すべきです。 例2 session_regenerate_id() による、セッションの消失を避ける <?php // 注意: このコードは完全に動作するわけではありません。一例です！ // my_session_start() and my_session_regenerate_id() によって、 // 不安定なネットワークによるセッションの消失を避けています。 // それに加えて、このコードは攻撃者から、盗まれたセッションを利用した // 攻撃を防ぐ可能性もあります。 function my_session_start () { session_start (); if (isset( $_SESSION [ 'destroyed' ])) { if ( $_SESSION [ 'destroyed' ] < time ()- 300 ) { // 通常は起こるべきではない。攻撃や不安定なネットワークによる可能性がある // このユーザーのセッションから、全ての認証ステータスを削除 remove_all_authentication_flag_from_active_sessions ( $_SESSION [ 'userid' ]); throw(new DestroyedSessionAccessException ); } if (isset( $_SESSION [ 'new_session_id' ])) { // 完全に expire してはいない。 // Cookie が不安定なネットワークによって失われた可能性がある。 // 適切なセッションIDのクッキーを設定するためにリトライする。 // 注意: 認証フラグを削除したい場合は、セッションIDを再度設定しようとしてはいけない。 session_commit (); session_id ( $_SESSION [ 'new_session_id' ]); // 新しいセッションIDが存在しているはず session_start (); return; } } } function my_session_regenerate_id () { // 不安定なネットワークのために、セッションID が設定されなかったときは、 // 新しいセッションID が、適切なセッションIDに設定されることが必須。 $new_session_id = session_create_id (); $_SESSION [ 'new_session_id' ] = $new_session_id ; // 破棄された時のタイムスタンプを設定 $_SESSION [ 'destroyed' ] = time (); // 現在のセッションを書き込んで閉じる session_commit (); // 新しいセッションを新しいセッションIDで開始 session_id ( $new_session_id ); ini_set ( 'session.use_strict_mode' , 0 ); session_start (); ini_set ( 'session.use_strict_mode' , 1 ); // 新しいセッションには、以下の情報は不要 unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> 参考 session_id() - 現在のセッション ID を取得または設定する session_create_id() - 新しいセッションIDを作成する session_start() - 新しいセッションを開始、あるいは既存のセッションを再開する session_destroy() - セッションに登録されたデータを全て破棄する session_reset() - session 配列を元の値で再初期化する session_name() - 現在のセッション名を取得または設定する Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 22 notes up down 42 tedivm at tedivm dot com ¶ 9 years ago I wrote the current top voted comment on this and wanted to add something. The existing code from my previous comment generates it's nonces in an insecure way- <?php $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); ?> Since "microtime" is predictable it makes brute forcing the nonce much easier. A better option would be something that utilizes randomness, such as- <?php bin2hex ( openssl_random_pseudo_bytes ( 32 )) ?> up down 42 tedivm at tedivm dot com ¶ 17 years ago I wrote the following code for a project I'm working on- it attempts to resolve the regenerate issue, as well as deal with a couple of other session related things. I tried to make it a little more generic and usable (for instance, in the full version it throws different types of exceptions for the different types of session issues), so hopefully someone might find it useful. <?php function regenerateSession ( $reload = false ) { // This token is used by forms to prevent cross site forgery attempts if(!isset( $_SESSION [ 'nonce' ]) || $reload ) $_SESSION [ 'nonce' ] = md5 ( microtime ( true )); if(!isset( $_SESSION [ 'IPaddress' ]) || $reload ) $_SESSION [ 'IPaddress' ] = $_SERVER [ 'REMOTE_ADDR' ]; if(!isset( $_SESSION [ 'userAgent' ]) || $reload ) $_SESSION [ 'userAgent' ] = $_SERVER [ 'HTTP_USER_AGENT' ]; //$_SESSION['user_id'] = $this->user->getId(); // Set current session to expire in 1 minute $_SESSION [ 'OBSOLETE' ] = true ; $_SESSION [ 'EXPIRES' ] = time () + 60 ; // Create new session without destroying the old one session_regenerate_id ( false ); // Grab current session ID and close both sessions to allow other scripts to use them $newSession = session_id (); session_write_close (); // Set session ID to the new one, and start it back up again session_id ( $newSession ); session_start (); // Don't want this one to expire unset( $_SESSION [ 'OBSOLETE' ]); unset( $_SESSION [ 'EXPIRES' ]); } function checkSession () { try{ if( $_SESSION [ 'OBSOLETE' ] && ( $_SESSION [ 'EXPIRES' ] < time ())) throw new Exception ( 'Attempt to use expired session.' ); if(! is_numeric ( $_SESSION [ 'user_id' ])) throw new Exception ( 'No session started.' ); if( $_SESSION [ 'IPaddress' ] != $_SERVER [ 'REMOTE_ADDR' ]) throw new Exception ( 'IP Address mixmatch (possible session hijacking attempt).' ); if( $_SESSION [ 'userAgent' ] != $_SERVER [ 'HTTP_USER_AGENT' ]) throw new Exception ( 'Useragent mixmatch (possible session hijacking attempt).' ); if(! $this -> loadUser ( $_SESSION [ 'user_id' ])) throw new Exception ( 'Attempted to log in user that does not exist with ID: ' . $_SESSION [ 'user_id' ]); if(! $_SESSION [ 'OBSOLETE' ] && mt_rand ( 1 , 100 ) == 1 ) { $this -> regenerateSession (); } return true ; }catch( Exception $e ){ return false ; } } ?> up down 3 Rumour ¶ 2 years ago The code example provided of my_session_regenerate_id() DOES NOT work and DESTROYS all session variables. Plus the second ini_set gives an error. The code for regenerating (only that part, the rest seems fine) should simply be this: <?php function my_session_regenerate_id () { $new_session_id = session_create_id (); // backup session variables $keepSession = $_SESSION ; // add info for users with bad connection not receiving the new session id $_SESSION [ 'new_session_id' ] = $new_session_id ; // Set destroy timestamp $_SESSION [ 'destroyed' ] = time (); // Write and close current session; session_commit () ; // Start session with new session ID ini_set ( 'session.use_strict_mode' , 0 ); session_id ( $new_session_id ); session_start (); $_SESSION = $keepSession ; } ?> up down 13 ei dot rik dot ops dot tad at gmail dot com ¶ 9 years ago In PHP 5.6 (and probably older versions), session_regenerate_id(true) do not trigger a read() call to the session handler for the new session id. In PHP 7, read() is triggered during session_regenerate_id(true). Nice to know when working with custom session handlers. up down 8 gr at gr5 dot org ¶ 14 years ago If you are trying to maintain 2 active sessions don't use session_regenerate_id(). Especially if the first session is closed and it's time to open the second. Because the session id is cached you also have to explicitly set it the second time. <?php session_name ( 'PHPSESSID' ); // redundant - here for clarity session_start (); // ...do stuff session_write_close (); // now switch to session 2... session_name ( 'PHPSESSID_2' ); if (isset( $_COOKIE [ 'phpsessid_2' ])) session_id ( $_COOKIE [ 'phpsessid_2' ]); // not doing this will simply reopen the first session again else session_id ( sha1 ( mt_rand ()); // dont use session_regenerate_id() here. Not creating a new id will create two cookies with same session id and same session variables session_start (); // ... do stuff with session 2 session_write_close (); ?> up down 13 ross at kndr dot org ¶ 21 years ago In a previous note, php at 5mm de describes how to prevent session hijacking by ensuring that the session id provided matches the HTTP_USER_AGENT and REMOTE_ADDR fields that were present when the session id was first issued. It should be noted that HTTP_USER_AGENT is supplied by the client, and so can be easily modified by a malicious user. Also, the client IP addresses can be spoofed, although that's a bit more difficult. Care should be taken when relying on the session for authentication. up down 4 babel at nosqamplease sympatico ca ¶ 21 years ago To add to php at 5mm de's comments: If the session is held over https, it's even better to save the client's cert or ssl session id instead of the hostname or ip, as it's proxy-transparent and more secure. up down 10 spmtrap at yahoo dot com ¶ 13 years ago `session_regenerate_id` sends a new cookie but doesn't overwrite the value stored in `$_COOKIE`. After calling `session_destroy`, the open session ID is discarded, so simply restarting the session with `session_start` (as done in Ben Johnson's code) will re-open the original, though now empty, session for the current request (subsequent requests will use the new session ID). Instead of `session_destroy`+`session_start`, use the `$delete_old_session` parameter to `session_regenerate_id` to delete the previous session data. <?php session_start (); /* Create a new session, deleting the previous session data. */ session_regenerate_id ( TRUE ); /* erase data carried over from previous session */ $_SESSION =array(); ?> To start a new session and leave the old untouched, simply leave out the argument to `session_regenerate_id`. up down 6 php at cny dot de ¶ 21 years ago Also note that REMOTE_ADDR may change on every request if the user comes through a proxy farm. Most AOL-users do. up down 2 k-gun !! mail ¶ 9 years ago Document example is wrong with usage of "session.use_strict_mode" according to RFC (says: "warning error for session_id() when use_strice_mode=1" on https://wiki.php.net/rfc/strict_sessions ). So, this directive affects "session_id()" not "session_start()". So usage must be like this; <?php // first set ini ini_set ( 'session.use_strict_mode' , '0' ); // and session_id ( $sid ); // then // maybe run this: ini_restore('session.use_strict_mode'); // then go on... ?> Refs (ctrl+f & use_strict_mode); https://wiki.php.net/rfc/strict_sessions https://wiki.php.net/rfc/session-create-id http://php.net/manual/en/function.session-id.php#119997 up down 3 madsen at sjovedyr.dk ¶ 22 years ago I had problems with a proxy changing a visitors session_id-cookie, so he'd get a LOT of errors when visiting my site. I handled the bogus session-id's like this. (Note: It only works in versions > 4.3.2.) <?php // Start a session and suppress error-messages. @ session_start (); // Catch bogus session-id's. if (! preg_match ( "/^[0-9a-z]*$/i" , session_id ())) { // Output a warning about the messed up session-id. $error -> handleError ( "WARN" , "Your session id is messed up, you might not be able to use some features on this site." ); // Generate a fresh session-id. session_regenerate_id (); } // Site contents. ?> Hope someone can use it. up down 1 Nicolas dot Chachereau at Infomaniak dot ch ¶ 20 years ago Session_destroy() does not only destroy the data associated with the current session_id (i.e. the file if you use the default session save handler), but also the session itself: if you call session_destroy() and then session_regenerate_id(), it will return false, and session_id() won't return anything. In order to manipulate a session after destroying it, you need to restart it. So in fact, the code mentionned by chris won't work. If you want to destroy the file associated with the old session_id, try the following: <?php session_start (); $old_sessid = session_id (); session_regenerate_id (); $new_sessid = session_id (); session_id ( $old_sessid ); session_destroy (); //If you don't copy the $_SESSION array, you won't be able to use the data associated with the old session id. $old_session = $_SESSION ; session_id ( $new_sessid ); session_start (); $_SESSION = $old_session ; //... ?> Note: this technique will send 3 Set-Cookie headers (one on each session_start() and one on session_regenerate_id()). I don't think this is a problem, but if it appears to be one, you could either leave it alone and wait for the garbage collector to catch the file associated with the old session, or try to delete the file with unlink(). up down 1 soapergem at gmail dot com ¶ 17 years ago This can be a very dangerous function if you're not careful about how you handle things, because even though it generates a whole new set of session data, it keeps the old data "open" until the script terminates, locking out any other scripts trying to run concurrently with the old session id. Recently I came across a situation where I wanted to explicitly pass in a session ID, copy the data from that session into a *new* session, and then continue operating under that new session, thereby allowing other scripts to use the old one concurrently. But I quickly found that these "other scripts" would not execute until the first script finished--even though it had already started a new session--because it kept the old session open. So if you're trying to copy over session data to a new session to free up the old session for continued, concurrent use, here's some code to ensure nobody's feet get stepped on: <?php // get session id of an existing session $sid = $_GET [ 'sid' ]; // start the old session to retrieve $_SESSION data session_id ( $sid ); session_start (); // start a new session; this copies the $_SESSION data over session_regenerate_id (); // hang on to the new session id $sid = session_id (); // close the old and new sessions session_write_close (); // re-open the new session session_id ( $sid ); session_start (); /* main code here */ ?> This could probably be encapsulated into a function with one parameter as well to save space if it was a repeated thing. up down 0 primenetworkzx at gmail dot com ¶ 17 years ago If you are storing your session data in a database you have to manually update the session_id in the database. The session_set_save_handler() will not do it for you. function UpdateSessID() { $old_sess_id = session_id(); session_regenerate_id(false); $new_sess_id = session_id(); $query = "UPDATE `session_table` SET `session_id` = '$new_sess_id' WHERE session_id = '$old_sess_id'"; mysql_query($query); } Be sure to set session_regenerate_id() to FALSE since it's not really necessary to delete the whole record from MySQL and add it again. That's unnecessary overhead. Only changing the id matters. up down 0 dyer85 at gmail dot com ¶ 20 years ago There could be a potential problem with elger at NOSPAM dot yellowbee dot nl's a few posts below. In the code, was used the REQUEST_URI server variable, which, in some cases might already contain the query string. Therefore, always apending '?whatever=foo' would occasionally cause the script to malfunction. I suggest using PHP_SELF, which will not contain the query string after the file. up down -2 mikebranttx at gmail dot com ¶ 8 years ago Note that in current PHP 7.2 nightly builds example #2 above will not work as shown. You will get following error upon trying to turn strict mode back on after session_start(): "ini_set(): A session is active. You cannot change the session module's ini settings at this time" I suppose this means that for any session where you perform session ID regeneration or session ID forwarding (from a session for which a recent session ID regeneration was performed to the new session ID). That you will just have to live with strict mode being disabled for the remainder of that active session. I don't know that this is really a security concern so long as you are following a single-session per request design (i.e. you are not working with multiple concurrent sessions). up down -2 chris at knowledge dot tee-vee ¶ 20 years ago licp - no, session_regenerate_id() does not destroy any saved session data. elger, I prefer the following order [code] // populate $_SESSION with any previously saved session data for the current session_id session_start(); ... // delete any saved data associated with current session_id, $_SESSION is not changed session_destroy(); // change session_id, $_SESSION not altered session_regenerate_id(); ... // save any $_SESSION data under the current session_id session_close(); [/code] up down -1 antomsa at hotmail dot it ¶ 4 years ago <?php function my_session_regenerate_id () { ... session_start (); ... unset( $_SESSION [ 'destroyed' ]); unset( $_SESSION [ 'new_session_id' ]); } ?> Within my_session_regenerate_id(), unset($_SESSION['destroyed']) and unset($_SESSION['new_session_id']) are useless because session_start() will open an empty session. They would be needed if built-in session_regenerate_id() was called. up down -4 kgm_india at yahoo dot co dot in ¶ 12 years ago as far as I have understood reading this online notes, session_name() is the name which is identified as session a through the cookies or http links. session_id is like a transaction within a session_name() and one session_name may have many session_id each session_id has the corresponding data stored. session_id are used in read and write callback under a session_name whatever it is, first call the session_name(), then call session_id () and then call start_session() start_session will open the session_name, then check the session_id called before and use it in the read or write call back for storing or retrieving data calling start_session() without session_name or session_id will use the default session_name and the default session_id in that order I hope if the order is followed there should not be any problems. do not call session_name or session_id after start_session(), if you are specific on using them. thank you for others note. up down -5 raido dot aasoja at gmail dot com ¶ 15 years ago A note on lost sessions and trying to fix it with session_regenerate_id: Make sure that you're not trying to push SimpleXML object to the session. It just won't go without first converting it to array. :) up down -3 sopel ¶ 20 years ago for php 5.1> user probably worth visiting is http://ilia.ws/archives/47-session_regenerate_id-Improvement.html up down -4 Alamin ¶ 7 years ago In the second example provided by php.net, should it call my_session_start inside the session regenerate method instead of directly calling session_start? I think it is an error. ＋ add a note セッション関数 session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/tools/clang/tools/extra/docs/ReleaseNotes.html | Extra Clang Tools 18.1.8 Release Notes — Extra Clang Tools 18.1.8 documentation Extra Clang Tools 18.1.8 documentation Extra Clang Tools 18.1.8 Release Notes «   Introduction   ::   Contents   ::   Clang-Tidy   » Extra Clang Tools 18.1.8 Release Notes ¶ Introduction What’s New in Extra Clang Tools 18.1.8? Major New Features Improvements to clangd Inlay hints Compile flags Hover Code completion Code actions Signature help Cross-references Objective-C Miscellaneous Improvements to clang-doc Improvements to clang-query Improvements to clang-rename Improvements to clang-tidy New checks New check aliases Changes in existing checks Removed checks Improvements to include-cleaner Improvements to clang-include-fixer Improvements to modularize Improvements to pp-trace Clang-tidy Visual Studio plugin Written by the LLVM Team Introduction ¶ This document contains the release notes for the Extra Clang Tools, part of the Clang release 18.1.8. Here we describe the status of the Extra Clang Tools in some detail, including major improvements from the previous release and new feature work. All LLVM releases may be downloaded from the LLVM releases web site . For more information about Clang or LLVM, including information about the latest release, please see the Clang Web Site or the LLVM Web Site . Note that if you are reading this file from a Git checkout or the main Clang web page, this document applies to the next release, not the current one. To see the release notes for a specific release, please see the releases page . What’s New in Extra Clang Tools 18.1.8? ¶ Some of the major new features and improvements to Extra Clang Tools are listed here. Generic improvements to Extra Clang Tools as a whole or to its underlying infrastructure are described first, followed by tool-specific sections. Major New Features ¶ … Improvements to clangd ¶ Inlay hints ¶ Type hints Improved heuristics for showing sugared vs. desguared types Some hints which provide no information (e.g. <dependent-type> ) are now omitted Parameter hints Parameter hints are now shown for calls through function pointers Parameter hints are now shown for calls to a class’s operator() No longer show bogus parameter hints for some builtins like __builtin_dump_struct Compile flags ¶ System include extractor ( --query-driver ) improvements The directory containing builtin headers is now excluded from extracted system includes Various flags which can affect the system includes ( --target , --stdlib , -specs ) are now forwarded to the driver Fixed a bug where clangd would sometimes try to call a driver that didn’t have obj-c support with -x objective-c++-header The driver path is now dot-normalized before being compared to the --query-driver pattern --query-driver is now supported by clangd-indexer Fixed a regression in clangd 17 where response files would not be expanded Hover ¶ Hover now shows alignment info for fields and records Code completion ¶ Refined heuristics for determining whether the use of a function can be a call or not Code actions ¶ The extract variable tweak gained support for extracting lambda expressions to a variable. A new tweak was added for turning unscoped into scoped enums. Signature help ¶ Improved support for calls through function pointer types Cross-references ¶ Improved support for C++20 concepts Find-references now works for labels Improvements to template heuristics Objective-C ¶ Miscellaneous ¶ Various stability improvements, e.g. crash fixes Improved error recovery on invalid code Clangd now bails gracefully on assembly and IR source files Improvements to clang-doc ¶ Improvements to clang-query ¶ The improvements are… Improvements to clang-rename ¶ The improvements are… Improvements to clang-tidy ¶ Preprocessor-level module header parsing is now disabled by default due to the problems it caused in C++20 and above, leading to performance and code parsing issues regardless of whether modules were used or not. This change will impact only the following checks: modernize-replace-disallow-copy-and-assign-macro , bugprone-reserved-identifier , and readability-identifier-naming . Those checks will no longer see macros defined in modules. Users can still enable this functionality using the newly added command line option –enable-module-headers-parsing . Remove configuration option AnalyzeTemporaryDestructors , which was deprecated since clang-tidy 16. Improved –dump-config to print check options in alphabetical order. Improved clang-tidy-diff.py script. Return exit code 1 if any clang-tidy subprocess exits with a non-zero code or if exporting fixes fails. Accept a directory as a value for -export-fixes to export individual yaml files for each compilation unit. Introduce a -config-file option that forwards a configuration file to clang-tidy . Corresponds to the –config-file option in clang-tidy . Improved run-clang-tidy.py script. It now accepts a directory as a value for -export-fixes to export individual yaml files for each compilation unit. New checks ¶ New bugprone-casting-through-void check. Detects unsafe or redundant two-step casting operations involving void* . New bugprone-chained-comparison check. Check detects chained comparison operators that can lead to unintended behavior or logical errors. New bugprone-compare-pointer-to-member-virtual-function check. Detects equality comparison between pointer to member virtual function and anything other than null-pointer-constant. New bugprone-inc-dec-in-conditions check. Detects when a variable is both incremented/decremented and referenced inside a complex condition and suggests moving them outside to avoid ambiguity in the variable’s value. New bugprone-incorrect-enable-if check. Detects incorrect usages of std::enable_if that don’t name the nested type type. New bugprone-multi-level-implicit-pointer-conversion check. Detects implicit conversions between pointers of different levels of indirection. New bugprone-optional-value-conversion check. Detects potentially unintentional and redundant conversions where a value is extracted from an optional-like type and then used to create a new instance of the same optional-like type. New bugprone-unused-local-non-trivial-variable check. Warns when a local non trivial variable is unused within a function. New cppcoreguidelines-no-suspend-with-lock check. Flags coroutines that suspend while a lock guard is in scope at the suspension point. New hicpp-ignored-remove-result check. Ensure that the result of std::remove , std::remove_if and std::unique are not ignored according to rule 17.5.1. New misc-coroutine-hostile-raii check. Detects when objects of certain hostile RAII types persists across suspension points in a coroutine. Such hostile types include scoped-lockable types and types belonging to a configurable denylist. New modernize-use-constraints check. Replace enable_if with C++20 requires clauses. New modernize-use-starts-ends-with check. Checks whether a find or rfind result is compared with 0 and suggests replacing with starts_with when the method exists in the class. Notably, this will work with std::string and std::string_view . New modernize-use-std-numbers check. Finds constants and function calls to math functions that can be replaced with C++20’s mathematical constants from the numbers header and offers fix-it hints. New performance-enum-size check. Recommends the smallest possible underlying type for an enum or enum class based on the range of its enumerators. New readability-avoid-nested-conditional-operator check. Identifies instances of nested conditional operators in the code. New readability-avoid-return-with-void-value check. Finds return statements with void values used within functions with void result types. New readability-redundant-casting check. Detects explicit type casting operations that involve the same source and destination types, and subsequently recommend their removal. New readability-redundant-inline-specifier check. Detects redundant inline specifiers on function and variable declarations. New readability-reference-to-constructed-temporary check. Detects C++ code where a reference variable is used to extend the lifetime of a temporary object that has just been constructed. New check aliases ¶ New alias cppcoreguidelines-macro-to-enum to modernize-macro-to-enum was added. Changes in existing checks ¶ Improved abseil-string-find-startswith check to also consider std::basic_string_view in addition to std::basic_string by default. Improved bugprone-assert-side-effect check to report usage of non-const << and >> operators in assertions and fixed some false-positives with const operators. Improved bugprone-dangling-handle check to support functional casting during type conversions at variable initialization, now with improved compatibility for C++17 and later versions. Improved bugprone-exception-escape check by extending the default check function names to include iter_swap and iter_move . Improved bugprone-implicit-widening-of-multiplication-result check to correctly emit fixes. Improved bugprone-lambda-function-name check by adding option IgnoreMacros to ignore warnings in macros. Improved bugprone-non-zero-enum-to-bool-conversion check by eliminating false positives resulting from direct usage of bitwise operators. Improved bugprone-reserved-identifier check, so that it does not warn on macros starting with underscore and lowercase letter. Improved bugprone-sizeof-expression check diagnostics to precisely highlight specific locations, providing more accurate guidance. Improved bugprone-unchecked-optional-access check, so that it does not crash during handling of optional values. Improved bugprone-undefined-memory-manipulation check to support fixed-size arrays of non-trivial types. Improved bugprone-unused-return-value check diagnostic message, added support for detection of unused results when cast to non- void type. Casting to void no longer suppresses issues by default, control this behavior with the new AllowCastToVoid option. Improved cppcoreguidelines-avoid-non-const-global-variables check to ignore static variables declared within the scope of class / struct . Improved cppcoreguidelines-avoid-reference-coroutine-parameters check to ignore false positives related to matching parameters of non coroutine functions and increase issue detection for cases involving type aliases with references. Improved cppcoreguidelines-missing-std-forward check to address false positives in the capture list and body of lambdas. Improved cppcoreguidelines-narrowing-conversions check by extending the IgnoreConversionFromTypes option to include types without a declaration, such as built-in types. Improved cppcoreguidelines-prefer-member-initializer check to ignore delegate constructors and ignore re-assignment for reference or when initialization depend on field that is initialized before. Additionally, it now provides valid fixes for member variables initialized with macros. Improved cppcoreguidelines-pro-bounds-array-to-pointer-decay check to ignore predefined expression (e.g., __func__ , …). Improved cppcoreguidelines-pro-bounds-constant-array-index check to perform checks on derived classes of std::array . Improved cppcoreguidelines-pro-type-const-cast check to ignore casts to const or volatile type (controlled by StrictMode option) and casts in implicitly invoked code. Improved cppcoreguidelines-pro-type-member-init check to ignore dependent delegate constructors. Improved cppcoreguidelines-pro-type-static-cast-downcast check to disregard casts on non-polymorphic types when the StrictMode option is set to false . Improved cppcoreguidelines-pro-type-vararg check to ignore false-positives in unevaluated context (e.g., decltype , sizeof , …). Improved cppcoreguidelines-rvalue-reference-param-not-moved check to ignore unused parameters when they are marked as unused and parameters of deleted functions and constructors. Improved google-readability-casting check to ignore constructor calls disguised as functional casts. Improved google-runtime-int check to ignore false positives on user defined-literals. Improved llvm-namespace-comment check to provide fixes for inline namespaces in the same format as clang-format . Improved llvmlibc-callee-namespace to support customizable namespace. This matches the change made to implementation in namespace. Improved llvmlibc-implementation-in-namespace to support customizable namespace. This further allows for testing the libc when the system-libc is also LLVM’s libc. Improved llvmlibc-inline-function-decl to properly ignore implicit functions, such as struct constructors, and explicitly deleted functions. Improved misc-const-correctness check to avoid false positive when using pointer to member function. Additionally, the check no longer emits a diagnostic when a variable that is not type-dependent is an operand of a type-dependent binary operator. Improved performance of the check through optimizations. The check no longer emits a diagnostic for non-parameter-pack variables in C++17 fold expressions. Improved misc-include-cleaner check by adding option DeduplicateFindings to output one finding per symbol occurrence, avoid inserting the same header multiple times, fix a bug where IgnoreHeaders option won’t work with verbatim/std headers. Improved misc-redundant-expression check to ignore false-positives in unevaluated context (e.g., decltype ). Improved misc-static-assert check to ignore false-positives when referring to non- constexpr variables in non-unevaluated context. Improved misc-unused-using-decls check to avoid false positive when using in elaborated type and only check C++ files. Improved modernize-avoid-bind check to not emit a return for fixes when the function returns void and to provide valid fixes for cases involving bound C++ operators. Improved modernize-loop-convert to support for-loops with iterators initialized by free functions like begin , end , or size and avoid crash for array of dependent array and non-dereferenceable builtin types used as iterators. Improved modernize-make-shared check to support std::shared_ptr implementations that inherit the reset method from a base class. Improved modernize-return-braced-init-list check to ignore false-positives when constructing the container with count copies of elements with value value . Improved modernize-use-auto to avoid create incorrect fix hints for pointer to array type and pointer to function type. Improved modernize-use-emplace to not replace aggregates that emplace cannot construct with aggregate initialization. Improved modernize-use-equals-delete check to ignore false-positives when special member function is actually used or implicit. Improved modernize-use-nullptr check by adding option IgnoredTypes that can be used to exclude some pointer types. Improved modernize-use-std-print check to accurately generate fixes for reordering arguments. Improved modernize-use-using check to fix function pointer and forward declared typedef correctly. Added option IgnoreExternC to ignore typedef declaration in extern "C" scope. Improved performance-faster-string-find check to properly escape single quotes. Improved performance-for-range-copy check to handle cases where the loop variable is a structured binding. Improved performance-noexcept-move-constructor to better handle conditional noexcept expressions, eliminating false-positives. Improved performance-noexcept-swap check to enforce a stricter match with the swap function signature and better handling of condition noexcept expressions, eliminating false-positives. iter_swap function name is checked by default. Improved readability-braces-around-statements check to ignore false-positive for if constexpr in lambda expression. Improved readability-avoid-const-params-in-decls diagnostics to highlight the const location Improved readability-container-contains to correctly handle integer literals with suffixes in fix-its. Improved readability-container-size-empty check to detect comparison between string and empty string literals and support length() method as an alternative to size() . Resolved false positives tied to negative values from size-like methods, and one triggered by size checks below zero. Improved readability-function-size check configuration to use none rather than -1 to disable some parameters. Improved readability-identifier-naming check to issue accurate warnings when a type’s forward declaration precedes its definition. Additionally, it now provides appropriate warnings for struct and union in C, while also incorporating support for the Leading_upper_snake_case naming convention. The handling of typedef has been enhanced, particularly within complex types like function pointers and cases where style checks were omitted when functions started with macros. Added support for C++20 concept declarations. Camel_Snake_Case and camel_Snake_Case now detect more invalid identifier names. Fields in anonymous records (i.e. anonymous structs and unions) now can be checked with the naming rules associated with their enclosing scopes rather than the naming rules of public struct / union members. Improved readability-implicit-bool-conversion check to take do-while loops into account for the AllowIntegerConditions and AllowPointerConditions options. It also now provides more consistent suggestions when parentheses are added to the return value or expressions. It also ignores false-positives for comparison containing bool bitfield. Improved readability-misleading-indentation check to ignore false-positives for line started with empty macro. Improved readability-non-const-parameter check to ignore false-positives in initializer list of record. Improved readability-redundant-member-init check to now also detect redundant in-class initializers. Improved readability-simplify-boolean-expr check by adding the new option IgnoreMacros that allows to ignore boolean expressions originating from expanded macros. Improved readability-simplify-subscript-expr check by extending the default value of the Types option to include std::span . Improved readability-static-accessed-through-instance check to identify calls to static member functions with out-of-class inline definitions. Removed checks ¶ Improvements to include-cleaner ¶ Support for --only-headers flag to limit analysis to headers matching a regex Recognizes references through `` concept``s Builtin headers are not analyzed Handling of references through friend declarations Fixes around handling of IWYU pragmas on stdlib headers Improved handling around references to/from template specializations Improvements to clang-include-fixer ¶ The improvements are… Improvements to modularize ¶ The improvements are… Improvements to pp-trace ¶ Clang-tidy Visual Studio plugin ¶ «   Introduction   ::   Contents   ::   Clang-Tidy   » © Copyright 2007-2024, The Clang Team. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://support.microsoft.com/tr-tr/windows/microsoft-edge-de-tan%C4%B1mlama-bilgilerini-y%C3%B6netme-g%C3%B6r%C3%BCnt%C3%BCleme-izin-verme-engelleme-silme-ve-kullanma-168dab11-0753-043d-7c16-ede5947fc64d | Microsoft Edge'de tanımlama bilgilerini yönetme: Görüntüleme, izin verme, engelleme, silme ve kullanma - Microsoft Desteği İlgili konular × Windows güvenliği, güvenliği ve gizliliği Genel bakış Güvenlik, güvenlik ve gizliliğe genel bakış Windows güvenliği Windows güvenliği ile ilgili yardım alın Windows güvenliği ile korunma Xbox'ınızı veya Windows kişisel bilgisayarınızı geri dönüştürmeden, satmadan veya hediye etmeden önce Windows bilgisayarınızdan kötü amaçlı yazılımları kaldırma Windows güvenliği Windows güvenliği ile ilgili yardım alma Microsoft Edge’de tarayıcı geçmişini görüntüleme ve silme Tanımlama bilgilerini silme ve yönetme Windows'u yeniden yüklerken değerli içeriğinizi güvenle kaldırın Kayıp bir Windows cihazını bulma ve kilitleme Windows gizliliği Windows gizliliği ile ilgili yardım alma Uygulamaların kullandığı Windows gizlilik ayarları Gizlilik panosunda verilerinizi görüntüleme Ana içeriğe atla Microsoft Destek Destek Destek Giriş Microsoft 365 Office Ürünler Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows diğer ... Cihazlar Surface Bilgisayar Donatıları Xbox Bilgisayar Oyunları HoloLens Surface Hub Donanım garantileri Hesap ve faturalandırma Hesap Microsoft Store ve faturalama Kaynaklar Yenilikler Topluluk forumları Microsoft 365 Yöneticileri Küçük İşletme Portalı Geliştirici Eğitim Destek dolandırıcılığını bildirin Ürün güvenliği Daha fazla Microsoft 365’i satın alın Tüm Microsoft Global Microsoft 365 Teams Copilot Windows Xbox Destek Yazılım Yazılım Windows Uygulamaları Yapay Zeka OneDrive Outlook Skype'tan Teams'e geçiş yapma OneNote Microsoft Teams PCs ve cihazlar PCs ve cihazlar Xbox alın Aksesuarları Eğlence Eğlence Xbox Game Pass Ultimate Xbox ve oyunlar PC Oyunları İş İş Microsoft Güvenlik Azure Dynamics 365 İş için Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 Geliştirici ve BT Geliştirici ve BT Microsoft Geliştiricisi Microsoft Learn Yapay zeka market uygulamaları için destek Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Diğer Diğer Ücretsiz yüklemeler ve güvenlik Eğitim Site Haritasını Göster Ara Yardım arayın Sonuç yok İptal Oturum aç Microsoft hesabıyla oturum açın Oturum açın veya hesap oluşturun. Merhaba, Farklı bir hesap seçin. Birden çok hesabınız var Oturum açmak istediğiniz hesabı seçin. İlgili konular Windows güvenliği, güvenliği ve gizliliği Genel bakış Güvenlik, güvenlik ve gizliliğe genel bakış Windows güvenliği Windows güvenliği ile ilgili yardım alın Windows güvenliği ile korunma Xbox'ınızı veya Windows kişisel bilgisayarınızı geri dönüştürmeden, satmadan veya hediye etmeden önce Windows bilgisayarınızdan kötü amaçlı yazılımları kaldırma Windows güvenliği Windows güvenliği ile ilgili yardım alma Microsoft Edge’de tarayıcı geçmişini görüntüleme ve silme Tanımlama bilgilerini silme ve yönetme Windows'u yeniden yüklerken değerli içeriğinizi güvenle kaldırın Kayıp bir Windows cihazını bulma ve kilitleme Windows gizliliği Windows gizliliği ile ilgili yardım alma Uygulamaların kullandığı Windows gizlilik ayarları Gizlilik panosunda verilerinizi görüntüleme Microsoft Edge'de tanımlama bilgilerini yönetme: Görüntüleme, izin verme, engelleme, silme ve kullanma Uygulandığı Öğe Windows 10 Windows 11 Microsoft Edge Tanımlama bilgileri, ziyaret ettiğiniz web sitelerine göre cihazınızda depolanan küçük veri parçalarıdır. Bunlar oturum açma kimlik bilgilerini hatırlama, site tercihleri ve kullanıcı davranışını izleme gibi çeşitli amaçlara hizmet eder. Ancak, gizlilik nedenleriyle veya gözatma sorunlarını çözmek için tanımlama bilgilerini silmek isteyebilirsiniz. Bu makalede şunların nasıl yapılacağını gösteren yönergeler sağlanır: Tüm tanımlama bilgilerini görüntüleme Tüm tanımlama bilgilerine izin ver Belirli bir web sitesinden tanımlama bilgilerine izin ver Üçüncü taraf tanımlama bilgilerini engelleme Tüm tanımlama bilgilerini engelle Belirli bir siteden tanımlama bilgilerini engelleme Tüm tanımlama bilgilerini silme Belirli bir sitedeki tanımlama bilgilerini silme Tarayıcıyı her kapattığınızda tanımlama bilgilerini silme Daha hızlı göz atmak için sayfayı önceden yüklemek için tanımlama bilgilerini kullanma Tüm tanımlama bilgilerini görüntüleme Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Gizlilik, arama ve hizmetler > Ayarlar'ı seçin. Çerezler'i seçin, ardından depolanan tüm tanımlama bilgilerini ve ilgili site bilgilerini görüntülemek için Tüm tanımlama bilgilerini ve site verilerini görüntüle'ye tıklayın. Tüm tanımlama bilgilerine izin ver Tanımlama bilgilerine izin vererek, web siteleri tarayıcınıza veri kaydedip alabilir ve bu da tercihlerinizi ve oturum açma bilgilerinizi anımsayarak göz atma deneyiminizi geliştirebilir. Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Gizlilik, arama ve hizmetler > Ayarlar'ı seçin. Tanımlama Bilgileri'ni seçin ve tüm tanımlama bilgilerine izin vermek için Sitelerin tanımlama bilgisi verilerini kaydetmesine ve okumasına izin ver (önerilir) düğmesini etkinleştirin. Belirli bir siteden tanımlama bilgilerine izin ver Tanımlama bilgilerine izin vererek, web siteleri tarayıcınıza veri kaydedip alabilir ve bu da tercihlerinizi ve oturum açma bilgilerinizi anımsayarak göz atma deneyiminizi geliştirebilir. Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Gizlilik, arama ve hizmetler > Ayarlar'ı seçin. Tanımlama bilgileri'ne tıklayın ve Tanımlama bilgilerini kaydetmeye izin verildi'ye gidin. Site url'sini girerek site başına tanımlama bilgilerine izin vermek için Site ekle'yi seçin. Üçüncü taraf tanımlama bilgilerini engelleme Üçüncü taraf sitelerinin bilgisayarınızda tanımlama bilgileri depolamasını istemiyorsanız tanımlama bilgilerini engelleyebilirsiniz. Ancak bunu yapmak, bazı sayfaların düzgün görüntülenmesini engelleyebilir veya siteden, siteyi görüntüleyebilmek için tanımlama bilgilerine izin vermeniz gerektiğini bildiren bir ileti alabilirsiniz. Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Gizlilik, arama ve hizmetler > Ayarlar'ı seçin. Tanımlama Bilgileri'ni seçin ve Üçüncü taraf tanımlama bilgilerini engelle iki durumlu düğmesini etkinleştirin. Tüm tanımlama bilgilerini engelle Üçüncü taraf sitelerinin bilgisayarınızda tanımlama bilgileri depolamasını istemiyorsanız tanımlama bilgilerini engelleyebilirsiniz. Ancak bunu yapmak, bazı sayfaların düzgün görüntülenmesini engelleyebilir veya siteden, siteyi görüntüleyebilmek için tanımlama bilgilerine izin vermeniz gerektiğini bildiren bir ileti alabilirsiniz. Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Gizlilik, arama ve hizmetler > Ayarlar'ı seçin. Tanımlama Bilgileri'ne tıklayın ve tüm tanımlama bilgilerini engellemek için Sitelerin tanımlama bilgisi verilerini kaydetmesine ve okumasına izin ver'i (önerilen) devre dışı bırakın. Belirli bir siteden tanımlama bilgilerini engelleme Microsoft Edge, belirli bir sitedeki tanımlama bilgilerini engellemenize olanak tanır, ancak bunu yapmak bazı sayfaların düzgün görüntülenmesini engelleyebilir veya bir siteden bu siteyi görüntülemek için tanımlama bilgilerine izin vermeniz gerektiğini bildiren bir ileti alabilirsiniz. Belirli bir sitedeki tanımlama bilgilerini engellemek için: Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Gizlilik, arama ve hizmetler > Ayarlar'ı seçin. Tanımlama bilgileri'ne tıklayın ve Tanımlama bilgilerini kaydetmesine ve okumasına izin verilmiyor bölümüne gidin. Site URL'sini girerek site başına tanımlama bilgilerini engellemek için Site ekle'yi seçin. Tüm tanımlama bilgilerini silme Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Ayarlar > Gizlilik, arama ve hizmetler öğesini seçin. Gözatma verilerini temizle'yi ve ardından Gözatma verilerini şimdi temizle'nin yanındaki Bulunanları temizle'yi seçin . Zaman aralığı seçeneğinin altında listeden bir zaman aralığı seçin. Tanımlama bilgileri ve diğer site verileri ’ni seçin ve ardından Şimdi temizle ’yi seçin. Not: Alternatif olarak, birlikte CTRL + SHIFT + DELETE tuşlarına basıp 4. ve 5. adımlarla devam ederek tanımlama bilgilerini silebilirsiniz. Tüm tanımlama bilgileriniz ve diğer site verileriniz artık seçtiğiniz zaman aralığı için silinir. Bu, çoğu sitede oturumunuzu kapatmanızı sağlar. Belirli bir sitedeki tanımlama bilgilerini silme Edge tarayıcıyı açın, Ayarlar ve daha fazlası > Gizlilik , arama ve hizmetler > Ayarlar'ı seçin. Tanımlama Bilgileri'ni seçin, ardından Tüm tanımlama bilgilerini ve site verilerini gör'e tıklayın ve tanımlama bilgilerini silmek istediğiniz siteyi arayın. Tanımlama bilgilerini silmek istediğiniz sitenin sağındaki aşağı oku seçin ve ardından Sil seçeneğini belirleyin. Seçtiğiniz sitenin tanımlama bilgileri artık siliniyor. Tanımlama bilgilerini silmek istediğiniz tüm siteler için bu adımı yineleyin. Tarayıcıyı her kapattığınızda tanımlama bilgilerini silme Edge tarayıcıyı açın, Ayarlar ve daha fazlası > Ayarlar > Gizlilik, arama ve hizmetler'i seçin. Gözatma verilerini temizle'yi ve ardından tarayıcıyı her kapatışınızda nelerin temizleneceğini seçin'i seçin. Tanımlama bilgileri ve diğer site verileri iki durumlu düğmesini açın. Bu özellik açıldıktan sonra Edge tarayıcınızı her kapatışınızda tüm tanımlama bilgileri ve diğer site verileri silinir. Bu, çoğu sitede oturumunuzu kapatmanızı sağlar. Daha hızlı göz atmak için sayfayı önceden yüklemek için tanımlama bilgilerini kullanma Edge tarayıcısını açın, tarayıcı pencerenizin sağ üst köşesinde Ayarlar ve daha fazlası'nı seçin. Ayarlar > Gizlilik, arama ve hizmetler öğesini seçin. Tanımlama Bilgileri'ni seçin ve daha hızlı gezinmek ve arama yapmak için Sayfaları Önceden Yükle düğmesini etkinleştirin. RSS AKIŞLARINA ABONE OLUN Daha fazla yardıma mı ihtiyacınız var? Daha fazla seçenek mi istiyorsunuz? Keşfedin Topluluk Bize Ulaşın Abonelik avantajlarını keşfedin, eğitim kurslarına göz atın, cihazınızın güvenliğini nasıl sağlayacağınızı öğrenin ve daha fazlasını yapın. Microsoft 365 abonelik avantajları Microsoft 365 eğitimi Microsoft güvenliği Erişilebilirlik merkezi Topluluklar, soru sormanıza ve soruları yanıtlamanıza, geri bildirimde bulunmanıza ve zengin bilgiye sahip uzmanlardan bilgi almanıza yardımcı olur. Microsoft Topluluğu'na sorun Microsoft Tech Topluluğu Windows Insider'lar Microsoft 365 Insider'lar Sık karşılaşılan sorunlara çözümler bulun veya bir destek temsilcisinden yardım alın. Çevrimiçi destek Bu bilgi yararlı oldu mu? Evet Hayır Teşekkürler! Microsoft ile ilgili başka geri bildiriminiz var mı? İyileştirme yapmamıza yardımcı olabilir misiniz? (Size yardımcı olabilmemiz için Microsoft’a geri bildirim gönderin.) Dil kalitesinden ne kadar memnunsunuz? Deneyiminizi ne etkiledi? Sorunum çözüldü Talimatlar anlaşılırdı Takip edilmesi kolay Jargon yok Resimler yardımcı oldu Çeviri kalitesi Ekranım ile eşleşmedi Talimatlar yanlıştı Çok teknik Yeterli bilgi yok Yeterli resim yok Çeviri kalitesi Başka geri bildirim göndermek istiyor musunuz? (İsteğe bağlı) Geri bildirim gönder Gönder’e bastığınızda, geri bildiriminiz Microsoft ürün ve hizmetlerini geliştirmek için kullanılır. BT yöneticiniz bu verileri toplayabilecek. Gizlilik Bildirimi. Geri bildiriminiz için teşekkürler! × Yenilikler Kuruluşlar için Copilot Kişisel kullanım için Copilot Microsoft 365 Microsoft ürünlerini keşfedin Windows 11 uygulamaları Microsoft Store Hesap profili İndirme Merkezi Microsoft Store Desteği İadeler Sipariş izleme Eğitim Microsoft Eğitim Eğitim cihazları Eğitim için Microsoft Teams Microsoft 365 Eğitim Office Eğitimi Eğitimci eğitimi ve gelişimi Öğrenciler ve ebeveynler için fırsatlar Öğrenciler için Azure İşletme Microsoft Güvenlik Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Geliştirici ve BT Microsoft Geliştiricisi Microsoft Learn Yapay zeka market uygulamaları için destek Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Şirket Kariyer Fırsatları Microsoft Hakkında Microsoft'ta Gizlilik Yatırımcılar Sürdürülebilirlik Türkçe (Türkiye) Gizlilik Tercihleriniz Geri Çevirme Simgesi Gizlilik Tercihleriniz Gizlilik Tercihleriniz Geri Çevirme Simgesi Gizlilik Tercihleriniz Tüketici Durumu Gizliliği Microsoft'a başvurun Gizlilik Tanımlama bilgilerini yönetin Kullanım Şartları Ticari Markalar Reklamlarımız hakkında © Microsoft 2026 | 2026-01-13T09:30:34 |
https://www.php.net/manual/de/function.session-name.php | PHP: session_name - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_regenerate_id » « session_module_name PHP-Handbuch Funktionsreferenz Session-Erweiterungen Sessions Session-Funktionen Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_name (PHP 4, PHP 5, PHP 7, PHP 8) session_name — Liefert und/oder setzt den Namen der aktuellen Session Beschreibung session_name ( ? string $name = null ): string | false session_name() gibt den Namen der aktuellen Session zurück. Falls name angegeben wurde, aktualisiert session_name() den Namen der Session und gibt den alten Namen der Session zurück. Wird ein neuer Session-Name ( name ) angegeben, ändert session_name() das HTTP-Cookie (und gibt den Inhalt aus, wenn session.use_trans_sid aktiviert ist). Nachdem das HTTP-Cookie gesendet wurde, erzeugt session_name() ein E_WARNING . session_name() muss vor session_start() aufgerufen werden, damit die Session ordnungsgemäß funktioniert. Der Session-Name wird auf den Ausgangswert zurückgesetzt, der zu Beginn in session.name gespeichert wurde. Deshalb muss session_name() bei jeder Anfrage aufgerufen werden (und bevor session_start() aufgerufen wurde). Parameter-Liste name Der Session-Name referenziert den Namen der Session, der in Cookies und URLs verwendet wird (z. B. PHPSESSID ). Er sollte nur alphanumerische Zeichen enthalten und sollte kurz und beschreibend sein (z. B. für Benutzer mit aktivierter Cookie-Warnung). Wenn name angegeben wird und nicht null ist, wird der Name der aktuellen Session durch dessen Wert ersetzt. Warnung Der Session-Name darf nicht nur aus Zahlen bestehen, sondern muss mindestens einen Buchstaben enthalten. Andernfalls wird jedesmal eine neue Session-ID erzeugt. Rückgabewerte Gibt den Namen der aktuellen Session zurück. Wird name übergegeben und die Funktion aktualisiert den Session-Namen, wird der Name der alten Session zurückgegeben. Bei einem Fehler wird false zurückgegeben. Changelog Version Beschreibung 8.0.0 name ist jetzt nullable (akzeptiert den NULL-Wert). 7.2.0 session_name() prüft den Session-Status; zuvor wurde nur der Cookie-Status geprüft. Somit war es zuvor möglich, dass session_name() nach session_start() aufgerufen wurde, was möglicherweise zum Absturz von PHP und zu anderem Fehlverhalten führen konnte. Beispiele Beispiel #1 session_name() -Beispiel <?php /* den Session-Namen auf WebsiteID setzen */ $name_vorher = session_name ( "WebsiteID" ); echo "Der vorhergehende Session-Name war $name_vorher <br />" ; ?> Siehe auch Die Konfigurationsanweisung session.name Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 9 notes up down 146 Hongliang Qiang ¶ 21 years ago This may sound no-brainer: the session_name() function will have no essential effect if you set session.auto_start to "true" in php.ini . And the obvious explanation is the session already started thus cannot be altered before the session_name() function--wherever it is in the script--is executed, same reason session_name needs to be called before session_start() as documented. I know it is really not a big deal. But I had a quite hard time before figuring this out, and hope it might be helpful to someone like me. up down 65 php at wiz dot cx ¶ 17 years ago if you try to name a php session "example.com" it gets converted to "example_com" and everything breaks. don't use a period in your session name. up down 40 relsqui at chiliahedron dot com ¶ 16 years ago Remember, kids--you MUST use session_name() first if you want to use session_set_cookie_params() to, say, change the session timeout. Otherwise it won't work, won't give any error, and nothing in the documentation (that I've seen, anyway) will explain why. Thanks to brandan of bildungsroman.com who left a note under session_set_cookie_params() explaining this or I'd probably still be throwing my hands up about it. up down 21 Joseph Dalrymple ¶ 14 years ago For those wondering, this function is expensive! On a script that was executing in a consistent 0.0025 seconds, just the use of session_name("foo") shot my execution time up to ~0.09s. By simply sacrificing session_name("foo"), I sped my script up by roughly 0.09 seconds. up down 10 Victor H ¶ 10 years ago As Joseph Dalrymple said, adding session_name do slow down a little bit the execution time. But, what i've observed is that it decreased the fluctuation between requests. Requests on my script fluctuated between 0,045 and 0,022 seconds. With session_name("myapp"), it goes to 0,050 and 0,045. Not a big deal, but that's a point to note. For those with problems setting the name, when session.auto_start is set to 1, you need to set the session.name on php.ini! up down 3 mmulej at gmail dot com ¶ 4 years ago Hope this is not out of php.net noting scope. session_name('name') must be set before session_start() because the former changes ini settings and the latter reads them. For the same reason session_set_cookie_params($options) must be set before session_start() as well. I find it best to do the following. function is_session_started() { if (php_sapi_name() === 'cli') return false; if (version_compare(phpversion(), '5.4.0', '>=')) return session_status() === PHP_SESSION_ACTIVE; return session_id() !== ''; } if (!is_session_started()) { session_name($session_name); session_set_cookie_params($cookie_options); session_start(); } up down 0 tony at marston-home dot demon dot co dot uk ¶ 7 years ago The description that session_name() gets and/or sets the name of the current session is technically wrong. It does nothing but deal with the value originally supplied by the session.name value within the php.ini file. Thus:- $name = session_name(); is functionally equivalent to $name = ini_get('session.name'); and session_name('newname); is functionally equivalent to ini_set('session.name','newname'); This also means that: $old_name = session_name('newname'); is functionally equivalent to $old_name = ini_set('session.name','newname'); The current value of session.name is not attached to a session until session_start() is called. Once session_start() has used session.name to lookup the session_id() in the cookie data the name becomes irrelevant as all further operations on the session data are keyed by the session_id(). Note that changing session.name while a session is currently active will not update the name in any session cookie. The new name does not take effect until the next call to session_start(), and this requires that the current session, which was created with the previous value for session.name, be closed. up down -4 tony at marston-home dot demon dot co dot uk ¶ 7 years ago The description has recently been modified to contain the statement "When new session name is supplied, session_name() modifies HTTP cookie". This is not correct as session_name() has never modified any cookie data. A change in session.name does not become effective until session_start() is called, and it is session_start() that creates the cookie if it does not already exist. See the following bug report for details: https://bugs.php.net/bug.php?id=76413 up down -3 descartavel1+php at gmail dot com ¶ 2 years ago Always try to set the prefix for your session name attribute to either `__Host-` or `__Secure-` to benefit from Browsers improved security. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#attributes Also, if you have auto_session enabled, you must set this name in session.name in your config (php.ini, htaccess, etc) ＋ add a note Session-Funktionen session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://support.microsoft.com/ru-ru/windows/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%84%D0%B0%D0%B9%D0%BB%D0%B0%D0%BC%D0%B8-cookie-%D0%B2-microsoft-edge-%D0%BF%D1%80%D0%BE%D1%81%D0%BC%D0%BE%D1%82%D1%80-%D1%80%D0%B0%D0%B7%D1%80%D0%B5%D1%88%D0%B5%D0%BD%D0%B8%D0%B5-%D0%B1%D0%BB%D0%BE%D0%BA%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0-%D1%83%D0%B4%D0%B0%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D0%B8-%D0%B8%D1%81%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-168dab11-0753-043d-7c16-ede5947fc64d | Управление файлами cookie в Microsoft Edge: просмотр, разрешение, блокировка, удаление и использование - Служба поддержки Майкрософт Связанные темы × Безопасность, защита и конфиденциальность Windows Обзор Общие сведения о безопасности, защите и конфиденциальности Безопасность Windows Техническая поддержка по безопасности Windows Обеспечение защиты с помощью безопасности Windows Прежде чем утилизировать, продать или подарить свое устройство с Windows или Xbox Удаление вредоносных программ с компьютера с Windows Безопасность Windows Техническая поддержка по безопасности Windows Просмотр и удаление журнала браузера в Microsoft Edge Удаление файлов cookie и управление ими Безопасное удаление ценного содержимого при переустановке Windows Поиск и блокировка потерянного устройства с Windows Конфиденциальность Windows Техническая поддержка по конфиденциальности Windows Параметры конфиденциальности Windows, используемые в приложениях Просмотр данных на панели мониторинга конфиденциальности Перейти к основному контенту Microsoft Поддержка Поддержка Поддержка Главная Microsoft 365 Office Продукты Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows еще... Устройства Surface Периферийные устройства для компьютера Xbox Компьютерные игры HoloLens Surface Hub Гарантии на оборудование Учетная запись и выставление счетов Учетная запись Microsoft Store и выставление счетов Ресурсы Новые возможности Форумы сообщества Администраторы Microsoft 365 Портал для малого бизнеса Для разработчиков Образование Сообщить о мошенничестве с поддержкой Безопасность продуктов Еще Покупка Microsoft 365 Продукты Майкрософт Global Microsoft 365 Teams Windows Xbox Поддержка ПО ПО Приложения для Windows ИИ OneDrive Outlook Переход от Skype в Teams OneNote Microsoft Teams Компьютеры и устройства Компьютеры и устройства Купите Xbox Аксессуары Развлечения Развлечения Xbox Game Pass Ultimate Xbox и игры Компьютерные игры Для бизнеса Для бизнеса Microsoft Security Azure Dynamics 365 Microsoft 365 для бизнеса Microsoft для промышленности Microsoft Power Platform Windows 365 Для разработчиков и ИТ Для разработчиков и ИТ Программа Майкрософт для разработчиков Microsoft Learn Поддержка ИИ-приложений на Marketplace Сообщество Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards Другое Другое Бесплатная загрузка и средства безопасности Образование Лицензирование Посмотреть карту сайта Поиск Поиск справки Нет результатов Отмена Войти Войдите с помощью учетной записи Майкрософт Войдите или создайте учетную запись. Здравствуйте, Выберите другую учетную запись. У вас несколько учетных записей Выберите учетную запись, с помощью которой нужно войти. Связанные темы Безопасность, защита и конфиденциальность Windows Обзор Общие сведения о безопасности, защите и конфиденциальности Безопасность Windows Техническая поддержка по безопасности Windows Обеспечение защиты с помощью безопасности Windows Прежде чем утилизировать, продать или подарить свое устройство с Windows или Xbox Удаление вредоносных программ с компьютера с Windows Безопасность Windows Техническая поддержка по безопасности Windows Просмотр и удаление журнала браузера в Microsoft Edge Удаление файлов cookie и управление ими Безопасное удаление ценного содержимого при переустановке Windows Поиск и блокировка потерянного устройства с Windows Конфиденциальность Windows Техническая поддержка по конфиденциальности Windows Параметры конфиденциальности Windows, используемые в приложениях Просмотр данных на панели мониторинга конфиденциальности Управление файлами cookie в Microsoft Edge: просмотр, разрешение, блокировка, удаление и использование Применяется к Windows 10 Windows 11 Microsoft Edge Файлы cookie — это небольшие фрагменты данных, хранящиеся на вашем устройстве веб-сайтами, которые вы посещаете. Они служат для различных целей, таких как запоминание учетных данных для входа, настройки сайта и отслеживание поведения пользователей. Однако может потребоваться удалить файлы cookie из соображений конфиденциальности или для устранения проблем с просмотром. В этой статье содержатся инструкции по выполнению следующих инструкций: Просмотр всех файлов cookie Разрешить все файлы cookie Разрешить файлы cookie с определенного веб-сайта Блокировка сторонних файлов cookie Блокировать все cookie Блокировка файлов cookie с определенного сайта Удаление всех файлов cookie Удаление файлов cookie определенного сайта Удаление файлов cookie при каждом закрытии браузера Использование файлов cookie для предварительной загрузки страницы для ускорения просмотра Просмотр всех файлов cookie Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie , а затем щелкните Просмотреть все файлы cookie и данные сайта , чтобы просмотреть все сохраненные файлы cookie и связанные сведения о сайте. Разрешить все файлы cookie Разрешив файлы cookie, веб-сайты смогут сохранять и извлекать данные в браузере, что может улучшить работу браузера, запомня ваши предпочтения и данные для входа. Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie и включите переключатель Разрешить сайтам сохранять и считывать данные файлов cookie (рекомендуется), чтобы разрешить все файлы cookie. Разрешение файлов cookie с определенного сайта Разрешив файлы cookie, веб-сайты смогут сохранять и извлекать данные в браузере, что может улучшить работу браузера, запомня ваши предпочтения и данные для входа. Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie и перейдите в раздел Разрешено, чтобы сохранить файлы cookie. Выберите Добавить сайт , чтобы разрешить файлы cookie для каждого сайта, введя URL-адрес сайта. Блокировка сторонних файлов cookie Если вы не хотите, чтобы сторонние сайты сохраняли файлы cookie на вашем компьютере, вы можете заблокировать файлы cookie. Из-за блокировки файлов cookie некоторые страницы могут отображаться неправильно, а также может отображаться сообщение о необходимости разрешить файлы cookie для просмотра сайта. Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie и включите переключатель Блокировать сторонние файлы cookie. Блокировать все cookie Если вы не хотите, чтобы сторонние сайты сохраняли файлы cookie на вашем компьютере, вы можете заблокировать файлы cookie. Из-за блокировки файлов cookie некоторые страницы могут отображаться неправильно, а также может отображаться сообщение о необходимости разрешить файлы cookie для просмотра сайта. Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie и отключите разрешить сайтам сохранять и считывать данные файлов cookie (рекомендуется), чтобы заблокировать все файлы cookie. Блокировка файлов cookie с определенного сайта Microsoft Edge позволяет блокировать файлы cookie с определенного сайта, однако это может помешать правильному отображению некоторых страниц или вы можете получить сообщение с сайта, сообщающее, что вам нужно разрешить файлы cookie для просмотра этого сайта. Чтобы заблокировать файлы cookie с определенного сайта, выполните следующие действия: Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie и перейдите к разделу Не разрешено сохранять и считывать файлы cookie . Выберите Добавить сайт , чтобы заблокировать файлы cookie для каждого сайта, введя URL-адрес сайта. Удаление всех файлов cookie Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Очистить данные браузера , а затем выберите Выбрать, что нужно удалить рядом с пунктом Очистить данные браузера сейчас . В разделе Диапазон времени выберите временной промежуток из списка. Выберите Файлы cookie и другие данные сайтов и нажмите кнопку Удалить сейчас . Примечание: Кроме того, можно удалить файлы cookie, нажав клавиши CTRL + SHIFT + DELETE , а затем перейдя к шагам 4 и 5. Все файлы cookie и другие данные сайта теперь будут удалены за выбранный вами период времени. При этом вы выходите из большинства сайтов. Удаление файлов cookie определенного сайта Откройте браузер Edge, выберите Параметры и другие > Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie , а затем щелкните Просмотреть все файлы cookie и данные сайта и найдите сайт, файлы cookie которого требуется удалить. Нажмите стрелку вниз справа от сайта, файлы cookie которого вы хотите удалить, и выберите Удалить . Файлы cookie для выбранного сайта будут удалены. Повторите это действие для любого сайта, файлы cookie которого вы хотите удалить. Удаление файлов cookie при каждом закрытии браузера Откройте браузер Edge, выберите Параметры и другие > Параметры > Конфиденциальность, поиск и службы . Выберите Очистить данные браузера , а затем выберите Выбрать, что следует очищать при каждом закрытии браузера . Включите переключатель Файлы cookie и другие данные сайтов . После включения этой функции при каждом закрытии браузера Edge удаляются все файлы cookie и другие данные сайта. При этом вы выходите из большинства сайтов. Использование файлов cookie для предварительной загрузки страницы для ускорения просмотра Откройте браузер Edge, выберите Параметры и многое другое в правом верхнем углу окна браузера. Выберите Параметры > Конфиденциальность, поиск и службы . Выберите Файлы cookie и включите переключение страниц предварительной загрузки для ускорения просмотра и поиска. ПОДПИСКА НА RSS-КАНАЛЫ Нужна дополнительная помощь? Нужны дополнительные параметры? Обнаружение Сообщества Свяжитесь с нами Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д. Преимущества подписки на Microsoft 365 Обучение работе с Microsoft 365 Microsoft Security Центр специальных возможностей В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей. Задайте вопрос сообществу Microsoft Сообщество Microsoft Tech Community Участники программы предварительной оценки Windows Участники программы предварительной оценки Microsoft 365 Найдите решения распространенных проблем или получите помощь от агента поддержки. Поддержка в сети Были ли сведения полезными? Да Нет Спасибо! Хотите отправить другие отзывы для Майкрософт? Что мы могли бы сделать лучше? (Отправьте отзыв в корпорацию Майкрософт, чтобы мы могли помочь.) Насколько вы удовлетворены качеством перевода? Что повлияло на вашу оценку? Моя проблема решена Понятные инструкции Понятные сведения Без профессиональной лексики Полезные изображения Качество перевода Не соответствует интерфейсу Неверные инструкции Слишком техническая информация Недостаточно информации Недостаточно изображений Качество перевода Добавите что-нибудь? Это необязательно Отправить отзыв После нажатия кнопки "Отправить" ваш отзыв будет использован для улучшения продуктов и служб Майкрософт. Эти данные будут доступны для сбора ИТ-администратору. Заявление о конфиденциальности. Спасибо за ваш отзыв! × Что нового? Copilot для организаций Microsoft 365 Узнайте больше о продуктах Microsoft Приложения Windows 11 Microsoft Store Профиль учетной записи Центр загрузки Поддержка Microsoft Store Возврат товаров Отслеживание заказа Для образования Microsoft для образования Устройства для образования Microsoft Teams для образования Microsoft 365 для образования Office для образования Подготовка и профессиональное развитие преподавателей Специальные предложения для учащихся и родителей Azure для учащихся Для бизнеса Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Разработчики и ИТ Программа Майкрософт для разработчиков Microsoft Learn Поддержка ИИ-приложений на Marketplace Сообщество Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Компания Вакансии О корпорации Майкрософт Новости компании Политика конфиденциальности Майкрософт Инвесторы Экологическая устойчивость Русский (Россия) Значок отказа для ваших вариантов выбора параметров конфиденциальности Ваши варианты выбора параметров конфиденциальности Значок отказа для ваших вариантов выбора параметров конфиденциальности Ваши варианты выбора параметров конфиденциальности Конфиденциальность медицинских сведений потребителей Связаться с Майкрософт Конфиденциальность Управление файлами cookie Условия использования Товарные знаки Сведения о рекламе © Microsoft 2026 | 2026-01-13T09:30:34 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2keGOX2gxggubPvbD2U4v7iuDC9S3X2Lk7QEf_zG6UCPFlqRgkB8gDW-EZJfw1fiHskSqvBHeZQITabHORPi6bmhZQB9HgmigfedLFjaYt-gvk5RTqrih_kcyIODnVVuMY0a6Vs1-agSJ_ | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:30:34 |
https://support.microsoft.com/nb-no/microsoft-edge/microsoft-edge-nettleserdata-og-personvern-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Microsoft Edge, nettleserdata og personvern - Støtte for Microsoft Gå til hovedinnhold Microsoft Støtte Støtte Støtte Hjem Microsoft 365 Office Produkter Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mer... Enheter Surface PC-tilbehør Xbox PC-spill HoloLens Surface Hub Maskinvaregaranti Konto & fakturering Konto Microsoft Store og fakturering Ressurser Nyheter Fellesskapsforum Microsoft 365-administratorer Portal for små bedrifter Utvikler Utdanning Rapporter en kundestøttesvindel Produktsikkerhet Mer Kjøp Microsoft 365 Alt fra Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Spesialtilbud Liten bedrift Kundestøtte Programvare Programvare Windows-apper AI OneDrive Outlook Overgang fra Skype til Teams OneNote Microsoft Teams PCer og enheter PCer og enheter Kjøp Xbox Tilbehør Underholdning Underholdning Xbox Game Pass Ultimate Xbox og spill PC-spill Bedrift Bedrift Microsoft Sikkerhet Azure Dynamics 365 Microsoft 365 for bedrifter Microsoft Industry Microsoft Power Platform Windows 365 Utvikler og IT Utvikler og IT Microsoft Developer Microsoft Learn Støtte for KI-apper på markedsplassen Microsoft Tech-fellesskap Microsoft Marketplace Visual Studio Marketplace Rewards Annen Annen Microsoft Rewards Gratis nedlastinger og sikkerhet Utdanning Gavekort Lisensiering Vis områdekart Søk Søk etter hjelp Ingen resultater Avbryt Logg på Logg på med Microsoft Logg på, eller opprett en konto. Hei, Velg en annen konto. Du har flere kontoer Velg kontoen du vil logge på med. Microsoft Edge, nettleserdata og personvern Gjelder for Privacy Microsoft Edge Windows 10 Windows 11 Microsoft Edge hjelper deg med å bla gjennom, søke, handle på nettet og mer. Du kan bruke Microsoft Edge, som alle moderne nettlesere, til å innhente og lagre bestemte data på enheten, for eksempel informasjonskapsler, sende informasjon til oss, for eksempel nettleserloggen, for å gjøre opplevelsen så rik, rask og personlig som mulig. Når vi samler inn data, ønsker vi å sikre at det er det riktige valget for deg. Noen er bekymret for at nettleserloggen innhentes. Derfor forteller vi deg hvilke data som er lagret på enheten eller samlet inn av oss. Vi gir deg muligheten til kontrollerer hvilke opplysninger som blir samlet inn. Hvis du vil ha mer informasjon om personvern i Microsoft Edge, anbefaler vi at du går gjennom Personvernerklæringen . Hvilke opplysninger som samles inn eller lagres, og hvorfor Microsoft bruker diagnosedata til å forbedre våre produkter og tjenester. Vi bruker disse opplysningene til å forstå hvordan produktene yter og hvor forbedringer må utføres. Microsoft Edge samler inn et sett med data som kreves for å holde Microsoft Edge sikker, oppdatert og fungerende som forventet. Microsoft tror på og utøver minimalisering av informasjonsinnsamling. Vi prøver bare å samle inn informasjonen vi trenger, og å lagre den bare så lenge det er nødvendig for å levere en tjeneste eller for analyse. I tillegg kan du kontrollere om valgfrie diagnosedata som er knyttet til enheten, skal deles med Microsoft for å løse produktproblemer og bidra til å forbedre Microsoft-produkter og -tjenester. Når du bruker funksjoner og tjenester i Microsoft Edge, sendes diagnosedata om hvordan du bruker disse funksjonene, til Microsoft. Microsoft Edge lagrer nettleserloggen, informasjon om nettsted du besøker, på enheten. Avhengig av innstillingene, sendes nettleserloggen til Microsoft, og vi bruker den til å finne og løse problemer og forbedre produktene og tjenestene våre for alle brukere. Du kan administrere samlingen av valgfrie diagnosedata i nettleseren ved å velge Innstillinger og mer > Innstillinger > Personvern, søk og tjenester > Personvern og slå av eller på Send valgfrie diagnosedata for å forbedre Microsoft-produkter . Dette omfatter informasjon fra testing av nye opplevelser. Start Microsoft Edge på nytt for å fullføre endringen av denne innstillingen. Hvis du aktiverer disse innstillingene, kan disse valgfrie diagnosedataene deles med Microsoft fra andre programmer som bruker Microsoft Edge, for eksempel en app for videostrømming som er vert for Microsoft Edge-nettplattformen for å strømme videoen. Microsoft Edge-nettplattformen vil sende informasjon om hvordan du bruker nettplattformen og nettstedene du besøker i programmet, til Microsoft. Denne datasamlingen bestemmes av den valgfrie innstillingen for diagnosedata under innstillinger for Personvern, søk og tjenester i Microsoft Edge. I Windows 10 bestemmes disse innstillingene av innstillingen for Windows-diagnosedata. Hvis du vil endre innstillingen for diagnosedata, velger du Start > Innstillinger > tilbakemelding om personvern > diagnostikk & . Fra og med 6. mars 2024 samles Diagnosedata fra Microsoft Edge separat fra Windows-diagnosedata på Windows 10 (versjon 22H2 og nyere) og Windows 11 (versjon 23H2 og nyere) enheter i EØS. For disse Windows-versjonene og på alle andre plattformer kan du endre innstillingene i Microsoft Edge ved å velge Innstillinger og mer > Innstillinger > personvern, søk og tjenester . I noen tilfeller kan det hende at innstillingene for diagnosedata administreres av organisasjonen. Når du søker etter noe, kan Microsoft Edge gi forslag til hva du søker etter. Hvis du vil aktivere denne funksjonen, velger du Innstillinger og mer > Innstillinger > personvern, søk og tjenester > Søke- og tilkoblede opplevelser > adresselinjen og søke > Søkeforslag og filtre , og slå på Vis meg søke- og nettstedsforslag ved hjelp av de innskrevne tegnene . Mens du skriver, sendes informasjonen du skriver inn i adresselinjen, til standard søkeleverandør for å gi deg søke- og nettstedsforslag så snart du begynner å skrive. Når du bruker InPrivate-visning eller gjestemodus , samler Microsoft Edge inn litt informasjon om hvordan du bruker nettleseren, avhengig av innstillingene for Windows-diagnosedata eller personverninnstillingene for Microsoft Edge, men automatiske forslag er slått av og informasjon om nettsteder du besøker, samles ikke inn. Microsoft Edge sletter nettleserloggen, informasjonskapsler og nettstedsdata samt passord, adresser og skjemadata når du lukker alle InPrivate-vinduer. Du kan starte en ny InPrivate-økt ved å velge Innstillinger og mer på en datamaskin eller Faner på en mobil enhet. Microsoft Edge har også funksjoner som bidrar til å beskytte deg og innholdet ditt på nettet. Windows Defender SmartScreen blokkerer automatisk nettsteder og innholdsnedlastinger som rapporteres å være skadelige. Windows Defender SmartScreen sjekker adressen til nettsiden du besøker, mot en liste over nettsideadresser som Microsoft mener er pålitelige. Denne listen er lagret på enheten. Adresser som ikke er på enhetens liste, og adressene til filer du laster ned sendes til Microsoft, og kontrolleres mot en jevnlig oppdatert liste over nettsider og nedlastinger som har blitt rapportert til Microsoft som utrygge eller mistenkelige. Hvis du vil fylle ut skjemaer og angi passord raskere, kan du lagre relevant informasjon i Microsoft Edge. Hvis du vil bruke disse funksjonene, lagres informasjonen på enheten. Hvis du har aktivert synkronisering for skjemafyll, for eksempel adresser eller passord, sendes denne informasjonen til Microsoft-skyen og lagres med Microsoft-kontoen for å synkroniseres på tvers av alle påloggede versjoner av Microsoft Edge. Du kan behandle disse dataene fra Innstillinger og mer > Innstillinger > Profiler > Synkronisering . Microsoft Edge deler leserloggen med Microsoft Windows via indeksereren for å integrere nettleseropplevelsen med andre aktiviteter du gjør på enheten. Denne informasjonen lagres lokalt på enheten. Den inneholder nettadresser, en kategori der nettadressen kan være relevant, for eksempel «mest besøkt», «nylig besøkt» eller «nylig lukket», og også en relativ frekvens eller resens i hver kategori. Nettsteder du besøker mens du er i InPrivate-modus, deles ikke. Denne informasjonen er deretter tilgjengelig for andre programmer på enheten, for eksempel startmenyen eller oppgavelinjen. Du kan administrere denne funksjonen ved å velge Innstillinger og mer > Innstillinger > Profiler , og aktivere eller deaktivere Del nettleserdata med andre Windows-funksjoner . Hvis deaktivert, slettes eventuelle tidligere delte data. For å beskytte en del video- og musikkinnhold fra å kopieres lagrer enkelte strømmingsnettsteder DRM-data (Digital Rights Management) på enheten, inkludert en unik ID og medielisenser. Når du går til ett av disse nettstedene, henter det DRM-informasjonen for å kontrollere at du har tillatelse til å bruke innholdet. Microsoft Edge lagrer også informasjonskapsler. Dette er små filer som legges på enheten når du surfer på nettet. Mange nettsteder bruker informasjonskapsler til å lagre informasjon om preferansene og innstillingene dine, som å lagre varer i handlekurven slik at du slipper å legge dem til hver gang du går til nettstedet. Enkelte nettsteder bruker også informasjonskapsler til å innhente informasjon om nettaktiviteten din for å vise deg atferdsbaserte annonser. Microsoft Edge har alternativer du kan bruke til å slette informasjonskapsler og blokkere nettsteder fra å lagre informasjonskapsler i fremtiden. Microsoft Edge vil sende Do Not Track-forespørsler til nettsteder når innstillingen Send Do Not Track-forespørsel er aktivert. Denne innstillingen er tilgjengelig på Innstillinger og mer > Innstillinger > personvern, søk og tjenester > Personvern > Send «Ikke spor»-forespørsler. Nettsteder kan likevel fortsatt spore aktivitetene dine selv om en Ikke spor-forespørsel er sendt. Slik fjerner du data som er innhentet eller lagret av Microsoft Edge Slik fjerner du nettlesingsinformasjon som er lagret på enheten, for eksempel lagrede passord eller informasjonskapsler: I Microsoft Edge velger du Innstillinger og mer > Innstillinger > personvern, søk og tjenester > Fjern nettleserdata . Velg hva du vil fjerne ved siden av Fjern nettleserdata nå. Under Tidsramme , velg et tidsområde. Merk av for hver datatype du vil fjerne, og velg deretter Fjern nå . Hvis du vil, kan du velge Velg hva du vil fjerne hver gang du lukker nettleseren , og velge hvilke datatyper som skal fjernes. Finn ut mer om hva som slettes for hvert element i nettleserloggen . Slik tømmer du nettleserloggen som er innhentet av Microsoft: Hvis du vil se nettleserloggen knyttet til kontoen din, logger du på kontoen din på account.microsoft.com . I tillegg har du også muligheten til å fjerne nettleserdataene som Microsoft har samlet inn, ved hjelp av Microsoft Instrumentbord for personvern . Hvis du vil slette leserloggen og andre diagnosedata som er knyttet til Windows 10 enheten, velger du Start > Innstillinger > Personvern > Diagnostikk & tilbakemelding , og deretter velger du Slett under Slett diagnosedata . Slik fjerner du leserloggen som deles med andre Microsoft-funksjoner på den lokale enheten: Velg Innstillinger og flere > Innstillinger > Profiler i Microsoft Edge. Velg Del nettleserdata med andre Windows-funksjoner . Aktiver/ deaktiver denne innstillingen. Slik administrerer du personverninnstillingene i Microsoft Edge Hvis du vil se gjennom og tilpasse personverninnstillingene, velger du Innstillinger og mer > Innstillinger > personvern, søk og tjenester . > personvern. Hvis du vil lære mer om person vern i Microsoft Edge, kan du lese personvernerklæring for Microsoft Edge . ABONNER PÅ RSS-FEEDER Trenger du mer hjelp? Vil du ha flere alternativer? Oppdag Community Kontakt oss Utforsk abonnementsfordeler, bla gjennom opplæringskurs, finn ut hvordan du sikrer enheten og mer. Abonnementsfordeler for Microsoft 365 Microsoft 365-opplæring Microsoft Sikkerhet Tilgjengelighetssenter Fellesskap hjelper deg med å stille og svare på spørsmål, gi tilbakemelding og høre fra eksperter med stor kunnskap. Spør Microsoft-fellesskapet Teknisk fellesskap for Microsoft Windows Insider-medlemmer Microsoft 365 Insiders Finn løsninger på vanlige problemer, eller få hjelp fra en kundestøtterepresentant. Nettbasert støtte Var denne informasjonen nyttig? Ja Nei Takk! Har du flere tilbakemeldinger til Microsoft? Kan du hjelpe oss med å bli bedre? (Send tilbakemelding til Microsoft, slik at vi kan hjelpe deg.) Hvor fornøyd er du med språkkvaliteten? Hva påvirket opplevelsen din? Løste problemet mitt Tydelige instruksjoner Enkelt å følge Ingen sjargong Bilder hjalp Oversettelseskvalitet Samsvarte ikke med skjermen min Feil instruksjoner For teknisk Ikke nok informasjon Ikke nok bilder Oversettelseskvalitet Har du ytterligere tilbakemeldinger? (Valgfritt) Send tilbakemelding Når du trykker på Send inn, blir tilbakemeldingen brukt til å forbedre Microsoft-produkter og -tjenester. IT-administratoren kan samle inn disse dataene. Personvernerklæring. Takk for tilbakemeldingen! × Nyheter Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organisasjoner Copilot til personlig bruk Microsoft 365 Utforsk Microsoft-produkter Windows 11-apper Microsoft Store Kontoprofil Nedlastingssenter Kundestøtte for Microsoft Store Returer Ordresporing Gjenvinning Kommersielle garantier Utdanning Microsoft Education Enheter for utdanning Microsoft Teams for utdanning Microsoft 365 Education Office Education Lærerutdanning og -utvikling Tilbud for elever og foreldre Azure for students Bedrift Microsoft Sikkerhet Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Liten bedrift Utvikler og IT Microsoft Developer Microsoft Learn Støtte for KI-apper på markedsplassen Microsoft Tech-fellesskap Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Selskap Karriere Om Microsoft Microsoft og personvern Investorer Bærekraft Norsk bokmål (Norge) Ikon for å velge bort personvernvalg Dine personvernvalg Ikon for å velge bort personvernvalg Dine personvernvalg Personvern for forbrukerhelse Kontakt Microsoft Personvern Behandle informasjonskapsler Vilkår for bruk Varemerker Om annonsene © Microsoft 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/573 | LLVM Weekly - #573, December 23rd 2024 LLVM Weekly - #573, December 23rd 2024 Welcome to the five hundred and seventy-third issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Peter Chou blogged about their GSoC project to improve the clang-doc documentation generator . The dates for EuroLLVM and AsiaLLVM 2025 have been announced . EuroLLVM will take place April 14th-16th in Berlin and AsiaLLVM on June 10th in Tokyo. As usual you can check the LLVM calendar for planned events. I won’t list them for the coming week as it seems likely many will be canceled due to holidays/christmas. On the forums Mingming Liu, Snehasish Kumar, and David Xinliang Li started an RFC thread on profile guided static data partitioning , for segrating data in binay ELF sections based on access frequency. LLVM 19.1.6 was released . Jonathan Thackray proposes splitting Clang’s CGbuiltin.cpp noting it is over 23000 lines long and takes over a minute to compile. There was further discussion on shrink wrap save/restore points splitting with notes from a recent RISC-V contributor sync-up on this shared by Alex Bradbury . gbMattN suggests TypeSanitizer should use an ‘outlined’ instrumentation mode by default . Hongren Zheng proposes adding OpAsm{Type,Attr}Interface to MLIR to aid pretty-printing . Suraj Sudhir posted an MLIR RFC on incrementing the TOSA dialect version to v1.0 . Fraser Cormack started an RFC thread on changing the behaviour of elementwise builtins in scalar integer types . LLVM commits The type sanitizer was committed. a487b79 . SDNode::uses() was renamed to SDNode::users() and SDNode::use_iterator was split into user_iterator and use_iterator meaning you can now write range-based for loops using SDUse& and SDNode::uses . 104ad92 , e6b2495 . llvm-mc now accepts a --hex argument to disassemble unprefixed hex bytes. c6ff809 . The RISCVVLOptimizer pass is now enabled by default for RISC-V. 169c32e . The LLVM Security Group was renamed to the LLVM Security Response Group. ccb66bf . The DXILResourceAccess pass was added, transforming resource access via llvm.dx.resource.getpointer to buffer loads and stores. 0fca76d . llvm-exegesis gained support for RISC-V. 8e8692a . A scheduling model was added for the MIPS P8700 RISC-V CPU and the scalar part of the scheduling model for the Tenstorrent Ascalon D8. 3222060 , e934a39 . The unused PoisonChecking utility pass was deleted. 0517772 . The Hexagon backend now supports the Hexagon V75 architecture. 8b37c1c . Clang commits Floating point, pointer, and function types were added to ClangIR. 8ae8a90 . Initial type sanitizer support was added to Clang. c135f6f . Matrix types can now be used in pseudo-destructor expressions, which allows them to be stored in STL containers. eb5c211 . A -Wtautological-compare diagnostic was introduced which warns when a check for pointer addition overflow is always true or false. 6d34cfa . The -ubsan-unique-traps flag was removed as the functionality has been superseded by -fno-sanitize-merge . cb8a90b , 5bb6503 . ThreadSafetyAnalysis was improved to support passing scoped capabilities into functions. c1e7e45 . Other project commits MLIR’s python binding was ported to nanobind, motivated by improved performance. b56d1ec , 5cd4274 . BOLT gained a conservatively safe variant of its identical code folding implementation. 3c357a49 . The Type Sanitizer runtime was committed. 641fbf1 . Flang now supports the UNSIGNED datatype with -funsigned . fc97d2e . LLDB’s progress report mechanism can now be rate limited. 0dbdc23 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/574 | LLVM Weekly - #574, December 30th 2024 LLVM Weekly - #574, December 30th 2024 Welcome to the five hundred and seventy-fourth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . It’s a quiet week this week - I hope everyone is managing to have an enjoyable break! News and articles from around the web and events Fangrui Song blogged about skipping boring functions in debuggers . As usual you can check the LLVM calendar for planned events. I won’t list them for the coming week as it seems likely many will be canceled due to holidays over the new year. On the forums Vitaly Buka proposes removing ‘vptr’ from -fsanitzer=undefined . Markus Böck provided an update on the RFC to make LLVMStructType immutable . Jianjian Guan asked about anonymous function ops in MLIR . LLVM commits As discussed in a previous RFC, a framework was added to LLVM for collecting usage and performance metrics. dbae717 . The Hexagon backend now supports the V79 architecture. c2b89fc . llvm-cov show --binary-counters can be used to indicate 1/0 for covered/uncovered. 223521b . The RISC-V backend gained support for the Qualcomm Xqciac (load-store address calculation) extension. 1557eed . Clang commits Clang now supports the Xtensa target. 2d6e7c2b3 . Initial support for attributes in ClangIR was upstreamed. 8e32959 . Other project commits A C example for the C-compatible wrapper function for a MLIR function was added to the documentation. 698bb5f . Flang enabled loop-versioning for slices. 711419e . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/575 | LLVM Weekly - #575, January 6th 2025 LLVM Weekly - #575, January 6th 2025 Welcome to the five hundred and seventy-fifth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . Eleven years of LLVM Weekly! Happy new year, which of course also means another milestone for LLVM Weekly which has now been running for eleven years, still without missing a week. Thank you for reading! News and articles from around the web and events Nikita Popov has again written a fantastic this year in LLVM blog post . Patrick Jordan Bene’s NESFab project claims to be the best performing high level language compiler targeting the 6502, comparing favourably to LLVM and GCC 6502 backends. There’s also an article about its codegen . (NB: Not a new project, but new to me - spotted on lobste.rs ). According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Johannes Doerfert. Online sync-ups on the following topics: Flang, LLVM/Offload, classic flang, BOLT, OpenMP for flang. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Maksim Levental announced the first release of eudsl, a toolkit for construction of embedded DSLs for targeting MLIR . The linked forum post gives more details about its design and the reason for the current Python emphasis. Javed Absar and collaborators started an MLIR RFC discussion on extending linalg elementwise named ops semantics . Oliver Hunt posted a Clang RFC on an experimental implementation of P2719 - type-aware allocation and deallocation functions . ChuanqiXu is seeking volunteers to help with issues with C++ modules support on Mac M1, Ubuntu, and Windows . Ellis Hoag gave a heads-up about plans to deprecate -forder-file-instrumentation in favour of temporal profiling . Matthias Springer advertised plans to delete the MLIR 1:N dialect conversion driver in April 2025 . Akihiko Odaki started a discussion about pointer type alignment warnings/enforcement in Clang vs UBSan . David Spickett is seeking additional reviews and/or contributed quotes for the upcoming flang-new to flang renaming blog post . LLVM commits InstCombine learned to simplify with.overflow intrinsics with assumption information. This addresses a missed optimisation spotted from Rust’s ‘hashbrown’ hash map implementation. 2adcec7 . llvm-jitlink now uses concurrent linking by default. 0965515 . The FastMathFlags interface in IRBuilder was refactored. a77346b . Assembler support was added to the RISC-V backend for the Qualcomm Xqcicli (conditional load immediate) extension. 532a269 . Clang commits Clang will now canonicalise absolute paths when emitting a dependency file. If I’m not mistaken, this should avoid this long-standing issue filed against ninja . ca2ab74 . Support started to be added for OpenMP offloading to SPIR-V through liboffload. cd19f3f . The AllowShortNamespacesOnASingleLine and WrapNamespaceBodyWithNewlines options were introduced to clang-format. 486ec4b , 1c997fe . clang-format now supports ** in .clang-format-ignore. cd23949 . The majority of the x86 builtin definitions were ported to using TableGen. 2529a8d , a774adb . Other project commits A simple pygments lexer was contributed for MLIR. c7d2370 . The 1:N MLIR dialect conversion driver was marked as deprecated. 80ecbaa . compiler-rt gained an implementation of truncxfhf2 for long double to half conversion. 28ae2ff . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://penneo.com/da/book-a-demo/ | Book en 20-minutters demo - Penneo Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Brancher Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus LOG PÅ Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ BOOK ET MØDE GRATIS PRØVEPERIODE DA EN NO FR NL Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus BOOK ET MØDE GRATIS PRØVEPERIODE LOG PÅ DA EN NO FR NL Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ Bruger du stadig tid på at jagte underskrifter? Med Penneos digitale signeringsløsning sparer du tid, styrker din datasikkerhed og tilbyder dine kunder en intuitiv underskriftsoplevelse med MitID og MitID Erhverv – helt uden papir og post. 7.000.000+ dokumenter blev underskrevet med Penneo i 2024. 3.000+ virksomheder bruger Penneo. Book en 20-minutters demo " * " indikerer påkrævede felter Phone Dette felt er til validering og bør ikke ændres. Fornavn * Efternavn * E-mail * Telefon * BE +32 AD +376 AU +61 AT +43 BG +359 CA +1 HR +385 CY +357 CZ +420 DK +45 EE +372 FO +298 FI +358 FR +33 DE +49 GR +30 GL +299 GG +44 HU +36 IS +354 IE +353 IM +44 IT +39 JP +81 LV +371 LI +423 LT +370 LU +352 MO +853 MK +389 MD +373 MC +377 ME +382 NL +31 NO +47 PL +48 PT +351 RO +40 SM +378 SK +421 ES +34 SE +46 CH +41 UA +380 GB +44 US +1 Single line text * Firmanavn * Dette felt er skjult, når du får vist formularen Land * Land Åland Islands Albania Andorra Australia Austria Belarus Belgium Bosnia and Herzegovina Bulgaria Canada China Croatia Cyprus Czech Republic Denmark Estonia Faroe Islands Finland France Georgia Germany Greece Greenland Hong Kong Hungary Iceland India Indonesia Ireland Isle of Man Israel Italy Japan Latvia Liechtenstein Lithuania Luxembourg Macau Macedonia Moldova Monaco Montenegro Netherlands New Zealand Norway Poland Portugal Romania Russia San Marino Serbia Singapore Slovakia Slovenia Spain Sweden Switzerland Taiwan Turkey Ukraine United Kingdom United States Land Dette felt er skjult, når du får vist formularen Form Dette felt er skjult, når du får vist formularen Language Dette felt er skjult, når du får vist formularen utm_source Dette felt er skjult, når du får vist formularen utm_medium Dette felt er skjult, når du får vist formularen utm_campaign Dette felt er skjult, når du får vist formularen utm_content Dette felt er skjult, når du får vist formularen utm_term Dette felt er skjult, når du får vist formularen gclid Dette felt er skjult, når du får vist formularen gbraid Dette felt er skjult, når du får vist formularen wbraid Dette felt er skjult, når du får vist formularen uuid * Jeg accepterer Penneos privatlivspolitik. * Jeg vil gerne modtage nyheder om Penneo og dets produkter. Jeg kan til enhver tid afmelde mig. Produkter Penneo Sign Priser Integrationer Åben API Validator Hvorfor Penneo Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Ressourcer Vidensunivers Trust Center Produktopdateringer SUPPORT SIGN Hjælpecenter KYC Hjælpecenter Systemstatus Virksomhed Om os Karriere Privatlivspolitik Vilkår Brug af cookies Accessibility Statement Whistleblower Policy Kontakt os PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.