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://aws.amazon.com/jp/waf/ | ウェブアプリケーションファイアウォール - ウェブ API 保護 - AWS WAF - AWS メインコンテンツに移動 Filter: 全て English お問い合わせ AWS Marketplace サポート マイアカウント 検索 Filter: 全て コンソールにサインイン アカウントの作成 AWS ウェブアプリケーションファイアウォール 概要 特徴 料金 開始方法 リソース さらに表示 製品 › セキュリティ、アイデンティティ、コンプライアンス › AWS WAF AWS 無料利用枠で 1,000 万件の Bot Control リクエスト/月を獲得 → AWS WAF 一般的な攻撃からウェブアプリケーションを保護 AWS WAF の使用を開始する AWS WAF の利点 マネージドルールにより時間を節約する マネージドルールで時間を節約し、アプリケーションの構築により多くの時間を費やすことができます。 ボットの監視、ブロック、リミット制限 一般的で蔓延しているボットをより簡単にモニタリング、ブロック、またはレート制限します。 セキュリティ設定ステップを削減する セキュリティデプロイ設定の複雑さとステップを最大 80% 削減する統合インターフェイスを使用して、複雑なセキュリティ設定を迅速化できます。 一元化された実用的な可視性 単一の包括的なインターフェイスは、コアセキュリティ機能と専門的なパートナー保護を組み合わせて、セキュリティの可視性とコントロールを強化します。この統合アプローチにより、セキュリティデータが実用的なインサイトに変換され、運用上のフリクションが排除され、リスク対応が迅速化されます。 セキュリティ体制を強化 事前設定済みの保護パックは、AWS のセキュリティに関する専門知識を活用して、API、PHP アプリケーション、ウェブサービスなどの特定の業界やワークロードタイプ向けの保護テンプレートを即座に提供します。これらのテンプレートは継続的に最適化されているため、デプロイに関する深い専門知識を必要とせずに、最新のセキュリティを実現できます。セキュリティに関するレコメンデーションを継続的に入手し、セキュリティ体制全体を強化しましょう。 AWS WAF を使用すべき理由 AWS WAF では、ボットトラフィックを制御するセキュリティルールを作成し、SQL インジェクションやクロスサイトスクリプティング (XSS) などの一般的な攻撃パターンをブロックすることができます。 再生 ユースケース ウェブトラフィックをフィルタリングする IP アドレス、HTTP ヘッダーと本文、またはカスタム URI などの条件に基づいてウェブリクエストをフィルタリングするルールを作成します。 ルールの作成の詳細 アカウント乗っ取り詐欺を防止する アプリケーションのログインページをモニタリングして、侵害された認証情報を使用したユーザーアカウントへの不正アクセスがないかをモニタリングします。 不正防止の詳細 第 7 層の自動 DDoS 保護 アプリケーション層 (第 7 層) の分散型サービス拒否 (DDoS) イベントを継続的にモニタリングし、数秒以内に自動的に軽減するように設計されています。 迅速なセキュリティ実装 ニーズに合わせて事前設定されたセキュリティデフォルトを 1 画面のインターフェイスでアクティブ化できる、合理化されたガイド付きオンボーディング設定を使用して、自信をもって新しいアプリケーションを起動できます。 セキュリティ体制を強化 エキスパートが厳選したルールパック、統合された可視性、継続的なレコメンデーションを通じて、セキュリティ体制を最適化するための即時の保護を得ることができます。 AWS WAF の使用を開始する AWS WAF の使用を開始する AWS WAF を詳しく見る エキスパートに問い合わせる お問い合わせ AWS アカウントを作成する 学ぶ AWS とは？ クラウドコンピューティングとは? エージェンティック AI とは? クラウドコンピューティングコンセプトのハブ AWS クラウドセキュリティ 最新情報 ブログ プレスリリース リソース 開始方法 トレーニング AWS Trust Center AWS ソリューションライブラリ アーキテクチャセンター 製品と技術上のよくある質問 アナリストレポート AWS パートナー デベロッパー Builder Center SDK とツール AWS での .NET AWS での Python AWS での Java AWS での PHP AWS での JavaScript ヘルプ お問い合わせ サポートチケットを申請する AWS re:Post ナレッジセンター AWS サポートの概要 専門家によるサポートを受ける AWS のアクセシビリティ 法務関連 English 先頭に戻る Amazon は男女雇用機会均等法を順守しています。人種、出身国、性別、性的指向、障がい、年齢、その他の属性によって差別することなく、平等に採用選考の機会を提供しています。 x facebook linkedin instagram twitch youtube podcasts email プライバシー サイト規約 Cookie の詳細設定 © 2026, Amazon Web Services, Inc. or its affiliates.All rights reserved. | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/download.html#source-distribution | Download :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Download Edit this Page Download You can manually download all published Log4j distributions, verify them, and see their licensing information by following the instructions in the Download page of Logging Services . Are you looking for the Log4j installation instructions ? Proceed to Installation . Are you looking for the list of changes associated with a particular release? Proceed to Release notes . Source distribution You can download the source code of the latest Log4j release using the links below: Table 1. Source distribution files Sources apache-log4j-2.25.3-src.zip Checksum apache-log4j-2.25.3-src.zip.sha512 Signature apache-log4j-2.25.3-src.zip.asc Signing keys KEYS Binary distribution A set of binaries of Log4j is available through two main distribution channels: ASF Nexus Repository All the binary artifacts are available on the Apache Software Foundation repository.apache.org Nexus repository . Its content is mirrored to the Maven Central repository . See Components for more information on the GAV coordinates of the artifacts. Binary distribution archive All the artifacts in the ASF Nexus repository are also available in a single ZIP archive: Table 2. Binary distribution files Binaries apache-log4j-2.25.3-bin.zip Checksum apache-log4j-2.25.3-bin.zip.sha512 Signature apache-log4j-2.25.3-bin.zip.asc Signing keys KEYS The authenticity of the Log4j binary release is independently verified by the Reproducible Builds for Maven Central Repository project. You can check the reproducibility status of the artifacts on their org.apache.logging.log4j:log4j RB check page. Software Bill of Materials (SBOM) Each Log4j artifact is accompanied by a Software Bill of Materials (SBOM). See the Download page of Logging Services page for details. Available versions Below you can find the list of available Log4j versions and their associated maintenance status; Active Development, Active Maintenance, End-of-Maintenance, and End-of-Life. Refer to Versioning and maintenance policy for details. Table 3. Maintenance status of selected Log4j versions Version Status Latest release First stable release EOM EOL Notes 3.0.x AD 3.0.0-beta3 2.26.x AD 2.25.x AM 2.25.3 2025-12-15 2.24.x EOM 2.24.3 2024-09-03 2025-06-13 2.12.x EOM 2.12.4 2019-06-23 2021-12-29 Last release supporting Java 7 2.3.x EOM 2.3.2 2015-05-09 2021-12-29 Last release supporting Java 6 1.x EOL 1.2.17 2000-01-08 2014-07-12 2015-08-05 Last release supporting Java 1.4 Click to see all past versions Table 4. Maintenance status of all Log4j versions Version Status Latest release First release EOM EOL 3.0.x AD 3.0.0-beta3 2.26.x AD 2.25.x AM 2.25.2 2025-06-13 2.24.x EOM 2.24.3 2024-09-03 2025-06-13 2.23.x EOM 2.23.1 2024-02-17 2024-09-03 2.22.x EOM 2.22.1 2023-11-17 2024-02-17 2.21.x EOM 2.21.1 2023-10-12 2023-11-17 2.20.x EOM 2.20.0 2023-02-17 2023-10-12 2.19.x EOM 2.19.0 2022-09-09 2023-02-17 2.18.x EOM 2.18.0 2022-06-28 2022-09-09 2.17.x EOM 2.17.2 2021-12-17 2022-06-28 2.16.x EOM 2.16.0 2021-12-13 2021-12-17 2.15.x EOM 2.15.0 2021-12-06 2021-12-13 2.14.x EOM 2.14.1 2020-11-06 2021-12-06 2.13.x EOM 2.13.3 2019-12-11 2020-11-06 2.12.x EOM 2.12.4 2019-06-23 2021-12-29 2.11.x EOM 2.11.2 2018-03-11 2019-06-23 2.10.x EOM 2.10.0 2017-11-18 2018-03-11 2.9.x EOM 2.9.1 2017-08-26 2017-11-18 2.8.x EOM 2.8.2 2017-01-21 2017-08-26 2.7.x EOM 2.7 2016-10-02 2017-01-21 2.6.x EOM 2.6.2 2016-05-25 2016-10-02 2.5.x EOM 2.5 2015-12-06 2016-05-25 2.4.x EOM 2.4.1 2015-09-20 2015-12-06 2.3.x EOM 2.3.2 2015-05-09 2021-12-29 2.2.x EOM 2.2 2015-02-22 2015-05-09 2.1.x EOM 2.1 2014-10-19 2015-02-22 2.0.x EOM 2.0.2 2014-07-12 2014-10-19 1.x EOL 1.2.17 2000-01-08 2014-07-12 2015-08-05 Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://vi-vn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0oK5bRFTTybnDOhYhIZLq01lQic0NLTeIbHIWCatEHpQ1l_XvBDhFFg93NTxyaIWLyhjuKO75pi9dqx6GinsMsCUF3-jXwiN5uEdfkpm7k0xf-caL8YQT8KCcQ_cBSLI1zBjdYsjE75jVT | Facebook Facebook Email hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-cloudfront-trigger-events.html | CloudFront peristiwa yang dapat memicu fungsi Lambda @Edge - Amazon CloudFront CloudFront peristiwa yang dapat memicu fungsi Lambda @Edge - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. CloudFront peristiwa yang dapat memicu fungsi Lambda @Edge Untuk setiap perilaku cache dalam CloudFront distribusi Amazon, Anda dapat menambahkan hingga empat pemicu (asosiasi) yang menyebabkan fungsi Lambda dijalankan saat peristiwa CloudFront tertentu terjadi. CloudFront pemicu dapat didasarkan pada salah satu dari empat CloudFront peristiwa, seperti yang ditunjukkan pada diagram berikut. CloudFront Peristiwa yang dapat digunakan untuk memicu fungsi Lambda @Edge adalah sebagai berikut: Permintaan penampil Fungsi dijalankan ketika CloudFront menerima permintaan dari penampil, sebelum memeriksa untuk melihat apakah objek yang diminta ada dalam CloudFront cache. Fungsi tidak dijalankan dalam kasus berikut: Saat mengambil halaman kesalahan kustom. Ketika CloudFront secara otomatis mengalihkan permintaan HTTP ke HTTPS (ketika nilai Kebijakan protokol penampil adalah Redirect HTTP ke HTTPS). Permintaan asal Fungsi dijalankan hanya ketika CloudFront meneruskan permintaan ke asal Anda. Ketika objek yang diminta ada di CloudFront cache, fungsi tidak dijalankan. Respons asal Fungsi mengeksekusi setelah CloudFront menerima respon dari asal dan sebelum cache objek dalam respon. Perhatikan bahwa fungsi menjalankan bahkan jika kesalahan dikembalikan dari asal. Fungsi tidak dijalankan dalam kasus berikut: Ketika file yang diminta dalam CloudFront cache dan tidak kedaluwarsa. Saat respons dihasilkan dari fungsi yang dipicu oleh peristiwa permintaan asal. Respons penampil Fungsi menjalankan sebelum mengembalikan file yang diminta ke penampil. Perhatikan bahwa fungsi dijalankan terlepas dari apakah file sudah dalam CloudFront cache. Fungsi tidak dijalankan dalam kasus berikut: Saat asal mengembalikan kode status HTTP sebesar 400 atau lebih. Saat halaman kesalahan kustom dikembalikan. Saat respons dihasilkan dari fungsi yang dipicu oleh peristiwa permintaan penampil. Ketika CloudFront secara otomatis mengalihkan permintaan HTTP ke HTTPS (ketika nilai Kebijakan protokol penampil adalah Redirect HTTP ke HTTPS). Saat Anda menambahkan beberapa pemicu ke perilaku cache yang sama, Anda dapat menggunakannya untuk menjalankan fungsi yang sama atau menjalankan fungsi yang berbeda untuk setiap pemicu. Anda juga dapat mengaitkan fungsi yang sama dengan lebih dari satu distribusi. catatan Ketika sebuah CloudFront peristiwa memicu eksekusi fungsi Lambda, fungsi harus selesai CloudFront sebelum dapat melanjutkan. Misalnya, jika fungsi Lambda dipicu oleh peristiwa permintaan CloudFront penampil, tidak CloudFront akan mengembalikan respons ke penampil atau meneruskan permintaan ke asal hingga fungsi Lambda selesai berjalan. Ini berarti bahwa setiap permintaan yang memicu fungsi Lambda meningkatkan latensi untuk permintaan, jadi Anda ingin fungsi tersebut dijalankan secepat mungkin. Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Tambahkan pemicu untuk fungsi Lambda @Edge Pilih acara pemicu 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.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 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-event-request-response.html | Fonctionnement de Lambda@Edge avec les demandes et les réponses - Amazon CloudFront Fonctionnement de Lambda@Edge avec les demandes et les réponses - 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. Fonctionnement de Lambda@Edge avec les demandes et les réponses Lorsque vous associez une CloudFront distribution à une fonction Lambda @Edge, elle CloudFront intercepte les demandes et les réponses à CloudFront des emplacements périphériques. Vous pouvez exécuter des fonctions Lambda lorsque les CloudFront événements suivants se produisent : Quand CloudFront reçoit une demande d'un téléspectateur (demande du téléspectateur) Avant CloudFront de transmettre une demande à l'origine (demande d'origine) Quand CloudFront reçoit une réponse de l'origine (réponse d'origine) Before CloudFront renvoie la réponse au spectateur (réponse du spectateur) Si vous l'utilisez AWS WAF, la demande du visualiseur Lambda @Edge est exécutée une fois les AWS WAF règles appliquées. Pour plus d’informations, consultez Utilisation des demandes et des réponses et Structure d'événement Lambda@Edge . 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 Personnalisation avec Lambda@Edge Comment utiliser Lambda@Edge 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://aws.amazon.com/tr/waf/ | Web Uygulaması Güvenlik Duvarı - Web API Koruması - AWS WAF - AWS Ana İçeriğe Atla Filter: Tüm English Bize ulaşın AWS Marketplace Destek Hesabım Arama Filter: Tüm Konsolda oturum açın Hesap oluşturun AWS Web Uygulaması Güvenlik Duvarı Genel Bakış Özellikler Fiyatlandırma Kullanmaya Başlama Kaynaklar Daha Fazla Ürünler › Güvenlik, Kimlik ve Uygunluk › AWS WAF AWS Ücretsiz Kullanım ile ayda 10 milyon yaygın bot denetimi isteği elde edin → AWS WAF Web uygulamalarınızı yaygın zararlı web yazılımlarına karşı koruyun AWS WAF'yi kullanmaya başlayın AWS WAF'nin Avantajları Yönetilen kurallarla zaman kazanın Yönetilen kurallarla zaman tasarrufu yaparak uygulama geliştirmeye daha fazla vakit ayırın. Botları izleyin, engelleyin ya da oran bazında kısıtlayın Genel ve yaygın robotları daha kolay bir şekilde izleyin, engelleyin veya oran bazında kısıtlayın. Güvenlik yapılandırma adımlarını azaltın Güvenlik dağıtımı yapılandırma karmaşıklığını ve adımlarını %80'e kadar azaltan birleştirilmiş bir arabirimle karmaşık güvenlik yapılandırmasını hızlandırın. Merkezi ve eyleme geçirilebilir görünürlük Tek ve kapsamlı bir arayüz, güvenlik görünürlüğünü ve kontrollerini geliştirmek için temel güvenlik işlevlerini özel iş ortağı korumalarıyla birleştirir. Bu birleşik yaklaşım, güvenlik verilerini eyleme geçirilebilir içgörülere dönüştürerek operasyonel sürtünmeyi ortadan kaldırır ve risk yanıtını hızlandırır. Güvenlik duruşunu güçlendirin Önceden yapılandırılmış koruma paketleri, API'ler, PHP uygulamaları ve web hizmetleri gibi belirli sektörler ve iş yükü türleri için anında koruma şablonları sunmak için AWS'nin güvenlik uzmanlığından yararlanır. Bu şablonlar, derin dağıtım uzmanlığı gerektirmeden güncel güvenlik sağlamak için sürekli olarak optimize edilir. Genel güvenlik duruşunu güçlendirmek için sürekli güvenlik önerileri alın. Neden AWS WAF? AWS WAF ile robot trafiğini kontrol eden ve SQL eklemesi veya siteler arası betik çalıştırma (XSS) gibi yaygın saldırı modellerini engelleyen güvenlik kuralları oluşturabilirsiniz. Oynat Kullanım örnekleri Web trafiğini filtreleyin Web isteklerini IP adresleri, HTTP üst bilgileri ve gövdesi veya özel URI'ler gibi koşullara dayalı olarak filtrelemek için kurallar oluşturun. Kural oluşturma hakkında daha fazla bilgi edinin Hesap ele geçirme dolandırıcılığını önleyin Ele geçirilmiş kimlik bilgilerini kullanarak kullanıcı hesaplarına yetkisiz olarak erişilmesine karşı uygulamanızın oturum açma sayfasını izleyin. Dolandırıcılığı önleme hakkında daha fazla bilgi edinin Otomatik katman 7 DDoS koruması Uygulama katmanı (katman 7) Dağıtılmış Hizmet Reddi (DDoS) olaylarını saniyeler içinde sürekli izlemek ve otomatik olarak azaltmak için tasarlanmıştır. Hızlı güvenlik uygulaması İhtiyaçlarınıza göre uyarlanmış önceden yapılandırılmış güvenlik varsayılanlarını etkinleştirmek için tek sayfalık bir arayüze sahip kolaylaştırılmış rehberli katılım kullanarak yeni uygulamaları güvenle başlatın. Güvenlik duruşunu güçlendirin Uzmanların seçtiği kural paketleri, birleştirilmiş görünürlük ve devam eden öneriler sayesinde güvenlik durumunuzu optimize etmek için anında koruma elde edersiniz. AWS WAF'yi kullanmaya başlayın AWS WAF'yi kullanmaya başlayın AWS WAF’yi keşfedin Bir uzmanla iletişime geçin Bize ulaşın Bir AWS Hesabı Oluşturun Öğrenin AWS Nedir? Bulut Bilgi İşlem nedir? Etken Yapay Zeka nedir? Bulut Bilgi İşlem Kavramları Merkezi AWS Bulut Güvenliği Yenilikler Bloglar Basın Bültenleri Kaynaklar Kullanmaya Başlama Eğitim AWS Güven Merkezi AWS Çözümleri Kitaplığı Mimari Merkezi Ürünler Hakkında ve Teknik SSS'ler Analist Raporları AWS Çözüm Ortakları Geliştiriciler Oluşturucu Merkezi SDK'ler ve Araçlar AWS'de .NET AWS'de Python AWS'de Java AWS'de PHP AWS'de JavaScript Yardım Bize Ulaşın Destek Sorgusu Oluşturun AWS re:Post Bilgi Merkezi AWS Destek’e Genel Bakış Uzman Yardımı Alın AWS Erişilebilirliği Hukuk English Başa dönün Amazon Fırsat Eşitliği İşverenidir: Azınlık/Kadın/Engellilik/Gazi/Cinsiyet Kimliği/Cinsel Yönelim/Yaş. x facebook linkedin instagram twitch youtube podcasts email Gizlilik Site koşulları Çerez Tercihleri © 2026, Amazon Web Services, Inc. veya bağlı kuruluşları. Tüm hakları saklıdır. | 2026-01-13T09:30:34 |
https://aws.amazon.com/cn/waf/ | AWS WAF 网站防火墙 - AWS云服务 跳至主要内容 Filter: 全部 English 联系我们 AWS Marketplace 支持 我的账户 搜索 Filter: 全部 登录控制台 创建账户 AWS Web Application Firewall 概述 功能 定价 入门 资源 更多 产品 › 安全性、身份与合规性 › AWS WAF 使用 AWS Free Tier 每月获得 1000 万次常见机器人控制功能请求 → AWS WAF 保护您的 Web 应用程序免遭常见漏洞的攻击 开始使用 AWS WAF AWS WAF 的优势 使用托管规则节省时间 通过托管式规则节省时间，从而使您能够将更多时间花在构建应用程序上。 监视、阻止机器人程序或限制其速率 更轻松地监控、阻止常见机器人并限制其速率。 减少安全配置步骤 借助一体化界面加速复杂安全配置，将安全部署配置的复杂度和步骤降低多达 80%。 集中且可操作的可见性 单一的综合界面将核心安全功能与专业合作伙伴防护相结合，提升安全可见性与管控能力。这种统一方法能将安全数据转化为可执行的见解，从而消除运维摩擦并加快风险响应速度。 加强安全状况 预配置的防护包利用 AWS 的安全专业知识，为特定行业和工作负载类型（如 API、PHP 应用程序和 Web 服务）提供即时防护模板。这些模板会持续优化，无需深厚的部署专业知识也能确保最新的安全防护。获得持续的安全建议，以加强整体安全状况。 为什么选择 AWS WAF？ 借助 AWS WAF，您可以创建安全规则来控制机器人流量并阻止常见的攻击模式，例如 SQL 注入或跨站脚本攻击（XSS）。 播放 使用案例 筛选 Web 流量 创建规则，根据多种条件（例如 IP 地址、HTTP 标头和正文或自定义 URI）来筛选 Web 流量。 详细了解创建规则 预防账户盗用欺诈 监控应用程序的登录页面，以防止使用已泄露的凭证未经授权访问用户账户。 详细了解欺诈预防 自动第 7 层 DDoS 防护 设计为持续监控，并在几秒钟内自动缓解应用程序层（第 7 层）分布式阻断服务（DDoS）事件。 快速实施安全措施 借助简洁的单页界面引导式设置自信地启动新应用，从而激活为您的需求量身定制的预配置安全默认设置。 加强安全状况 通过专家精选的规则包、整合的可见性和持续的建议，您可以获得即时防护，从而优化安全状况。 开始使用 AWS WAF 开始使用 AWS WAF 探索 AWS WAF 联系专家 联系我们 创建 AWS 账户 了解 什么是 AWS？ 什么是云计算？ 什么是代理式人工智能？ 云计算概念中心 AWS 云安全性 最新资讯 博客 新闻稿 资源 入门 训练 AWS 信任中心 AWS 解决方案库 架构中心 产品和技术常见问题 分析报告 AWS 合作伙伴 开发人员 构建者中心 软件开发工具包与工具 运行于 AWS 上的 .NET 运行于 AWS 上的 Python 运行于 AWS 上的 Java 运行于 AWS 上的 PHP 运行于 AWS 上的 JavaScript 帮助 联系我们 提交支持工单 AWS re:Post Knowledge Center AWS Support 概述 获取专家帮助 AWS 可访问性 法律 English 回到顶部 Amazon 是一个倡导机会均等的雇主：反对少数族裔、妇女、残疾人士、退伍军人、性别认同、性取向和年龄歧视。 x facebook linkedin instagram twitch youtube podcasts email 隐私 网站条款 Cookie 首选项 © 2025, Amazon Web Services, Inc. 或其联属公司。保留所有权利。 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-add-triggers.html | Hinzufügen von Auslösern für eine Lambda@Edge-Funktion - Amazon CloudFront Hinzufügen von Auslösern für eine Lambda@Edge-Funktion - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch 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. Hinzufügen von Auslösern für eine Lambda@Edge-Funktion Ein Lambda @Edge -Trigger ist eine Kombination aus einer CloudFront Verteilung, einem Cache-Verhalten und einem Ereignis, das die Ausführung einer Funktion bewirkt. Sie können beispielsweise einen Trigger erstellen, der bewirkt, dass die Funktion ausgeführt wird, wenn von einem Viewer eine Anfrage für ein bestimmtes Cache-Verhalten CloudFront empfangen wird, das Sie für Ihre Distribution eingerichtet haben. Sie können einen oder mehrere CloudFront Trigger angeben. Tipp Wenn Sie eine CloudFront Verteilung erstellen, geben Sie Einstellungen an, die festlegen, CloudFront wie auf unterschiedliche Anfragen reagiert werden soll. Die Standardeinstellungen werden als Standard-Cacheverhalten für die Distribution bezeichnet. Sie können zusätzliche Cache-Verhaltensweisen einrichten, die definieren, wie unter bestimmten Umständen CloudFront reagiert wird, z. B. wenn eine Anfrage für einen bestimmten Dateityp empfangen wird. Weitere Informationen finden Sie unter Einstellungen für das Cache-Verhalten . Wenn Sie eine Lambda-Funktion neu erstellen, können Sie nur einen Auslöser angeben. Sie können derselben Funktion später weitere Trigger hinzufügen, indem Sie die Lambda-Konsole verwenden oder die Verteilung in der CloudFront Konsole bearbeiten. Die Lambda-Konsole funktioniert gut, wenn Sie einer Funktion für dieselbe CloudFront Distribution weitere Trigger hinzufügen möchten. Die CloudFront Konsole kann besser sein, wenn Sie Trigger für mehrere Distributionen hinzufügen möchten, da es einfacher ist, die Distribution zu finden, die Sie aktualisieren möchten. Sie können auch andere CloudFront Einstellungen gleichzeitig aktualisieren. Themen CloudFront Ereignisse, die eine Lambda @Edge -Funktion auslösen können Auswählen des Ereignisses zur Auslösung der Funktion Hinzufügen von Auslösern zu einer Lambda@Edge-Funktion 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 Bearbeiten einer Lambda-Funktion CloudFront Ereignisse als Auslöser 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://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/standard-logs-reference.html#BasicDistributionFileFormat | Referensi logging standar - Amazon CloudFront Referensi logging standar - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Waktu pengiriman file log Bagaimana permintaan dicatat saat URL atau header permintaan melebihi ukuran maksimum Bidang file log Menganalisis log Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Referensi logging standar Bagian berikut berlaku untuk logging standar (v2) dan logging standar (legacy). Topik Waktu pengiriman file log Bagaimana permintaan dicatat saat URL atau header permintaan melebihi ukuran maksimum Bidang file log Menganalisis log Waktu pengiriman file log CloudFront mengirimkan log untuk distribusi hingga beberapa kali dalam satu jam. Secara umum, file log berisi informasi tentang permintaan yang CloudFront diterima selama periode waktu tertentu. CloudFront biasanya mengirimkan file log untuk periode waktu tersebut ke tujuan Anda dalam waktu satu jam dari peristiwa yang muncul di log. Namun, perhatikan bahwa beberapa atau semua entri file log untuk periode waktu terkadang dapat tertunda hingga 24 jam. Ketika entri log tertunda, CloudFront simpan dalam file log yang nama file termasuk tanggal dan waktu periode di mana permintaan terjadi , bukan tanggal dan waktu ketika file dikirim. Saat membuat file log, CloudFront konsolidasikan informasi untuk distribusi Anda dari semua lokasi tepi yang menerima permintaan untuk objek Anda selama periode waktu yang dicakup oleh file log. CloudFront dapat menyimpan lebih dari satu file untuk jangka waktu tergantung pada berapa banyak permintaan yang CloudFront diterima untuk objek yang terkait dengan distribusi. CloudFront mulai mengirimkan log akses dengan andal sekitar empat jam setelah Anda mengaktifkan pencatatan. Anda mungkin mendapatkan beberapa log akses sebelum waktu tersebut. catatan Jika tidak ada pengguna yang meminta objek Anda selama periode waktu tersebut, Anda tidak akan menerima file log untuk periode tersebut. Bagaimana permintaan dicatat saat URL atau header permintaan melebihi ukuran maksimum Jika ukuran total semua header permintaan, termasuk cookie, melebihi 20 KB, atau jika URL melampaui 8192 byte, CloudFront tidak dapat menguraikan permintaan sepenuhnya dan tidak dapat mencatatnya. Karena permintaan tersebut tidak dicatat, Anda tidak akan melihat kode status kesalahan HTTP kembali. Jika badan permintaan melebihi ukuran maksimum, permintaan akan dicatat, termasuk kode status kesalahan HTTP. Bidang file log File log untuk distribusi berisi 33 bidang. Daftar berikut berisi setiap nama kolom, secara berurutan, bersama dengan deskripsi informasi di bidang tersebut. date Tanggal di mana peristiwa terjadi dalam format YYYY-MM-DD . Misalnya, 2019-06-30 . Tanggal dan waktu berada dalam Waktu Universal Terkoordinasi (UTC). Untuk WebSocket koneksi, ini adalah tanggal ketika koneksi ditutup. time Waktu ketika CloudFront server selesai menanggapi permintaan (dalam UTC), misalnya,. 01:42:39 Untuk WebSocket koneksi, ini adalah waktu ketika koneksi ditutup. x-edge-location Lokasi tepi yang melayani permintaan. Setiap lokasi tepi diidentifikasi oleh kode tiga huruf dan nomor yang ditetapkan secara sewenang-wenang (misalnya, DFW3). Kode tiga huruf biasanya sesuai dengan kode bandara International Air Transport Association (IATA) untuk bandara di dekat lokasi geografis lokasi tepi. (Ringkasan ini mungkin berubah di masa mendatang.) sc-bytes Jumlah total byte yang dikirim server ke penampil sebagai respons terhadap permintaan, termasuk header. Untuk WebSocket dan koneksi gRPC, ini adalah jumlah total byte yang dikirim dari server ke klien melalui koneksi. c-ip Alamat IP penampil yang membuat permintaan, misalnya, 192.0.2.183 atau 2001:0db8:85a3::8a2e:0370:7334 . Jika penampil menggunakan proksi HTTP atau penyeimbang beban untuk mengirim permintaan, nilai bidang ini adalah alamat IP dari perantara atau penyeimbang beban. Lihat juga x-forwarded-for bidang. cs-method Metode permintaan HTTP yang diterima dari penampil. cs(Host) Nama domain CloudFront distribusi (misalnya, d111111abcdef8.cloudfront.net). cs-uri-stem Bagian URL permintaan yang mengidentifikasi jalur dan objek (misalnya, /images/cat.jpg ). Tanda tanya (?) dalam URLs dan string kueri tidak termasuk dalam log. sc-status Berisi salah satu nilai berikut: Kode status HTTP dari respon server (misalnya, 200 ). 000 , yang menunjukkan bahwa penampil menutup koneksi sebelum server dapat merespons permintaan. Jika penampil menutup koneksi setelah server mulai mengirim respons, bidang ini berisi kode status HTTP dari respons yang mulai dikirim server. cs(Referer) Nilai dari Referer header dalam permintaan. Ini adalah nama domain yang membuat permintaan. Perujuk umum termasuk mesin pencari, situs web lain yang terhubung langsung ke objek Anda, dan situs web Anda sendiri. cs(User-Agent) Nilai dari User-Agent header dalam permintaan. User-Agent header mengidentifikasi sumber permintaan, seperti jenis perangkat dan peramban yang mengirimkan permintaan atau, jika permintaan berasal dari mesin pencari, mesin pencari mana. cs-uri-query Bagian utas kueri URL permintaan, jika ada. Ketika URL tidak berisi string kueri, nilai bidang ini adalah tanda hubung (-). Untuk informasi selengkapnya, lihat Konten cache berdasarkan parameter string kueri . cs(Cookie) Cookie header dalam permintaan, termasuk nama—pasangan nilai dan atribut terkait. Jika Anda mengaktifkan pencatatan cookie, CloudFront catat cookie di semua permintaan terlepas dari cookie mana yang Anda pilih untuk diteruskan ke asal. Ketika permintaan tidak menyertakan header cookie, nilai bidang ini adalah tanda hubung (-). Untuk informasi selengkapnya tentang cookie, lihat Konten cache berdasarkan cookie . x-edge-result-type Bagaimana server menggolongkan respons setelah byte terakhir meninggalkan server. Dalam beberapa kasus, jenis hasil dapat berubah antara waktu saat server siap mengirimkan respons dan waktu saat server selesai mengirimkan respons. Lihat juga x-edge-response-result-type bidang. Misalnya, dalam streaming HTTP, seandainya server menemukan segmen aliran di cache. Dalam skenario itu, nilai kolom ini biasanya adalah Hit . Namun, jika penampil menutup koneksi sebelum server mengirimkan seluruh segmen, jenis hasil akhir (dan nilai kolom ini) adalah Error . WebSocket dan koneksi gRPC akan memiliki nilai Miss untuk bidang ini karena kontennya tidak dapat di-cache dan diproksi langsung ke asal. Nilai yang mungkin termasuk: Hit – Server melayani objek ke penampil dari cache. RefreshHit – Server menemukan objek dalam cache tetapi objek telah kedaluwarsa, sehingga server menghubungi asal untuk memverifikasi bahwa cache memiliki versi terbaru dari objek tersebut. Miss – Permintaan tidak dapat dipenuhi oleh objek di dalam cache, sehingga server meneruskan permintaan ke asal dan mengembalikan hasil ke penampil. LimitExceeded — Permintaan ditolak karena CloudFront kuota (sebelumnya disebut sebagai batas) terlampaui. CapacityExceeded Server mengembalikan kode status HTTP 503 karena tidak memiliki kapasitas yang cukup pada saat permintaan untuk melayani objek. Error – Biasanya, ini berarti permintaan tersebut mengakibatkan kesalahan klien (nilai sc-status bidang ada di 4xx atau kesalahan server (nilai sc-status bidang ada di 5xx beragam). Jika nilai sc-status adalah 200 , atau jika nilai bidang ini adalah Error dan nilai dari x-edge-response-result-type bidang tidak Error , artinya permintaan HTTP berhasil tetapi klien terputus sebelum menerima semua byte. Redirect – Server mengarahkan penampil dari HTTP ke HTTPS sesuai dengan pengaturan distribusi. LambdaExecutionError — Fungsi Lambda @Edge yang terkait dengan distribusi tidak selesai karena asosiasi yang salah bentuk, batas waktu fungsi, masalah AWS ketergantungan, atau masalah ketersediaan umum lainnya. x-edge-request-id String buram yang secara unik mengidentifikasi permintaan. CloudFront juga mengirimkan string ini di header x-amz-cf-id respons. x-host-header Nilai yang disertakan oleh penampil dalam Host header permintaan. Jika Anda menggunakan nama CloudFront domain di objek Anda URLs (seperti d111111abcdef8.cloudfront.net), bidang ini berisi nama domain tersebut. Jika Anda menggunakan nama domain alternatif (CNAMEs) di objek Anda URLs (seperti www.example.com), bidang ini berisi nama domain alternatif. Jika Anda menggunakan nama domain alternatif, lihat cs(Host) di bidang 7 untuk nama domain yang terkait dengan distribusi Anda. cs-protocol Protokol permintaan pemirsa ( http , https , grpcs , ws , atau wss ). cs-bytes Jumlah total byte data yang disertakan oleh penampil, termasuk header. Untuk WebSocket dan koneksi gRPC, ini adalah jumlah total byte yang dikirim dari klien ke server pada koneksi. time-taken Jumlah detik (hingga seperseribu detik, misalnya, 0,082) dari saat server menerima permintaan penampil hingga saat server menulis byte terakhir dari respons ke antrian output, yang diukur pada server. Dari perspektif penampil, total waktu untuk mendapatkan respons penuh akan lebih lama dari nilai ini karena latensi jaringan dan buffering TCP. x-forwarded-for Jika penampil menggunakan proksi HTTP atau timbangantor beban untuk mengirim permintaan, nilai c-ip adalah alamat IP dari perantara atau pemukul beban. Dalam hal ini, bidang ini adalah alamat IP penampil yang memulai permintaan. Bidang ini dapat berisi beberapa alamat IP yang dipisahkan koma. Setiap alamat IP dapat berupa IPv4 alamat (misalnya, 192.0.2.183 ) atau IPv6 alamat (misalnya, 2001:0db8:85a3::8a2e:0370:7334 ). Jika penampil tidak menggunakan proksi HTTP atau penyeimbang beban, nilai bidang ini adalah tanda hubung (-). ssl-protocol Ketika permintaan menggunakan HTTPS, bidang ini berisi SSL/TLS protokol yang dinegosiasikan oleh penampil dan server untuk mentransmisikan permintaan dan respons. Untuk daftar nilai yang mungkin, lihat SSL/TLS protokol yang didukung di. Protokol dan sandi yang didukung antara pemirsa dan CloudFront Saat cs-protocol di kolom 17 adalah http , nilai untuk kolom ini adalah tanda hubung (-). ssl-cipher Ketika permintaan menggunakan HTTPS, bidang ini berisi SSL/TLS cipher yang dinegosiasikan oleh penampil dan server untuk mengenkripsi permintaan dan respons. Untuk daftar nilai yang mungkin, lihat SSL/TLS cipher yang didukung di. Protokol dan sandi yang didukung antara pemirsa dan CloudFront Saat cs-protocol di kolom 17 adalah http , nilai untuk kolom ini adalah tanda hubung (-). x-edge-response-result-type Bagaimana server mengklasifikasikan respons tepat sebelum mengembalikan respons ke penampil. Lihat juga x-edge-result-type bidang. Nilai yang mungkin termasuk: Hit – Server melayani objek ke penampil dari cache. RefreshHit – Server menemukan objek dalam cache tetapi objek telah kedaluwarsa, sehingga server menghubungi asal untuk memverifikasi bahwa cache memiliki versi terbaru dari objek tersebut. Miss – Permintaan tidak dapat dipenuhi oleh objek dalam cache, sehingga server meneruskan permintaan ke server asal dan mengembalikan hasil ke penampil. LimitExceeded — Permintaan ditolak karena CloudFront kuota (sebelumnya disebut sebagai batas) terlampaui. CapacityExceeded — Server mengembalikan kesalahan 503 karena tidak memiliki kapasitas yang cukup pada saat permintaan untuk melayani objek. Error – Biasanya, ini berarti permintaan tersebut mengakibatkan kesalahan klien (nilai sc-status bidang ada di 4xx atau kesalahan server (nilai sc-status bidang ada di 5xx beragam). Jika nilai x-edge-result-type adalah Error dan nilai bidang ini tidak Error , klien terputus sebelum menyelesaikan unduhan. Redirect – Server mengarahkan penampil dari HTTP ke HTTPS sesuai dengan pengaturan distribusi. LambdaExecutionError — Fungsi Lambda @Edge yang terkait dengan distribusi tidak selesai karena asosiasi yang salah bentuk, batas waktu fungsi, masalah AWS ketergantungan, atau masalah ketersediaan umum lainnya. cs-protocol-version Versi HTTP yang ditentukan penampil dalam permintaan. Nilai yang mungkin termasuk adalah HTTP/0.9 , HTTP/1.0 , HTTP/1.1 , HTTP/2.0 , dan HTTP/3.0 . fle-status Saat enkripsi tingkat lapangan dikonfigurasi untuk distribusi, bidang ini berisi kode yang menunjukkan apakah badan permintaan berhasil diproses. Ketika server berhasil memproses isi permintaan, mengenkripsi nilai dalam bidang yang ditentukan, dan meneruskan permintaan ke asal, nilai bidang ini adalah Processed . Nilai dari x-edge-result-type masih dapat menunjukkan kesalahan sisi klien atau sisi server dalam kasus ini. Nilai yang mungkin untuk kolom ini meliputi: ForwardedByContentType – Server meneruskan permintaan ke tempat asal tanpa mengurai atau enkripsi karena tidak ada jenis konten yang dikonfigurasi. ForwardedByQueryArgs — Server meneruskan permintaan ke asal tanpa parsing atau enkripsi karena permintaan berisi argumen kueri yang tidak ada dalam konfigurasi untuk enkripsi tingkat lapangan. ForwardedDueToNoProfile – Server meneruskan permintaan ke tempat asal tanpa mengurai atau enkripsi karena tidak ada profil yang ditentukan dalam konfigurasi untuk enkripsi tingkat lapangan. MalformedContentTypeClientError – Server menolak permintaan dan mengembalikan kode status HTTP 400 ke penampil karena nilai Content-Type header dalam format yang tidak valid. MalformedInputClientError – Server menolak permintaan dan mengembalikan kode status HTTP 400 ke penampil karena bodi permintaan dalam format yang tidak valid. MalformedQueryArgsClientError – Server menolak permintaan dan mengembalikan kode status HTTP 400 ke penampil karena argumen kueri kosong atau dalam format yang tidak valid. RejectedByContentType – Server menolak permintaan dan mengembalikan kode status HTTP 400 ke penampil karena tidak ada jenis konten yang ditentukan dalam konfigurasi untuk enkripsi tingkat lapangan. RejectedByQueryArgs – Server menolak permintaan dan mengembalikan kode status HTTP 400 ke penampil karena tidak ada alasan kueri yang ditentukan dalam konfigurasi untuk enkripsi tingkat lapangan. ServerError – Server asal mengembalikan kesalahan. Jika permintaan melebihi kuota enkripsi tingkat lapangan (sebelumnya disebut sebagai batas), bidang ini berisi salah satu kode kesalahan berikut, dan server mengembalikan kode status HTTP 400 ke penampil. Untuk daftar kuota saat ini pada enkripsi tingkat lapangan, lihat Kuotas pada enkripsi tingkat lapangan . FieldLengthLimitClientError – Kolom yang dikonfigurasi untuk dienkripsi melebihi panjang maksimum yang diizinkan. FieldNumberLimitClientError – Permintaan agar distribusi dikonfigurasi untuk mengenkripsi berisi lebih dari jumlah kolom yang diperbolehkan. RequestLengthLimitClientError – Panjang badan permintaan melebihi panjang maksimum yang diperbolehkan ketika enkripsi tingkat lapangan dikonfigurasi. Jika enkripsi tingkat bidang tidak dikonfigurasi untuk distribusi, nilai bidang ini adalah tanda hubung (-). fle-encrypted-fields Jumlah bidang enkripsi tingkat lapangan yang dienkripsi dan diteruskan oleh server ke asal. CloudFront server mengalirkan permintaan yang diproses ke asal saat mereka mengenkripsi data, sehingga bidang ini dapat memiliki nilai meskipun nilainya fle-status adalah kesalahan. Jika enkripsi tingkat bidang tidak dikonfigurasi untuk distribusi, nilai bidang ini adalah tanda hubung (-). c-port Nomor port permintaan dari penampil. time-to-first-byte Jumlah detik antara menerima permintaan dan menulis byte pertama respons, sebagaimana diukur pada server. x-edge-detailed-result-type Bidang ini berisi nilai yang sama dengan x-edge-result-type bidang, kecuali dalam kasus berikut: Ketika objek disajikan ke penampil dari lapisan Origin Shield , bidang ini berisi OriginShieldHit . Ketika objek tidak dalam CloudFront cache dan respons dihasilkan oleh permintaan asal fungsi Lambda @Edge , bidang ini berisi. MissGeneratedResponse Ketika nilai bidang adalah Error , x-edge-result-type bidang ini berisi salah satu nilai berikut dengan informasi lebih lanjut tentang kesalahan: AbortedOrigin – Server mengalami masalah dengan asal usul. ClientCommError – Respons ke penampil terganggu karena masalah komunikasi antara server dan penampil. ClientGeoBlocked — Distribusi dikonfigurasi untuk menolak permintaan dari lokasi geografis pemirsa. ClientHungUpRequest – Penampil berhenti sebelum waktunya saat mengirim permintaan. Error — Terjadi kesalahan yang jenis kesalahannya tidak sesuai dengan kategori lainnya. Jenis kesalahan ini dapat terjadi saat server menjalankan respons kesalahan dari cache. InvalidRequest – Server menerima permintaan yang tidak valid dari penampil. InvalidRequestBlocked – Akses ke sumber daya yang diminta diblokir. InvalidRequestCertificate — Distribusi tidak cocok dengan SSL/TLS sertifikat tempat koneksi HTTPS dibuat. InvalidRequestHeader Permintaan mengandung header yang tidak valid. InvalidRequestMethod – Distribusi tidak dikonfigurasi untuk menangani metode permintaan HTTP yang digunakan. Ini dapat terjadi ketika distribusi hanya mendukung permintaan yang dapat disimpan. OriginCommError — Permintaan habis waktu saat menghubungkan ke asal, atau membaca data dari asal. OriginConnectError — Server tidak dapat terhubung ke asal. OriginContentRangeLengthError — Content-Length Header dalam respons asal tidak cocok dengan panjang di Content-Range header. OriginDnsError — Server tidak dapat menyelesaikan nama domain asal. OriginError - Asal memberikan jawaban yang salah. OriginHeaderTooBigError – Header yang dikembalikan oleh asalnya terlalu besar untuk diproses oleh server edge. OriginInvalidResponseError – Asal memberikan respons tidak valid. OriginReadError — Server tidak bisa membaca dari asalnya. OriginWriteError — Server tidak bisa menulis ke asal. OriginZeroSizeObjectError – Objek seukuran nol yang dikirim dari sumber mengakibatkan kesalahan. SlowReaderOriginError – Penampil lambat untuk membaca pesan yang menyebabkan kesalahan asal. sc-content-type Nilai HTTP Content-Type header respons. sc-content-len Nilai HTTP Content-Length header respons. sc-range-start Saat tanggapan berisi HTTP Content-Range header, kolom ini berisi nilai mulai rentang. sc-range-end Saat tanggapan berisi HTTP Content-Range header, kolom ini berisi nilai akhir rentang. distribution-tenant-id ID penyewa distribusi. connection-id Pengenal unik untuk koneksi TLS. Anda harus mengaktifkan MTL untuk distribusi Anda sebelum Anda bisa mendapatkan informasi untuk bidang ini. Untuk informasi selengkapnya, lihat Penampil Mutual TLS (mTLS) . Berikut ini adalah contoh file log untuk distribusi. #Version: 1.0 #Fields: date time x-edge-location sc-bytes c-ip cs-method cs(Host) cs-uri-stem sc-status cs(Referer) cs(User-Agent) cs-uri-query cs(Cookie) x-edge-result-type x-edge-request-id x-host-header cs-protocol cs-bytes time-taken x-forwarded-for ssl-protocol ssl-cipher x-edge-response-result-type cs-protocol-version fle-status fle-encrypted-fields c-port time-to-first-byte x-edge-detailed-result-type sc-content-type sc-content-len sc-range-start sc-range-end 2019-12-04 21:02:31 LAX1 392 192.0.2.100 GET d111111abcdef8.cloudfront.net /index.html 200 - Mozilla/5.0%20(Windows%20NT%2010.0;%20Win64;%20x64)%20AppleWebKit/537.36%20(KHTML,%20like%20Gecko)%20Chrome/78.0.3904.108%20Safari/537.36 - - Hit SOX4xwn4XV6Q4rgb7XiVGOHms_BGlTAC4KyHmureZmBNrjGdRLiNIQ== d111111abcdef8.cloudfront.net https 23 0.001 - TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 Hit HTTP/2.0 - - 11040 0.001 Hit text/html 78 - - 2019-12-04 21:02:31 LAX1 392 192.0.2.100 GET d111111abcdef8.cloudfront.net /index.html 200 - Mozilla/5.0%20(Windows%20NT%2010.0;%20Win64;%20x64)%20AppleWebKit/537.36%20(KHTML,%20like%20Gecko)%20Chrome/78.0.3904.108%20Safari/537.36 - - Hit k6WGMNkEzR5BEM_SaF47gjtX9zBDO2m349OY2an0QPEaUum1ZOLrow== d111111abcdef8.cloudfront.net https 23 0.000 - TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 Hit HTTP/2.0 - - 11040 0.000 Hit text/html 78 - - 2019-12-04 21:02:31 LAX1 392 192.0.2.100 GET d111111abcdef8.cloudfront.net /index.html 200 - Mozilla/5.0%20(Windows%20NT%2010.0;%20Win64;%20x64)%20AppleWebKit/537.36%20(KHTML,%20like%20Gecko)%20Chrome/78.0.3904.108%20Safari/537.36 - - Hit f37nTMVvnKvV2ZSvEsivup_c2kZ7VXzYdjC-GUQZ5qNs-89BlWazbw== d111111abcdef8.cloudfront.net https 23 0.001 - TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 Hit HTTP/2.0 - - 11040 0.001 Hit text/html 78 - - 2019-12-13 22:36:27 SEA19-C1 900 192.0.2.200 GET d111111abcdef8.cloudfront.net /favicon.ico 502 http://www.example.com/ Mozilla/5.0%20(Windows%20NT%2010.0;%20Win64;%20x64)%20AppleWebKit/537.36%20(KHTML,%20like%20Gecko)%20Chrome/78.0.3904.108%20Safari/537.36 - - Error 1pkpNfBQ39sYMnjjUQjmH2w1wdJnbHYTbag21o_3OfcQgPzdL2RSSQ== www.example.com http 675 0.102 - - - Error HTTP/1.1 - - 25260 0.102 OriginDnsError text/html 507 - - 2019-12-13 22:36:26 SEA19-C1 900 192.0.2.200 GET d111111abcdef8.cloudfront.net / 502 - Mozilla/5.0%20(Windows%20NT%2010.0;%20Win64;%20x64)%20AppleWebKit/537.36%20(KHTML,%20like%20Gecko)%20Chrome/78.0.3904.108%20Safari/537.36 - - Error 3AqrZGCnF_g0-5KOvfA7c9XLcf4YGvMFSeFdIetR1N_2y8jSis8Zxg== www.example.com http 735 0.107 - - - Error HTTP/1.1 - - 3802 0.107 OriginDnsError text/html 507 - - 2019-12-13 22:37:02 SEA19-C2 900 192.0.2.200 GET d111111abcdef8.cloudfront.net / 502 - curl/7.55.1 - - Error kBkDzGnceVtWHqSCqBUqtA_cEs2T3tFUBbnBNkB9El_uVRhHgcZfcw== www.example.com http 387 0.103 - - - Error HTTP/1.1 - - 12644 0.103 OriginDnsError text/html 507 - - Menganalisis log Karena Anda dapat menerima beberapa log akses per jam, kami sarankan Anda menggabungkan semua file log yang Anda terima untuk periode waktu tertentu ke dalam satu file. Anda kemudian dapat menganalisis data untuk periode tersebut dengan lebih akurat dan lengkap. Salah satu cara untuk menganalisis log akses Anda adalah dengan menggunakan Amazon Athena . Athena adalah layanan kueri interaktif yang dapat membantu Anda menganalisis data untuk AWS layanan, termasuk. CloudFront Untuk mempelajari selengkapnya, lihat Menanyakan CloudFront Log Amazon di Panduan Pengguna Amazon Athena . Selain itu, posting AWS blog berikut membahas beberapa cara untuk menganalisis log akses. Amazon CloudFront Request Logging (untuk konten yang dikirimkan melalui HTTP) CloudFront Log yang Ditingkatkan, Sekarang Dengan String Kueri Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Konfigurasikan logging standar (warisan) Gunakan log akses waktu nyata 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-event-structure.html#lambda-event-structure-request | Struktur acara Lambda @Edge - Amazon CloudFront Struktur acara Lambda @Edge - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Pemilihan asal dinamis Permintaan acara Peristiwa respon Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Struktur acara Lambda @Edge Topik berikut menjelaskan objek peristiwa permintaan dan respons yang CloudFront diteruskan ke fungsi Lambda @Edge saat dipicu. Topik Pemilihan asal dinamis Permintaan acara Peristiwa respon Pemilihan asal dinamis Anda dapat menggunakan pola jalur dalam perilaku cache untuk merutekan permintaan ke asal berdasarkan jalur dan nama objek yang diminta, seperti images/*.jpg . Menggunakan Lambda@Edge, Anda juga dapat merutekan permintaan ke asal berdasarkan karakteristik lain, seperti nilai-nilai dalam header permintaan. Ada sejumlah cara agar pemilihan asal dinamis ini dapat berguna. Misalnya, Anda dapat mendistribusikan permintaan lintas asal-usul di area geografis yang berbeda untuk membantu menyeimbangkan beban global. Atau Anda dapat secara selektif merutekan permintaan ke asal-usul berbeda yang masing-masing melayani fungsi tertentu: penanganan bot, optimalisasi SEO, autentikasi, dan sebagainya. Untuk contoh kode yang mendemonstrasikan cara menggunakan fitur ini, lihat Pemilihan asal dinamis berbasis konten - contoh . Dalam peristiwa permintaan CloudFront asal, origin objek dalam struktur peristiwa berisi informasi tentang asal yang akan diarahkan ke permintaan, berdasarkan pola jalur. Anda dapat memperbarui nilai di origin mengajukan keberatan untuk mengirimkan permintaan ke negara asal yang berbeda. Saat Anda memperbarui origin objek, Anda tidak perlu menentukan asal dalam distribusi. Anda juga dapat mengganti objek asal Amazon S3 dengan objek asal kustom, dan sebaliknya. Namun, Anda hanya dapat menentukan asal tunggal per permintaan; asal kustom atau asal Amazon S3, tetapi tidak keduanya. Permintaan acara Topik berikut menunjukkan struktur objek yang CloudFront diteruskan ke fungsi Lambda untuk acara permintaan penampil dan asal . Contoh-contoh ini menunjukkan GET tanpa isi. Berikut ini contoh adalah daftar semua bidang yang mungkin muncul dalam peristiwa permintaan penampil dan asal. Topik Contoh permintaan penampil Contoh permintaan asal Permintaan bidang acara Contoh permintaan penampil Contoh berikut menunjukkan objek acara permintaan penampil. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "viewer-request", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "host": [ { "key": "Host", "value": "d111111abcdef8.cloudfront.net" } ], "user-agent": [ { "key": "User-Agent", "value": "curl/7.66.0" } ], "accept": [ { "key": "accept", "value": "*/*" } ] }, "method": "GET", "querystring": "", "uri": "/" } } } ] } Contoh permintaan asal Contoh berikut menunjukkan objek peristiwa permintaan asal usul. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "origin-request", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "x-forwarded-for": [ { "key": "X-Forwarded-For", "value": "203.0.113.178" } ], "user-agent": [ { "key": "User-Agent", "value": "Amazon CloudFront" } ], "via": [ { "key": "Via", "value": "2.0 2afae0d44e2540f472c0635ab62c232b.cloudfront.net (CloudFront)" } ], "host": [ { "key": "Host", "value": "example.org" } ], "cache-control": [ { "key": "Cache-Control", "value": "no-cache" } ] }, "method": "GET", "origin": { "custom": { "customHeaders": { }, "domainName": "example.org", "keepaliveTimeout": 5, "path": "", "port": 443, "protocol": "https", "readTimeout": 30, "responseCompletionTimeout": 30, "sslProtocols": [ "TLSv1", "TLSv1.1", "TLSv1.2" ] } }, "querystring": "", "uri": "/" } } } ] } Permintaan bidang acara Meminta data objek peristiwa dimuat dalam dua subobjek: config ( Records.cf.config ) and request ( Records.cf.request ). Daftar berikut menjelaskan setiap bidang subobject. Bidang di objek konfigurasi Daftar berikut menjelaskan bidang dalam config objek ( Records.cf.config ). distributionDomainName (hanya baca) Nama domain distribusi yang terkait dengan permintaan. distributionID (hanya baca) ID distribusi yang terkait dengan permintaan. eventType (hanya baca) Jenis pemicu yang terkait dengan permintaan: viewer-request atau origin-request . requestId (hanya baca) String terenkripsi yang secara unik mengidentifikasi permintaan. viewer-to-CloudFront requestId Nilai juga muncul di log CloudFront akses sebagai x-edge-request-id . Untuk informasi selengkapnya, lihat Akses log (log standar) dan Bidang file log . Bidang di objek permintaan Daftar berikut menjelaskan bidang dalam request objek ( Records.cf.request ). clientIp (hanya baca) Alamat IP penampil yang membuat permintaan. Jika penampil menggunakan proksi HTTP atau penyeimbang beban untuk mengirim permintaan, nilainya adalah alamat IP proksi atau pengimbang beban. header (baca/tulis) Header pada permintaan. Perhatikan hal-hal berikut: Kunci dalam headers objek adalah versi huruf kecil nama header HTTP standar. Menggunakan tombol huruf kecil memberi Anda akses huruf kecil ke nilai header. Setiap objek header (misalnya, headers["accept"] atau headers["host"] ) adalah serangkaian pasangan utama-nilai. Untuk header tertentu, larik berisi satu pasangan nilai kunci untuk setiap nilai dalam permintaan. key berisi nama case-sensitive dari header seperti yang muncul dalam permintaan HTTP; misalnya,,, Host User-Agent , X-Forwarded-For Cookie , dan sebagainya. value berisi nilai header sebagaimana muncul dalam permintaan HTTP. Ketika fungsi Lambda Anda menambahkan atau memodifikasi header permintaan dan Anda tidak menyertakan bidang header key , Lambda @Edge secara otomatis menyisipkan header key menggunakan nama header yang Anda berikan. Terlepas dari bagaimana Anda memformat nama header, kunci header yang disisipkan secara otomatis diformat dengan kapitalisasi awal untuk setiap bagian, dipisahkan oleh tanda hubung (-). Misalnya, Anda dapat menambahkan header seperti berikut, tanpa header key : "user-agent": [ { "value": "ExampleCustomUserAgent/1.X.0" } ] Dalam contoh ini, Lambda@Edge secara otomatis memasukkan "key": "User-Agent" . Untuk informasi tentang pembatasan penggunaan header, lihat Pembatasan pada fungsi edge . method (hanya baca) Metode HTTP permintaan. querystring (baca/tulis) String kueri, jika ada, dalam permintaan. Jika permintaan tidak menyertakan string kueri, objek acara masih menyertakan querystring dengan nilai kosong. Untuk informasi selengkapnya tentang string kueri, lihat Konten cache berdasarkan parameter string kueri . uri (baca/tulis) Jalur relatif objek yang diminta. Jika fungsi Lambda Anda memodifikasi uri perhatikan hal-hal berikut: uri nilai harus dimulai dengan garis miring ke depan (/). Saat fungsi mengubah uri yang mengubah objek yang diminta oleh penampil. Ketika fungsi mengubah uri nilai, itu tidak mengubah perilaku cache untuk permintaan atau asal permintaan yang dikirim. body (baca/tulis) Isi permintaan HTTP. body struktur dapat memuat kolom berikut: inputTruncated (hanya baca) Bendera Boolean yang menunjukkan apakah tubuh dijejali Lambda@Edge. Untuk informasi selengkapnya, lihat Pembatasan pada isi permintaan dengan opsi sertakan isi . action (baca/tulis) Tindakan yang ingin Anda lakukan dengan tubuh. Opsi untuk action adalah sebagai berikut: read-only: Ini adalah pengaturan default. Saat mengembalikan respons dari fungsi Lambda, jika action adalah hanya baca, Lambda@Edge mengabaikan setiap perubahan pada encoding atau data . replace: Tentukan ini saat Anda ingin mengganti tubuh yang dikirim ke asal. encoding (baca/tulis) Pengodean untuk tubuh. Saat Lambda@Edge mengekspos tubuh ke fungsi Lambda, pertama-tama tubuh berubah menjadi base64-encoding. Jika Anda memilih replace untuk action untuk mengganti tubuh, Anda dapat memilih untuk menggunakan pengodean base64 (default) atau text . Jika Anda menentukan encoding sebagai base64 tetapi tubuh tidak validbase64, CloudFront mengembalikan kesalahan. data (baca/tulis) Isi konten permintaan. origin (baca/tulis) (hanya peristiwa awal) Asal pengiriman permintaan ke. origin Struktur harus berisi tepat satu asal , yang dapat berupa asal khusus atau asal Amazon S3. Bergantung pada jenis asal yang Anda tentukan (asal kustom atau Amazon S3), Anda harus menentukan bidang berikut dalam permintaan Anda: customHeaders (baca/tulis) (kustom dan berasal dari Amazon S3) (Opsional) Anda dapat menyertakan header khusus dengan permintaan dengan menentukan nama header dan pasangan nilai untuk setiap header kustom. Anda tidak dapat menambahkan header yang tidak diizinkan, dan header dengan nama yang sama tidak dapat hadir. Records.cf.request.headers Catatan tentang header permintaan juga berlaku untuk header kustom. Untuk informasi lebih lanjut, lihat Header khusus yang tidak CloudFront dapat ditambahkan ke permintaan asal dan Pembatasan pada fungsi edge . domainName (baca/tulis) (kustom dan berasal dari Amazon S3) Nama domain asal. Nama domain tidak bisa kosong. Untuk asal kustom – Tentukan nama domain DNS, seperti www.example.com . Nama domain tidak dapat menyertakan titik dua (:), dan tidak bisa menjadi alamat IP. Nama domain dapat terdiri dari hingga 253 karakter. Untuk asal Amazon S3 – Tentukan nama domain DNS bucket Amazon S3, seperti amzn-s3-demo-bucket.s3.eu-west-1.amazonaws.com . Nama bisa sampai 128 karakter dan harus berupa huruf kecil. path (baca/tulis) (kustom dan berasal dari Amazon S3) Jalur direktori di tempat asal permintaan harus menemukan konten. Jalur harus dimulai dengan garis miring (/) tetapi tidak boleh diakhiri dengan satu (misalnya, seharusnya tidak diakhiri dengan example-path/ ). Hanya untuk asal kustom, alur harus dienkode URL dan memiliki panjang maksimum 255 karakter. keepaliveTimeout (baca/tulis) (hanya asal sesuai undang-undang) Berapa lama, dalam hitungan detik, yang CloudFront harus mencoba mempertahankan koneksi ke asal setelah menerima paket terakhir dari respons. Nilainya harus berupa angka dari 1-120, inklusif. port (baca/tulis) (hanya asal sesuai undang-undang) Port yang CloudFront harus terhubung ke asal kustom Anda. Port harus 80, 443, atau nomor dalam kisaran 1024–65535, termasuk. protocol (baca/tulis) (hanya asal sesuai undang-undang) Protokol koneksi yang CloudFront harus digunakan saat menghubungkan ke asal Anda. Nilai dapat berupa http atau https . readTimeout (baca/tulis) (kustom dan berasal dari Amazon S3) Berapa lama, dalam hitungan detik, CloudFront harus menunggu tanggapan setelah mengirim permintaan ke asal Anda. Ini juga menentukan berapa lama CloudFront harus menunggu setelah menerima paket tanggapan sebelum menerima paket berikutnya. Nilainya harus berupa angka dari 1-120, inklusif. Jika Anda membutuhkan kuota yang lebih tinggi, lihat Batas waktu respons per asal . responseCompletionTimeout (baca/tulis) (kustom dan berasal dari Amazon S3) Waktu (dalam detik) permintaan dari CloudFront ke asal dapat tetap terbuka dan menunggu tanggapan. Jika respons lengkap tidak diterima dari asal saat ini, CloudFront akhiri koneksi. Nilai untuk responseCompletionTimeout harus sama dengan atau lebih besar dari nilai untuk readTimeout . Jika Anda menetapkan nilai ini ke 0, itu akan menghapus nilai sebelumnya yang Anda tetapkan dan kembali ke default. Anda juga dapat melakukannya dengan menghapus responseCompletionTimeout bidang dari permintaan acara. sslProtocols (baca/tulis) (hanya asal sesuai undang-undang) SSL/TLS Protokol minimum yang CloudFront dapat digunakan saat membuat koneksi HTTPS dengan asal Anda. Nilai dapat berupa: TLSv1.2 , TLSv1.1 , TLSv1 , atau SSLv3 . authMethod (baca/tulis) (hanya asal-usul Amazon S3) Jika Anda menggunakan identitas akses asal (OAI) , setel bidang ini ke origin-access-identity . Jika Anda tidak menggunakan OAI, atur ke none . Jika Anda mengatur authMethod untuk origin-access-identity , ada beberapa persyaratan: Anda harus menentukan region (lihat bidang berikut). Anda harus menggunakan OAI yang sama ketika Anda mengubah permintaan dari satu asal Amazon S3 ke yang lain. Anda tidak dapat menggunakan OAI saat mengubah permintaan dari asal kustom ke asal Amazon S3. catatan Bidang ini tidak mendukung kontrol akses asal (OAC) . region (baca/tulis) (hanya asal-usul Amazon S3) AWS Wilayah ember Amazon S3 Anda. Ini hanya diperlukan ketika Anda mengatur authMethod untuk origin-access-identity . Peristiwa respon Topik berikut menunjukkan struktur objek yang CloudFront diteruskan ke fungsi Lambda untuk penampil dan peristiwa respons asal . Berikut ini contoh adalah daftar semua bidang yang mungkin muncul di penampil dan kejadian respons asal. Topik Contoh respon asal Contoh respons penampil Bidang acara respons Contoh respon asal Contoh berikut menunjukkan objek peristiwa respons asal usul. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "origin-response", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "x-forwarded-for": [ { "key": "X-Forwarded-For", "value": "203.0.113.178" } ], "user-agent": [ { "key": "User-Agent", "value": "Amazon CloudFront" } ], "via": [ { "key": "Via", "value": "2.0 8f22423015641505b8c857a37450d6c0.cloudfront.net (CloudFront)" } ], "host": [ { "key": "Host", "value": "example.org" } ], "cache-control": [ { "key": "Cache-Control", "value": "no-cache" } ] }, "method": "GET", "origin": { "custom": { "customHeaders": { }, "domainName": "example.org", "keepaliveTimeout": 5, "path": "", "port": 443, "protocol": "https", "readTimeout": 30, "responseCompletionTimeout": 30, "sslProtocols": [ "TLSv1", "TLSv1.1", "TLSv1.2" ] } }, "querystring": "", "uri": "/" }, "response": { "headers": { "access-control-allow-credentials": [ { "key": "Access-Control-Allow-Credentials", "value": "true" } ], "access-control-allow-origin": [ { "key": "Access-Control-Allow-Origin", "value": "*" } ], "date": [ { "key": "Date", "value": "Mon, 13 Jan 2020 20:12:38 GMT" } ], "referrer-policy": [ { "key": "Referrer-Policy", "value": "no-referrer-when-downgrade" } ], "server": [ { "key": "Server", "value": "ExampleCustomOriginServer" } ], "x-content-type-options": [ { "key": "X-Content-Type-Options", "value": "nosniff" } ], "x-frame-options": [ { "key": "X-Frame-Options", "value": "DENY" } ], "x-xss-protection": [ { "key": "X-XSS-Protection", "value": "1; mode=block" } ], "content-type": [ { "key": "Content-Type", "value": "text/html; charset=utf-8" } ], "content-length": [ { "key": "Content-Length", "value": "9593" } ] }, "status": "200", "statusDescription": "OK" } } } ] } Contoh respons penampil Contoh berikut menunjukkan objek acara respons penampil. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "viewer-response", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "host": [ { "key": "Host", "value": "d111111abcdef8.cloudfront.net" } ], "user-agent": [ { "key": "User-Agent", "value": "curl/7.66.0" } ], "accept": [ { "key": "accept", "value": "*/*" } ] }, "method": "GET", "querystring": "", "uri": "/" }, "response": { "headers": { "access-control-allow-credentials": [ { "key": "Access-Control-Allow-Credentials", "value": "true" } ], "access-control-allow-origin": [ { "key": "Access-Control-Allow-Origin", "value": "*" } ], "date": [ { "key": "Date", "value": "Mon, 13 Jan 2020 20:14:56 GMT" } ], "referrer-policy": [ { "key": "Referrer-Policy", "value": "no-referrer-when-downgrade" } ], "server": [ { "key": "Server", "value": "ExampleCustomOriginServer" } ], "x-content-type-options": [ { "key": "X-Content-Type-Options", "value": "nosniff" } ], "x-frame-options": [ { "key": "X-Frame-Options", "value": "DENY" } ], "x-xss-protection": [ { "key": "X-XSS-Protection", "value": "1; mode=block" } ], "age": [ { "key": "Age", "value": "2402" } ], "content-type": [ { "key": "Content-Type", "value": "text/html; charset=utf-8" } ], "content-length": [ { "key": "Content-Length", "value": "9593" } ] }, "status": "200", "statusDescription": "OK" } } } ] } Bidang acara respons Data objek peristiwa respons dimuat dalam tiga subobjek: config ( Records.cf.config ), request ( Records.cf.request ), dan response ( Records.cf.response ). Untuk informasi lebih lanjut tentang bidang di objek permintaan, lihat Bidang di objek permintaan . Daftar berikut menjelaskan bidang dalam config dan response subobjects. Bidang di objek konfigurasi Daftar berikut menjelaskan bidang dalam config objek ( Records.cf.config ). distributionDomainName (hanya baca) Nama domain distribusi yang terkait dengan respons. distributionID (hanya baca) ID distribusi yang terkait dengan respons. eventType (hanya baca) Jenis pemicu yang terkait dengan respons: origin-response atau viewer-response . requestId (hanya baca) String terenkripsi yang secara unik mengidentifikasi viewer-to-CloudFront permintaan yang terkait dengan respons ini. requestId Nilai juga muncul di log CloudFront akses sebagai x-edge-request-id . Untuk informasi selengkapnya, lihat Akses log (log standar) dan Bidang file log . Bidang di objek respons Daftar berikut menjelaskan bidang dalam response objek ( Records.cf.response ). Untuk informasi tentang penggunaan fungsi Lambda@Edge untuk membuat respons HTTP, lihat Hasilkan respons HTTP dalam pemicu permintaan . headers (baca/tulis) Header dalam respons. Perhatikan hal-hal berikut: Kunci dalam headers objek adalah versi huruf kecil nama header HTTP standar. Menggunakan tombol huruf kecil memberi Anda akses huruf kecil ke nilai header. Setiap objek header (misalnya, headers["content-type"] atau headers["content-length"] ) adalah serangkaian pasangan utama-nilai. Untuk header tertentu, larik berisi satu pasangan nilai kunci untuk setiap nilai dalam respons. key berisi nama case-sensitive header seperti yang muncul dalam respons HTTP; misalnya,,, Content-Type Content-Length Cookie , dan sebagainya. value berisi nilai header sebagaimana muncul dalam respons HTTP. Ketika fungsi Lambda Anda menambahkan atau memodifikasi header respons dan Anda tidak menyertakan bidang header key , Lambda @Edge secara otomatis menyisipkan header key menggunakan nama header yang Anda berikan. Terlepas dari bagaimana Anda memformat nama header, kunci header yang disisipkan secara otomatis diformat dengan kapitalisasi awal untuk setiap bagian, dipisahkan oleh tanda hubung (-). Misalnya, Anda dapat menambahkan header seperti berikut, tanpa header key : "content-type": [ { "value": "text/html;charset=UTF-8" } ] Dalam contoh ini, Lambda@Edge secara otomatis memasukkan "key": "Content-Type" . Untuk informasi tentang pembatasan penggunaan header, lihat Pembatasan pada fungsi edge . status Kode status HTTP dari respons. statusDescription Deskripsi status HTTP untuk respons. Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Hapus fungsi dan replika Bekerja dengan permintaan dan tanggapan 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://young-programmers.blogspot.com/search/label/shdh?updated-max=2009-08-23T13:32:00-07:00&max-results=20&start=20&by-date=false | Young Programmers Podcast: shdh skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes No posts with label shdh . Show all posts No posts with label shdh . Show all posts Home Subscribe to: Comments (Atom) About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ▼  2015 (1) ▼  February (1) This Podcast Moves to YouTube ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ►  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:34 |
https://www.youtube.com/watch?v=BZHayxEKKZk&list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3 | 093: PHPRoundtable September 2024 - CLIs and TUIs with PHP for fun and profit - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x01eb7b986644d4a1"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtGVUhCSjJfWlBwOCi4oZjLBjIKCgJLUhIEGgAgXw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRX097zC8DrYDxA3uB_IeUgKy-gsjF4mmM8jHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","videoMetadataCarouselViewModel","carouselTitleViewModel","carouselItemViewModel","textCarouselItemViewModel","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","playlist","playlistPanelVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","menuNavigationItemRenderer","slimMetadataToggleButtonRenderer","toggleButtonRenderer","toggleMenuServiceItemRenderer","playlistLoopButtonRenderer","playlistLoopButtonStateRenderer","notificationActionRenderer","autoplay","liveChatRenderer","liveChatHeaderRenderer","sortFilterSubMenuRenderer","clientSideToggleMenuItemRenderer","playerOverlayRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","playerOverlayVideoDetailsRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","expandableVideoDescriptionBodyRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoAttributeViewModel","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtGVUhCSjJfWlBwOCi4oZjLBjIKCgJLUhIEGgAgXw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=2\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":1,"params":"EAEYATgBYgtCWkhheXhFS0taa2gA2gECCAE%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=2\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":1,"params":"EAEYATgBYgtCWkhheXhFS0taa2gA2gECCAE%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=2\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":1,"params":"EAEYATgBYgtCWkhheXhFS0taa2gA2gECCAE%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=2\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":1,"params":"EAEYAzgBYgtCWkhheXhFS0taa2gA2gECCAE%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=2\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":1,"params":"EAEYAzgBYgtCWkhheXhFS0taa2gA2gECCAE%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=2\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":1,"params":"EAEYAzgBYgtCWkhheXhFS0taa2gA2gECCAE%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=zve_CVB75Bk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=7\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"zve_CVB75Bk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":6,"params":"CMFFEAEYAiAAOAFiC0JaSGF5eEVLS1praADaAQIIAQ%3D%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=zve_CVB75Bk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=7\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"zve_CVB75Bk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":6,"params":"CMFFEAEYAiAAOAFiC0JaSGF5eEVLS1praADaAQIIAQ%3D%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=zve_CVB75Bk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=7\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"zve_CVB75Bk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":6,"params":"CMFFEAEYAiAAOAFiC0JaSGF5eEVLS1praADaAQIIAQ%3D%3D","playerParams":"QAFIAQ%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=zve_CVB75Bk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=7\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"zve_CVB75Bk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":6,"params":"CMFFEAEYBCAAOAFiC0JaSGF5eEVLS1praADaAQIIAQ%3D%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=zve_CVB75Bk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=7\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"zve_CVB75Bk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":6,"params":"CMFFEAEYBCAAOAFiC0JaSGF5eEVLS1praADaAQIIAQ%3D%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjiuoSlmoiSAxXV-EwCHaj9ENkyCGF1dG9wbGF5SJnTqIix2fbIBZoBBQgQEPgdygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=zve_CVB75Bk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026index=7\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"zve_CVB75Bk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","index":6,"params":"CMFFEAEYBCAAOAFiC0JaSGF5eEVLS1praADaAQIIAQ%3D%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"playbackRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"093: PHPRoundtable September 2024 - CLIs and TUIs with PHP for fun and profit"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 325회"},"shortViewCount":{"simpleText":"조회수 325회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC0JaSGF5eEVLS1prGmBFZ3RDV2toaGVYaEZTMHRhYTBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDBKYVNHRjVlRVZMUzFwckwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}}],"trackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"9","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMwCEKVBIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},{"innertubeCommand":{"clickTrackingParams":"CMwCEKVBIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CM0CEPqGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CM0CEPqGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"BZHayxEKKZk"},"likeParams":"Cg0KC0JaSGF5eEVLS1prIAAyCwi5oZjLBhCluu4a"}},"idamTag":"66426"}},"trackingParams":"CM0CEPqGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}}}}}}}]}},"accessibilityText":"다른 사용자 9명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMwCEKVBIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"10","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMsCEKVBIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},{"innertubeCommand":{"clickTrackingParams":"CMsCEKVBIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"BZHayxEKKZk"},"removeLikeParams":"Cg0KC0JaSGF5eEVLS1prGAAqCwi5oZjLBhDP-e8a"}}}]}},"accessibilityText":"다른 사용자 9명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMsCEKVBIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtCWkhheXhFS0taayA-KAE%3D","likeStatusEntity":{"key":"EgtCWkhheXhFS0taayA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMkCEKiPCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}},{"innertubeCommand":{"clickTrackingParams":"CMkCEKiPCSITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMoCEPmGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMoCEPmGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"BZHayxEKKZk"},"dislikeParams":"Cg0KC0JaSGF5eEVLS1prEAAiCwi5oZjLBhDXk_Ea"}},"idamTag":"66425"}},"trackingParams":"CMoCEPmGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMkCEKiPCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMgCEKiPCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}},{"innertubeCommand":{"clickTrackingParams":"CMgCEKiPCSITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"BZHayxEKKZk"},"removeLikeParams":"Cg0KC0JaSGF5eEVLS1prGAAqCwi5oZjLBhDvwvEa"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMgCEKiPCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isTogglingDisabled":true}},"dislikeEntityKey":"EgtCWkhheXhFS0taayA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtCWkhheXhFS0taayD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMYCEOWWARgDIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},{"innertubeCommand":{"clickTrackingParams":"CMYCEOWWARgDIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtCWkhheXhFS0taa6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CMYCEOWWARgDIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CMcCEI5iIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMYCEOWWARgDIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CMQCEOuQCSITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMUCEPuGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DBZHayxEKKZk%2526list%253DPLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMUCEPuGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2lr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=0591dacb110a2999\u0026ip=1.208.108.242\u0026initcwndbps=2996250\u0026mt=1768296317\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CMUCEPuGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}}}}}},"trackingParams":"CMQCEOuQCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMICEOuQCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}},{"innertubeCommand":{"clickTrackingParams":"CMICEOuQCSITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMMCEPuGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DBZHayxEKKZk%2526list%253DPLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMMCEPuGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2lr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=0591dacb110a2999\u0026ip=1.208.108.242\u0026initcwndbps=2996250\u0026mt=1768296317\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CMMCEPuGBCITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMICEOuQCSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","superTitleLink":{"runs":[{"text":"PHPRoundtable","navigationEndpoint":{"clickTrackingParams":"CMECELW0CRgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3"}}}]},"dateText":{"simpleText":"실시간 스트리밍 시작일: 2024. 9. 12."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"스트리밍 시간: 1년 전"}},"simpleText":"스트리밍 시간: 1년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/wl072aZTIH194UeU2wVLlyLEHoZlXyO1TttW9J8wzF0z4CP5BB4_b80LvT5hFlewvDwdTgNEg5I=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/wl072aZTIH194UeU2wVLlyLEHoZlXyO1TttW9J8wzF0z4CP5BB4_b80LvT5hFlewvDwdTgNEg5I=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/wl072aZTIH194UeU2wVLlyLEHoZlXyO1TttW9J8wzF0z4CP5BB4_b80LvT5hFlewvDwdTgNEg5I=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"PHP Architect","navigationEndpoint":{"clickTrackingParams":"CMACEOE5IhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/@Phparch","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCUEzH08rDNBfljD9PGVZujg","canonicalBaseUrl":"/@Phparch"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CMACEOE5IhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/@Phparch","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCUEzH08rDNBfljD9PGVZujg","canonicalBaseUrl":"/@Phparch"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 5.23천명"}},"simpleText":"구독자 5.23천명"},"trackingParams":"CMACEOE5IhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCUEzH08rDNBfljD9PGVZujg","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CLICEJsrIhMI4rqEpZqIkgMV1fhMAh2o_RDZKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"PHP Architect을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"PHP Architect을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. PHP Architect 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CL8CEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. PHP Architect 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. PHP Architect 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CL4CEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. PHP Architect 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CLcCEJf5ASITCOK6hKWaiJIDFdX4TAIdqP0Q2Q==","command":{"clickTrackingParams":"CLcCEJf5ASITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLcCEJf5ASITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CL0CEOy1BBgDIhMI4rqEpZqIkgMV1fhMAh2o_RDZMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQQ_XNlE","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ1VFekgwOHJETkJmbGpEOVBHVlp1amcSAggBGAAgBFITCgIIAxILQlpIYXl4RUtLWmsYAA%3D%3D"}},"trackingParams":"CL0CEOy1BBgDIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CLwCEO21BBgEIhMI4rqEpZqIkgMV1fhMAh2o_RDZMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQQ_XNlE","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ1VFekgwOHJETkJmbGpEOVBHVlp1amcSAggDGAAgBFITCgIIAxILQlpIYXl4RUtLWmsYAA%3D%3D"}},"trackingParams":"CLwCEO21BBgEIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CLgCENuLChgFIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLgCENuLChgFIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLkCEMY4IhMI4rqEpZqIkgMV1fhMAh2o_RDZ","dialogMessages":[{"runs":[{"text":"PHP Architect"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CLsCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZMgV3YXRjaMoBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCUEzH08rDNBfljD9PGVZujg"],"params":"CgIIAxILQlpIYXl4RUtLWmsYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CLsCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLoCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CLgCENuLChgFIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CLICEJsrIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLYCEP2GBCITCOK6hKWaiJIDFdX4TAIdqP0Q2TIJc3Vic2NyaWJlygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DBZHayxEKKZk%2526list%253DPLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3%26continue_action%3DQUFFLUhqbmpHM3lZenotV1pUQVI4LVZRcmhjallGUVRvUXxBQ3Jtc0ttR0Z3Y1FwTjZIbGh5RS1XeTJzbDh3TmJVRUJxbUx3QWZMYU1xQmNsNC1WOXItTGpnOVJ3TnAzS3p1ZzBzY2hKOUJnWUt5WnBEUmJ0WVJYQmNhbEhnamhlUWZkOE9RLUxjTEhqN3hrWHNLWmJrWkFjSzhXcGFsQlZTdllaMW9keXp6OEViRW85bHp6cHFoS2s5WVRscHRsNjQ1dXIyY2xZV3VJVkRia0ZoZXl0ZWp5UXRxUHJ6WW0ybk9XZUYwbmhIZGhodTI\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLYCEP2GBCITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BZHayxEKKZk\u0026list=PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BZHayxEKKZk","playlistId":"PLJPRYJOPv4pTM79W974SZ7AqZ3cMdg5q3","loggingContext":{"vssLoggingContext":{"serializedContextData":"GiJQTEpQUllKT1B2NHBUTTc5Vzk3NFNaN0FxWjNjTWRnNXEz"}},"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2lr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=0591dacb110a2999\u0026ip=1.208.108.242\u0026initcwndbps=2996250\u0026mt=1768296317\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbmpHM3lZenotV1pUQVI4LVZRcmhjallGUVRvUXxBQ3Jtc0ttR0Z3Y1FwTjZIbGh5RS1XeTJzbDh3TmJVRUJxbUx3QWZMYU1xQmNsNC1WOXItTGpnOVJ3TnAzS3p1ZzBzY2hKOUJnWUt5WnBEUmJ0WVJYQmNhbEhnamhlUWZkOE9RLUxjTEhqN3hrWHNLWmJrWkFjSzhXcGFsQlZTdllaMW9keXp6OEViRW85bHp6cHFoS2s5WVRscHRsNjQ1dXIyY2xZV3VJVkRia0ZoZXl0ZWp5UXRxUHJ6WW0ybk9XZUYwbmhIZGhodTI","idamTag":"66429"}},"trackingParams":"CLYCEP2GBCITCOK6hKWaiJIDFdX4TAIdqP0Q2Q=="}}}}}},"subscribedEntityKey":"EhhVQ1VFekgwOHJETkJmbGpEOVBHVlp1amcgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CLICEJsrIhMI4rqEpZqIkgMV1fhMAh2o_RDZKPgdMgV3YXRjaMoBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCUEzH08rDNBfljD9PGVZujg"],"params":"EgIIAxgAIgtCWkhheXhFS0taaw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CLICEJsrIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLICEJsrIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLMCEMY4IhMI4rqEpZqIkgMV1fhMAh2o_RDZ","dialogMessages":[{"runs":[{"text":"PHP Architect"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CLUCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZKPgdMgV3YXRjaMoBBD9c2UQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCUEzH08rDNBfljD9PGVZujg"],"params":"CgIIAxILQlpIYXl4RUtLWmsYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CLUCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLQCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CLECEM2rARgBIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CLECEM2rARgBIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLECEM2rARgBIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CLECEM2rARgBIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Unlock the power of command-line interfaces and text-based user interfaces with PHP in our latest PHPRoundtable episode: ‘CLIs and TUIs with PHP for Fun and Profit.’ Join us as we dive deep into how developers leverage PHP to create robust and interactive CLI and TUI applications that drive productivity and innovation.","styleRuns":[{"startIndex":0,"length":320,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":320,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"videoMetadataCarouselViewModel":{"carouselTitles":[{"carouselTitleViewModel":{"title":"실시간 채팅 다시보기","previousButton":{"buttonViewModel":{"iconName":"CHEVRON_LEFT","accessibilityText":"이전","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLACEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_XSMALL","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"nextButton":{"buttonViewModel":{"iconName":"CHEVRON_RIGHT","accessibilityText":"다음","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CK8CEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_XSMALL","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}}],"carouselItems":[{"carouselItemViewModel":{"itemType":"VIDEO_METADATA_CAROUSEL_PAGINATION_TYPE_LIVE_CHAT_STATIC_TEXT","carouselItem":{"textCarouselItemViewModel":{"iconName":"MESSAGE_BUBBLE_OVERLAP","text":{"content":"실시간 스트리밍 중에 다른 사용자가 이 동영상에 대해 어떤 이야기를 했는지 확인해 보세요."},"onTap":{"innertubeCommand":{"clickTrackingParams":"CK0CEOuICSITCOK6hKWaiJIDFdX4TAIdqP0Q2coBBD9c2UQ=","setLiveChatCollapsedStateAction":{}}},"trackingParams":"CK0CEOuICSITCOK6hKWaiJIDFdX4TAIdqP0Q2Q==","button":{"buttonViewModel":{"title":"패널 열기","onTap":{"innertubeCommand":{"clickTrackingParams":"CK4CEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","setLiveChatCollapsedStateAction":{}}},"style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CK4CEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_XSMALL"}}}}}}]}}],"trackingParams":"CKwCELsvGAMiEwjiuoSlmoiSAxXV-EwCHaj9ENk="}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CKsCELsvGAQiEwjiuoSlmoiSAxXV-EwCHaj9ENnKAQQ_XNlE","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SC0JaSGF5eEVLS1prGAYyJSIRIgtCWkhheXhFS0taazAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CKsCELsvGAQiEwjiuoSlmoiSAxXV-EwCHaj9ENk=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CKoCELovIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/oPz4SYzh47g/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBNx4l3hQQ5Q3FNnsmJCpKFw1x2jA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/oPz4SYzh47g/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB5zVSukQz5X5UP5KwecVDOr9L2Ig","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"icon":{"sources":[{"clientResource":{"imageName":"MUSIC"}}]},"text":"22:40","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"oPz4SYzh47g","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","inlinePlaybackBadgeData":{"replicateAsTimestamp":true},"rendererContext":{"accessibilityContext":{"label":"22분 40초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CKkCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"oPz4SYzh47g","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKkCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CKgCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"oPz4SYzh47g"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKgCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CKECENTEDBgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CKcCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKcCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"oPz4SYzh47g","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CKcCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["oPz4SYzh47g"],"params":"CAQ%3D"}},"videoIds":["oPz4SYzh47g"],"videoCommand":{"clickTrackingParams":"CKcCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=oPz4SYzh47g\u0026pp=0gcJCZgAKgI3ePta","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"oPz4SYzh47g","playerParams":"0gcJCZgAKgI3ePta","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a0fcf8498ce1e3b8\u0026ip=1.208.108.242\u0026initcwndbps=4046250\u0026mt=1768296317\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKcCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKYCEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CKECENTEDBgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"연말 norah jones"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/geqy-kkpUOcWY1ew0pmsJ8k72JRX8-0fgo8Z7vfYjF_GvIJjZJ-oITwqFhXp9_RniRSKK4CHzA=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"천월령陈月玲 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CKECENTEDBgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","commandMetadata":{"webCommandMetadata":{"url":"/@coraline288","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCqIERwIQmiDBT3n2Yndlr4A","canonicalBaseUrl":"/@coraline288"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"천월령陈月玲"}}]},{"metadataParts":[{"text":{"content":"조회수 112만회"}},{"text":{"content":"5년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CKICEPBbIhMI4rqEpZqIkgMV1fhMAh2o_RDZygEEP1zZRA==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CKUCEP6YBBgAIhMI4rqEpZqIkgMV1fhMAh2o_RDZ","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CKUCEP6YBBgAIhMI4rqEpZqI | 2026-01-13T09:30:34 |
https://support.microsoft.com/it-it/microsoft-edge/microsoft-edge-dati-delle-esplorazioni-e-privacy-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Microsoft Edge, dati delle esplorazioni e privacy - Supporto tecnico Microsoft Passa a contenuti principali Microsoft Supporto Supporto Supporto Home Microsoft 365 Office Prodotti Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows altro ... Dispositivi Surface Accessori per PC Xbox Giochi per PC HoloLens Surface Hub Garanzie hardware Account e fatturazione account Microsoft Store e fatturazione Risorse Novità Forum della community Amministratori Microsoft 365 Portale per piccole imprese Sviluppatore Istruzione Segnala una truffa di supporto Sicurezza del prodotto Espandi Acquista Microsoft 365 Tutti i siti Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Offerte Aziende Supporto tecnico Software Software App di Windows IA OneDrive Outlook Passaggio da Skype a Teams OneNote Microsoft Teams Accessori e dispositivi Accessori e dispositivi Acquista i prodotti Xbox Accessori Intrattenimento Intrattenimento Xbox Game Pass Ultimate Xbox e giochi Giochi per PC Business Business Microsoft Security Azure Dynamics 365 Microsoft 365 per le aziende Microsoft Industry Microsoft Power Platform Windows 365 Sviluppatori e IT Sviluppatori e IT Sviluppatore Microsoft Microsoft Learn Supporto per le app del marketplace di IA Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Altro Altro Microsoft Rewards Download gratuiti e sicurezza Formazione Carte regalo Licensing Visualizza mappa del sito Cerca Richiedi assistenza Nessun risultato Annulla Accedi Accedi con Microsoft Accedi o crea un account. Salve, Seleziona un altro account. Hai più account Scegli l'account con cui vuoi accedere. Microsoft Edge, dati delle esplorazioni e privacy Si applica a Privacy Microsoft Edge Windows 10 Windows 11 Microsoft Edge consente di esplorare, cercare, effettuare acquisti online e altro ancora. Come tutti i browser moderni, Microsoft Edge consente di raccogliere e archiviare specifici dati nel dispositivo (ad esempio i cookie) e di inviare informazioni a Microsoft, quali la cronologia esplorazioni, per rendere l'esperienza quanto più ricca, veloce e personale possibile. Ogni volta che raccogliamo dati, vogliamo essere certi che sia la scelta giusta per te. Alcune persone si preoccupano del fatto che vengano raccolti dati relativi alla cronologia esplorazioni del Web. Ecco perché ti indichiamo quali dati vengono archiviati nel tuo dispositivo o raccolti da noi. Puoi scegliere di controllare quali dati possono essere raccolti. Per altre informazioni sulla privacy in Microsoft Edge, ti consigliamo di prendere visione dell’ Informativa sulla privacy . Quali dati vengono raccolti o archiviati e perché Microsoft utilizza i dati di diagnostica per migliorare i propri prodotti e servizi. Usiamo questi dati per comprendere meglio le prestazioni dei nostri prodotti e dove devono essere apportati miglioramenti. Microsoft Edge raccoglie un insieme di dati di diagnostica obbligatori per mantenere Microsoft Edge protetto, aggiornato e operativo come previsto. Microsoft crede nel massimo contenimento della raccolta delle informazioni e mette in pratica questo principio. Ci impegniamo a raccogliere solo le informazioni di cui abbiamo bisogno e a archiviarle solo per il tempo necessario per fornire un servizio o per l'analisi. Inoltre, puoi controllare se i dati di diagnostica facoltativi associati al tuo dispositivo vengono condivisi con Microsoft per risolvere i problemi relativi ai prodotti e contribuire al miglioramento dei prodotti e servizi Microsoft. Mentre usi le funzionalità e i servizi in Microsoft Edge, i dati di diagnostica sulle modalità di utilizzo di queste funzionalità vengono inviati a Microsoft. Microsoft Edge salva nel dispositivo la cronologia esplorazioni ossia le informazioni sui siti Web visitati. A seconda delle impostazioni, la cronologia esplorazioni viene inviata a Microsoft, per individuare i problemi e risolverli e per migliorare i prodotti e i servizi per tutti gli utenti. Puoi gestire la raccolta di dati di diagnostica facoltativi nel browser selezionando Impostazioni e altro > Impostazioni > Privacy, ricerca e servizi > Privacy e attivando o disattivando Invia dati di diagnostica facoltativi per migliorare i prodotti Microsoft . Ciò include i dati provenienti dai test delle nuove esperienze. Per completare la modifica di questa impostazione, riavvia Microsoft Edge. Se abiliti queste impostazioni, consenti la condivisione dei dati di diagnostica facoltativi con Microsoft da parte di altre applicazioni tramite Microsoft Edge, ad esempio un'app per la riproduzione in streaming di video che ospita la piattaforma Web di Microsoft Edge per riprodurre in streaming il video. La piattaforma Web di Microsoft Edge invierà informazioni sull’utilizzo della piattaforma Web e i siti visitati nell'applicazione a Microsoft. La raccolta dei dati è determinata dalle impostazioni dei dati di diagnostica facoltativi nelle impostazioni relative alla privacy, alla ricerca e ai servizi di Microsoft Edge. Su Windows 10, queste impostazioni sono determinate dall’impostazione relativa alla diagnostica Windows. Per modificare l'impostazione dei dati di diagnostica, seleziona Start > Settings > Privacy > Diagnostics & feedback . A partire dal 6 marzo 2024, i dati di diagnostica di Microsoft Edge vengono raccolti separatamente dai dati di diagnostica Windows in dispositivi Windows 10 (versione 22H2 e successiva) e Windows 11 (versione 23H2 e successive) nello Spazio economico europeo. Per queste versioni di Windows e in tutte le altre piattaforme, puoi modificare le impostazioni in Microsoft Edge selezionando Impostazioni e altro > Impostazioni > Privacy, ricerca e servizi . In alcuni casi, le impostazioni dei dati di diagnostica potrebbero essere gestite dall'organizzazione. Quando cerchi qualcosa, Microsoft Edge può fornire suggerimenti su ciò che stai cercando. Per attivare questa funzionalità, seleziona Impostazioni e altro > Impostazioni > Privacy, ricerca e servizi > La ricerca e le esperienze connesse > barra degli indirizzi e > i filtri e suggerimenti per la ricerca e attiva Mostra suggerimenti per la ricerca e i siti usando i caratteri digitati . Quando inizi a digitare, le informazioni che immetti nella barra degli indirizzi vengono inviate al provider di ricerca predefinito per offrirti suggerimenti immediati per le ricerche e i siti Web. Quando usi l'esplorazione InPrivate o la modalità guest , Microsoft Edge raccoglie alcune informazioni su come usi il browser a seconda dell'impostazione dei dati di diagnostica Windows o delle impostazioni di privacy di Microsoft Edge, ma i suggerimenti automatici sono disattivati e le informazioni sui siti Web che visiti non vengono raccolte. Microsoft Edge eliminerà la cronologia esplorazioni, i cookie e i dati dei siti nonché le password, gli indirizzi e i dati dei moduli quando chiudi tutte le finestre InPrivate. Puoi avviare una nuova sessione InPrivate selezionando Impostazioni e altro su un computer o Schede su un dispositivo mobile. Inoltre, Microsoft Edge include funzionalità per garantire la tua sicurezza online, oltre che dei tuoi contenuti. Windows Defender SmartScreen blocca automaticamente i siti Web e i download di contenuti ritenuti dannosi. Windows Defender SmartScreen verifica l'indirizzo della pagina Web visitata rispetto a un elenco di indirizzi di pagine Web archiviato nel dispositivo che Microsoft ritiene legittimi. Gli indirizzi non presenti nell'elenco del dispositivo e gli indirizzi dei file scaricati verranno inviati a Microsoft e confrontati con un elenco aggiornato di frequente di pagine Web e download segnalati a Microsoft come non sicuri o sospetti. Per velocizzare le attività ripetitive come la compilazione dei moduli e l'immissione delle password, Microsoft Edge consente di salvare le informazioni in modo da agevolare le operazioni. Se scegli di usare queste funzionalità, Microsoft Edge archivia le informazioni nel dispositivo. Se hai attivato la sincronizzazione per il riempimento dei moduli come indirizzi o password, queste informazioni verranno inviate al cloud Microsoft e archiviate con il tuo account Microsoft per essere sincronizzate in tutte le versioni di Microsoft Edge a cui hai eseguito l'accesso. È possibile gestire questi dati da Impostazioni e altri > Impostazioni > Profili > Sincronizzazione . Per integrare la tua esperienza di esplorazione con altre attività eseguite nel tuo dispositivo, Microsoft Edge condivide la cronologia esplorazioni con Microsoft Windows tramite il relativo indicizzatore. Queste informazioni sono archiviate localmente nel dispositivo. Include gli URL, una categoria in cui l'URL potrebbe essere pertinente, ad esempio "più visitata", "visitata di recente" o "chiusa di recente" e anche una frequenza o una correttezza relativa all'interno di ogni categoria. I siti Web visitati in modalità InPrivate non verranno condivisi. Queste informazioni sono quindi disponibili per altre applicazioni nel dispositivo, ad esempio il menu Start o la barra delle applicazioni. Puoi gestire questa funzionalità selezionando Impostazioni e altro > Impostazioni > Profili e attivando o disattivando Condividi i dati delle esplorazioni con altre funzionalità di Windows . Se disattivata, tutti i dati condivisi in precedenza verranno eliminati. Per proteggere dalla copia determinati contenuti video e musicali, alcuni siti Web di streaming archiviano i dati DRM (Digital Rights Management) nel tuo dispositivo, incluso un identificatore (ID) univoco e licenze per i contenuti multimediali. Quando visiti uno di questi siti Web, questo recupera le informazioni DRM per verificare che tu disponga dell'autorizzazione per l'uso del contenuto. Microsoft Edge archivia inoltre i cookie, piccoli file che vengono memorizzati nel tuo dispositivo durante l'esplorazione del Web. Molti siti Web utilizzano i cookie per memorizzare informazioni sulle tue preferenze e impostazioni, ad esempio il salvataggio degli articoli nel carrello così da non dover aggiungerli di nuovo a ogni visita. Alcuni siti Web usano inoltre i cookie per raccogliere informazioni sulle tue attività online in modo da visualizzare annunci pubblicitari basati sui tuoi interessi. Microsoft Edge offre opzioni che consentono di cancellare i cookie e impedire ai siti Web di salvare i cookie in futuro. Microsoft Edge invierà le richieste Non tenere traccia ai siti Web quando l'impostazione Invia richieste Non tenere traccia è attivata. Questa impostazione è disponibile in Impostazioni e altre > Impostazioni > privacy, ricerca e servizi > privacy > inviare richieste "Non tenere traccia". I siti Web possono comunque tenere traccia delle tue attività anche quando viene inviata una richiesta Non tenere traccia. Come cancellare i dati raccolti o archiviati da Microsoft Edge Per cancellare le informazioni sulle esplorazioni archiviate nel dispositivo, come le password salvate o i cookie: In Microsoft Edge seleziona Impostazioni e altro > Impostazioni > Privacy, ricerca e servizi > Cancella dati delle esplorazioni . Seleziona Scegli gli elementi da cancellare accanto a Cancella i dati delle esplorazioni ora. In Intervallo di tempo scegli un intervallo di tempo. Seleziona la casella di controllo accanto a ogni tipo di dati che vuoi cancellare e quindi seleziona Cancella ora . Se vuoi, puoi selezionare Scegli cosa cancellare ogni volta che chiudi il browser e scegliere quali tipi di dati devono essere cancellati. Altre informazioni su ciò che viene eliminato per ogni elemento nella cronologia del browser . Per cancellare la cronologia esplorazioni raccolta da Microsoft: Per visualizzare la cronologia delle esplorazioni associate al tuo account, accedi al tuo account all’indirizzo account.microsoft.com . Inoltre, puoi scegliere di cancellare i dati delle esplorazioni che Microsoft ha raccolto utilizzando la Dashboard di privacy Microsoft . Per eliminare la cronologia esplorazioni e altri dati di diagnostica associati al dispositivo Windows 10, seleziona Start > Settings > Privacy > Diagnostics & feedback e quindi seleziona Elimina in Elimina dati di diagnostica . Per cancellare la cronologia esplorazioni condivisa con altre funzionalità Microsoft nel dispositivo locale: In Microsoft Edge seleziona Impostazioni e altro > Impostazioni > Profili . Seleziona Condividi i dati delle esplorazioni con altre funzionalità di Windows . Disattiva questa impostazione. Come gestire le impostazioni di privacy in Microsoft Edge Per rivedere e personalizzare le impostazioni di privacy, seleziona Impostazioni e altro > Impostazioni > Privacy, ricerca e servizi . > Privacy. Per altre informazioni sulla privacy in Microsoft Edge, consulta il white paper sulla privacy di Microsoft Edge . SOTTOSCRIVI FEED RSS Serve aiuto? Vuoi altre opzioni? Individua Community Contattaci Esplorare i vantaggi dell'abbonamento e i corsi di formazione, scoprire come proteggere il dispositivo e molto altro ancora. Vantaggi dell'abbonamento a Microsoft 365 Formazione su Microsoft 365 Microsoft Security Centro accessibilità Le community aiutano a porre e a rispondere alle domande, a fornire feedback e ad ascoltare gli esperti con approfondite conoscenze. Chiedi alla community Microsoft Microsoft Tech Community Partecipanti al Programma Windows Insider Partecipanti al Programma Insider di Microsoft 365 Trovare soluzioni ai problemi comuni o ottenere assistenza da un agente di supporto. Supporto online Queste informazioni sono risultate utili? Sì No Grazie! Altri feedback per Microsoft? Puoi aiutarci a migliorare? (Invia feedback a Microsoft per consentirci di aiutarti.) Come valuti la qualità della lingua? Cosa ha influito sulla tua esperienza? Il problema è stato risolto Cancella istruzioni Facile da seguire Nessun linguaggio gergale Immagini utili Qualità della traduzione Non adatto al mio schermo Istruzioni non corrette Troppo tecnico Informazioni insufficienti Immagini insufficienti Qualità della traduzione Altri commenti e suggerimenti? (Facoltativo) Invia feedback Premendo Inviare, il tuo feedback verrà usato per migliorare i prodotti e i servizi Microsoft. L'amministratore IT potrà raccogliere questi dati. Informativa sulla privacy. Grazie per il feedback! × Le novità Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot per le organizzazioni Copilot per l'utilizzo personale Microsoft 365 Esplora i prodotti Microsoft App di Windows 11 Microsoft Store Profilo account Download Center Supporto Microsoft Store Resi Monitoraggio ordini Riciclaggio Garanzie commerciali Formazione Microsoft Education Dispositivi per l'istruzione Microsoft Teams per l'istruzione Microsoft 365 Education Office Education Formazione e sviluppo per gli insegnanti Offerte per studenti e genitori Azure per studenti Aziende Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Piccole imprese Sviluppatori e IT Sviluppatore Microsoft Microsoft Learn Supporto per le app del marketplace di IA Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Azienda Opportunità di carriera Informazioni su Microsoft Notizie aziendali Privacy in Microsoft Investitori Accessibilità Sostenibilità Italiano (Italia) Icona di rifiuto esplicito delle scelte di privacy Le tue scelte sulla privacy Icona di rifiuto esplicito delle scelte di privacy Le tue scelte sulla privacy Privacy per l'integrità dei consumer Riferimenti societari Contatta Microsoft Privacy Gestisci i cookie Condizioni per l'utilizzo Marchi Informazioni sulle inserzioni EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://vi-vn.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 hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/es_es/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html | Almacenamiento en caché de contenido en función de parámetros de cadenas de consulta - Amazon CloudFront Almacenamiento en caché de contenido en función de parámetros de cadenas de consulta - Amazon CloudFront Documentación Amazon CloudFront Guía para desarrolladores Configuración de la consola y de la API para el reenvío de cadenas de consulta y almacenamiento en caché Optimización del almacenamiento en caché Parámetros de cadena de consulta y registros estándar de CloudFront (registros de acceso) Almacenamiento en caché de contenido en función de parámetros de cadenas de consulta Algunas aplicaciones web utilizan cadenas de consulta para enviar información al origen. Una cadena de consulta es la parte de una solicitud web que aparece después de un carácter ? y puede contener uno o varios parámetros, separados por caracteres & . En el siguiente ejemplo, la cadena de consulta incluye dos parámetros, color=red y size=large : https://d111111abcdef8.cloudfront.net/images/image.jpg? color=red&size=large Para distribuciones, puede elegir si desea que CloudFront reenvíe cadenas de consultas al origen y si desea almacenar en caché el contenido en función de todos los parámetros o de los parámetros seleccionados. ¿Por qué podría resultar útil? Considere el siguiente ejemplo. Supongamos que su sitio web está disponible en cinco idiomas. La estructura de directorios y los nombres de archivo de las cinco versiones del sitio web son idénticos. Cuando un usuario consulta el sitio web, las solicitudes que se reenvían a CloudFront incluyen un parámetro de cadena de consulta de idioma en función del idioma elegido por el usuario. Puede configurar CloudFront para reenviar cadenas de consulta al origen y almacenar en caché en función del parámetro de idioma. Si configura el servidor web para devolver la versión de una página determinada que se corresponda con el idioma seleccionado, CloudFront almacena en la caché cada versión del idioma por separado, en función del valor del parámetro de cadena de consulta del idioma. En este ejemplo, si la página principal para el sitio web es main.html , las siguientes cinco solicitudes hacen que CloudFront almacene cinco veces en la caché main.html , una vez por cada valor de parámetro de cadena de consulta de idioma: https://d111111abcdef8.cloudfront.net/main.html? language=de https://d111111abcdef8.cloudfront.net/main.html? language=en https://d111111abcdef8.cloudfront.net/main.html? language=es https://d111111abcdef8.cloudfront.net/main.html? language=fr https://d111111abcdef8.cloudfront.net/main.html? language=jp Tenga en cuenta lo siguiente: Algunos servidores HTTP no procesan parámetros de cadenas de consulta y, por lo tanto, no devuelven distintas versiones de un objeto en función de los valores de los parámetros. Para estos orígenes, si configura CloudFront para reenviar los parámetros de cadenas de consulta al origen, CloudFront sigue almacenando en caché en función de los valores de los parámetros a pesar de que el origen devuelva versiones idénticas del objeto a CloudFront para cada valor del parámetro. Para que los parámetros de cadenas de consulta funcionen tal y como se describe en el ejemplo anterior con los idiomas, debe utilizar el carácter & como delimitador entre parámetros de cadenas de consulta. Si utiliza un delimitador diferente, es posible que obtenga resultados imprevistos, en función de los parámetros que especifique para que CloudFront utilice como base para el almacenamiento en caché y del orden en el que aparecen los parámetros en la cadena de consulta. Los siguientes ejemplos muestran lo que ocurre si utiliza un delimitador diferente y configura CloudFront para almacenar en caché solo en función del parámetro color : En la siguiente solicitud, CloudFront almacena en caché el contenido en función del valor del parámetro color , pero CloudFront interpreta el valor como red;size=large : https://d111111abcdef8.cloudfront.net/images/image.jpg? color=red;size=large En la siguiente solicitud, CloudFront almacena en caché el contenido pero no en función de los parámetros de cadenas de consulta. Esto se debe a que ha configurado CloudFront para almacenar en caché en función del parámetro color , pero CloudFront interpreta la siguiente cadena como que contiene solo un parámetro size con el valor large;color=red : https://d111111abcdef8.cloudfront.net/images/image.jpg? size=large;color=red Puede configurar CloudFront para que realice una de las siguientes acciones: No enviar cadenas de consultas al origen. Si no reenvía cadenas de consultas, CloudFront no almacena en caché en función de parámetros de cadenas de consulta. Reenviar cadenas de consulta al origen y almacenar en caché en función de todos los parámetros de la cadena de consulta. Reenviar cadenas de consulta al origen y almacenar en caché en función de parámetros especificados en la cadena de consulta. Para obtener más información, consulte Optimización del almacenamiento en caché . Temas Configuración de la consola y de la API para el reenvío de cadenas de consulta y almacenamiento en caché Optimización del almacenamiento en caché Parámetros de cadena de consulta y registros estándar de CloudFront (registros de acceso) Configuración de la consola y de la API para el reenvío de cadenas de consulta y almacenamiento en caché Al crear una distribución en la consola de CloudFront, CloudFront configura el reenvío y el almacenamiento en caché de cadenas de consulta en función del tipo de origen. Si lo desea, puede editar manualmente esta configuración. Para obtener más información, consulte la siguiente configuración en la Referencia de toda la configuración de distribución : Reenvío de cadenas de consulta y almacenamiento en caché Lista de permitidos de cadenas de consulta Para configurar el reenvío y el almacenamiento en caché de cadenas de consulta con la API de CloudFront, consulte CachePolicy y OriginRequestPolicy en la referencia de la API de Amazon CloudFront . Optimización del almacenamiento en caché Cuando se configura CloudFront para almacenar en caché en función de parámetros de cadenas de consulta, puede realizar los siguientes pasos para reducir el número de solicitudes que CloudFront reenvía al origen. Cuando las ubicaciones periférica de CloudFront sirven objetos, se reduce la carga en el servidor de origen y se reduce la latencia porque los objetos se sirven desde ubicaciones más cercanas a los usuarios. Almacene en caché solo en función de parámetros por los que su origen devuelve diferentes versiones de un objeto Por cada parámetro de cadena de consulta que la aplicación web reenvía a CloudFront, CloudFront reenvía solicitudes al origen por cada valor del parámetro y almacena en caché una versión independiente del objeto por cada valor del parámetro. Esto ocurre incluso si el origen siempre devuelve el mismo objeto independientemente del valor del parámetro. Para varios parámetros, el número de solicitudes y el número de objetos se multiplican. Le recomendamos configurar CloudFront para almacenar en caché solo los parámetros de cadenas de consulta para los que el origen devuelve distintas versiones y que piense detenidamente en las ventajas de almacenar en caché en función de cada parámetro. Supongamos que tiene un sitio web de venta al por menor. Dispone de imágenes de una chaqueta en seis colores diferentes y la chaqueta está disponible en diez tallas distintas. Sus imágenes de la chaqueta muestran los distintos colores, pero no las distintas tallas. Para optimizar el almacenamiento en caché, debe configurar CloudFront para almacenar en caché solo en función del parámetro de color, no el de tamaño. Esto aumenta la probabilidad de que CloudFront pueda atender una solicitud de la caché, lo que mejora el rendimiento y reduce la carga en el origen. Organice los parámetros siempre en el mismo orden El orden de los parámetros de cadenas de consulta es importante. En el siguiente ejemplo, las cadenas de consulta son idénticas, salvo que los parámetros están en órdenes diferentes. Esto hace que CloudFront reenvíe dos solicitudes de image.jpg independientes al origen y que almacene en caché dos versiones independientes del objeto: https://d111111abcdef8.cloudfront.net/images/image.jpg? color=red&size=large https://d111111abcdef8.cloudfront.net/images/image.jpg? size=large&color=red Le recomendamos enumerar los nombres de los parámetros siempre en el mismo orden, por ejemplo, por orden alfabético. Utilice siempre el mismo tipo de letra (mayúsculas o minúsculas) para los nombres y valores de parámetros CloudFront diferencia mayúsculas de minúsculas en los valores y nombres de los parámetros al almacenar en caché en función de los parámetros de cadenas de consulta. En el siguiente ejemplo, las cadenas de consulta son idénticas, salvo por las mayúsculas y minúsculas de los nombres y valores del parámetro. Esto hace que CloudFront reenvíe cuatro solicitudes de image.jpg independientes al origen y que almacene en caché cuatro versiones independientes del objeto: https://d111111abcdef8.cloudfront.net/images/image.jpg? color=red https://d111111abcdef8.cloudfront.net/images/image.jpg? color=Red https://d111111abcdef8.cloudfront.net/images/image.jpg? Color=red https://d111111abcdef8.cloudfront.net/images/image.jpg? Color=Red Recomendamos utilizar mayúsculas o minúsculas de forma consistente en los valores y nombres de parámetros, como todo en minúsculas. No utilice nombres de parámetros que entren en conflicto con URL firmadas Si utiliza URL firmadas para restringir el acceso al contenido (si ha agregado signatarios de confianza a la distribución), CloudFront elimina los siguientes parámetros de cadenas de consulta antes de reenviar el resto de la URL al origen: Expires Key-Pair-Id Policy Signature Si utiliza URL firmadas y desea configurar CloudFront para reenviar cadenas de consulta al origen, sus propios parámetros de cadenas de consulta no pueden denominarse Expires , Key-Pair-Id , Policy ni Signature . Parámetros de cadena de consulta y registros estándar de CloudFront (registros de acceso) Si habilita el registro, CloudFront registra la URL completa, incluidos los parámetros de cadenas de consulta. Esto ocurre independientemente de si ha configurado CloudFront para reenviar cadenas de consulta al origen. Para obtener más información acerca del registro de CloudFront, consulte Registros estándar (registros de acceso) . JavaScript está desactivado o no está disponible en su navegador. Para utilizar la documentación de AWS, debe estar habilitado JavaScript. Para obtener más información, consulte las páginas de ayuda de su navegador. Convenciones del documento Administración de vencimiento de caché Almacenamiento en caché de contenido en función de cookies ¿Le ha servido de ayuda esta página? - Sí Gracias por hacernos saber que estamos haciendo un buen trabajo. Si tiene un momento, díganos qué es lo que le ha gustado para que podamos seguir trabajando en esa línea. ¿Le ha servido de ayuda esta página? - No Gracias por informarnos de que debemos trabajar en esta página. Lamentamos haberle defraudado. Si tiene un momento, díganos cómo podemos mejorar la documentación. | 2026-01-13T09:30:34 |
https://www.iso.org/es/perspectivas | ISO - Todos los artículos 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 Perspectivas Destacado Las ventajas de implementar un sistema de gestión ambiental para su empresa La priorización de la sostenibilidad ambiental no solo es tendencia: es una estrategia vital para garantizar la salud y la prosperidad de las organizaciones a largo plazo. Equilibrar el crecimiento con la gestión ambiental es más importante que nunca ahora que los impactos del cambio climático aumentan … Últimos artículos 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 ¿Qué es la web oscura? Mitos, realidades y riesgos de ciberseguridad Gestión de la configuración: por qué es tan importante para la seguridad de TI Cómo los derechos de propiedad intelectual protegen la creatividad y la innovación Identificar peligros de SST y gestionar riesgos Equipo de protección personal: proteger a los trabajadores en un lugar de trabajo en constante evolución Seguridad en el trabajo: una guía para proteger la salud de las personas en el trabajo Seguridad de la información: pilar de resiliencia en la era digital Cargar más Actualidad Ver más 12 diciembre 2025 Diez premios Emmy y sumando: nueva distinción para el SC 29 por dar forma al futuro de las normas multimedia Opinion Colaboración por el clima: cómo los organismos normalizadores impulsan la gobernanza ambiental mundial 11 diciembre 2025 International Standards at the heart of development: ISO joins the World Bank in launching the World Development Report 2025 8 diciembre 2025 Good data, better decisions: ISO showcases new environmental standards dashboard at UNEA-7 2 diciembre 2025 International Organizations align at International AI Standards Summit 21 noviembre 2025 El Pabellón de la Normalización concluye la COP30 con un llamado a integrar las Normas Internacionales en cada etapa de la acción climática 20 noviembre 2025 Reforzar la acción climática: ISO celebra la iniciativa coordinada del sistema de la ONU para la implementación de las CDN Cargar más Perspectivas y actualidad Perspectivas Todos los artículos 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.iso.org/es/home/about-iso/events.html | ISO - Events and meetings 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 Sobre nosotros Events and meetings ISO runs a series of events to help you get the most from standards Bringing standards to life through shared experiences and case studies, as well as identifying future trends where standards have a role to play, contributes to the goal of seeing ISO standards used everywhere. You can see what's coming up next, as well as browse the archive of our most recent events to better see the wide range of topics covered and access resources. If you have a question about any of our events, past or future, get in touch with us , or connect with us on social media below. ISO en la COP30: Convocando alianzas, impulsando la acción climática 10-21 de noviembre de 2025 ISO Annual Meetings Kigali, Rwanda | 6-10 October 2025 ISO Annual Meeting 2025 The ISO Annual Meeting is the premier event for timely discussions on emerging trends and challenges in International Standards and their crucial role in advancing the global sustainable development agenda. Cartagena de Indias, Colombia | 9-13 September 2024 ISO Annual Meeting 2024 A week of insightful discussions on advancing standards to address the world's most pressing challenges. Brisbane, Australia | 18–22 September 2023 ISO Annual Meeting 2023 Meeting global needs together: in an era defined by rapid change, the ISO Annual Meeting 2023 was a unique opportunity for meaningful discussion and truly global collaboration. Abu Dhabi, UAE | 19 – 23 septiembre 2022 ISO Annual Meeting 2022 The ISO Annual Meeting is the keystone event in the ISO calendar featuring thematic sessions, networking opportunities, the ISO General Assembly and related … Online event | 20 – 24 septiembre 2021 ISO Week 2021 This year’s event will look a bit different, as we’re hosting it entirely online. We’ve developed a bespoke virtual platform where you can watch presentations, … Conferences and Workshops Seoul, Korea | 2-3 December 2025 International AI Standards Summit 2025 The International AI Standards Summit 2025 is an exclusive, high-level gathering designed to drive the global conversation on AI design, governance and International Standards. London, UK | 19 to 23 May 2025 46th COPOLCO plenary and workshops We are delighted to welcome you to the 46th COPOLCO Plenary and Workshops, hosted by the British Standards Institution (BSI) in London, United Kingdom, from 19-23 May 2025. Berlin, Germany | 8 to 11 April 2025 39th CASCO plenary and workshops We are delighted to welcome you to the 39th CASCO Plenary and workshop, hosted by the DIN Deutsches Institut für Normung, in Berlin, Germany, from 8 to 11 April 2025. Online | 11 diciembre 2024 Building trust in conformity assessment of sustainability matters – good practices and the path forward A CASCO webinar to explore conformity assessment applied to sustainability matters, highlighting best practices and the way forward. Online Event | 25 – 29 abril 2022 CASCO plenary and workshop 2022 The 36th CASCO plenary and workshop is taking place entirely online this year. Find out more about the week’s programme, learn about the different events … Virtual events Virtual event | 22 May 2024 Circular economy standards launch Webcast on 22 May with Circular Economy expert Catherine Chevauché answering your questions. Online | 11 diciembre 2024 Building trust in conformity assessment of sustainability matters – good practices and the path forward A CASCO webinar to explore conformity assessment applied to sustainability matters, highlighting best practices and the way forward. Online | 21 noviembre 2023 Conformity assessment building trust in a digital world A CASCO webinar about the assessment of increasingly complex and digitized products, processes, services, and systems. Geneva, Switzerland | 27 junio 2023 Webinar on Semantics and Semantic Interoperability – Electronic Business Memorandum of Understanding (eB-MoU) In today's data-driven world, organizations face the challenge of efficiently integrating and making sense of vast amounts of diverse data. Semantics and … Sobre nosotros Events 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/pricing/penneo-sign/ | Priser - Penneo Sign 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Å Penneo Sign Priser Denmark Denmark Sign Essential Fra 834 DKK pr. måned, faktureres årligt 500 underskrifter inkluderet Ekstra underskrifter: 14 DKK pr. underskrift, mængderabat gælder.Underskrifter er defineret som hver enkelt underskriftslinje i hvert dokument. Underskriftslinjer henviser til hver udpeget plads til underskrifter i dokumentet. Underskrift med nationale eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv, BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. SMS-verifikation SSO Dokumentarkiv BOOK ET MØDE Har du brug for hurtig hjælp? Vi ringer dig op inden for 20 minutter. Sign Plus Fra 1,250 DKK pr. måned, faktureres årligt 500 underskrifter inkluderet Ekstra underskrifter: 14 DKK pr. underskrift, mængderabat gælder.Underskrifter er defineret som hver enkelt underskriftslinje i hvert dokument. Underskriftslinjer henviser til hver udpeget plads til underskrifter i dokumentet. Underskrift med nationale eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv, BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. SMS-verifikation SSO Dokumentarkiv Branchespecifikke underskriftsflows Visse arbejdsopgaver (f.eks. årsrapporter) kræver underskrifter i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet af de rigtige personer i den rigtige rækkefølge. Penneo Sign indeholder et udvalg af typiske underskriftsflows. Integrationer (med undtagelse af Caseware, som kræver et særskilt gebyr) BOOK ET MØDE Har du brug for hurtig hjælp? Vi ringer dig op inden for 20 minutter. Sign Pro Fra 3,917 DKK pr. måned, faktureres årligt 500 underskrifter inkluderet Ekstra underskrifter: 14 DKK pr. underskrift, mængderabat gælder.Underskrifter er defineret som hver enkelt underskriftslinje i hvert dokument. Underskriftslinjer henviser til hver udpeget plads til underskrifter i dokumentet. Underskrift med nationale eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv, BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. SMS-verifikation SSO Dokumentarkiv Branchespecifikke underskriftsflows Visse arbejdsopgaver (f.eks. årsrapporter) kræver underskrifter i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet af de rigtige personer i den rigtige rækkefølge. Penneo Sign indeholder et udvalg af typiske underskriftsflows. Integrationer (med undtagelse af Caseware, som kræver et særskilt gebyr) Dedikeret supportline Står i med et akut problem? Kontakt vores supportlinje og tal direkte med en af vores produktspecialister. Personlig onboardingplan Vi skræddersyr jeres onboardingoplevelse, så den passer perfekt til jeres teams specifikke behov. Dedikeret sparringspartner Få en dedikeret partner, der er fokuseret på at hjælpe jer med at vokse. Med regelmæssige gennemgang af jeres konto vil vi identificere muligheder for forbedring og sikre, at jeres team udnytter Penneos fulde potentiale. Adgang til API Sandbox Giv jeres udviklere adgang til Penneos sandbox-miljø. Her kan I i trygge rammer simulere API-kald, teste forskellige scenarier og validere jeres kode. Det sikrer, at alt fungerer som forventet, inden I tager løsningen i brug. BOOK ET MØDE Har du brug for hurtig hjælp? Vi ringer dig op inden for 20 minutter. Populære funktioner Inkluderet Kundeservice 4,3 stjerner hos Trustpilot Inkluderet Automatic reminders to signers Inkluderet Dashboard overview Tilføjelse Internationale underskrifter med pas & itsme® Tilføjelse Formularer Tilføjelse Brugerdefineret underskriftsflow SE ALLE PENNEO FUNKTIONER Digital tillid mellem parterne Når forretningsinteraktioner bliver mere og mere digitale, er behovet for tillid større end nogensinde. Penneo sikrer tillid mellem virksomheder og deres klienter ved at tilbyde en platform, der møder de højeste sikkerhedsstandarder, og som er i overensstemmelse med EU og national lovgivning. Sammenlign planer Sign Essential Sign Plus Sign Pro Send flere dokumenter på én gang Tilføj flere filer i en forsendelse for at sende dem til underskrift på én gang. Underskriv flere dokumenter på én gang Underskriv alle dokumenter i forsendelsen på samme tid, og brug kun dit eID én gang. Underskrift med national eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv,BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. Mulighed for at tilføje flere underskrivere Nogle forsendelser kræver underskrifter fra mere end én person. I Penneo Sign kan du tilføje det nødvendige antal underskrivere til hver forsendelse. Mulighed for at tilføje modtagere Modtagere er personer, der skal modtage dokumenterne i din forsendelse, men som ikke behøver at underskrive. Automatiske påmindelser Penneo Sign sender automatiske påmindelsesmails til underskrivere for at minde dem om at underskrive de nødvendige dokumenter. Flere standardfunktioner Automatiske opdateringsmails Ejere af forsendelser modtager automatiske mails for at holde styr på opdateringerne i forsendelserne og underskrivernes handlinger. Anmodning om underskrift og bekræftelsesmail Underskriv ved at tegne en underskrift Underskriv ved at uploade et billede af din underskrift Visnings- og underskriftsbegrænsninger Beskyt dine dokumenter ved at kontrollere, hvem der har tilladelse til at se og underskrive dem. SMS verifikation En adgangsbegrænsningsmetode, der giver dig mulighed for at kontrollere, hvem der er autoriseret til at se og underskrive dokumenter. Hændelseslog Se alle afsluttede handlinger vedrørende forsendelsen i hændelsesloggen. Kontakter Dokumentarkiv Sikkert og organiseret arkiv af alle underskrevne dokumenter, som hjælper din virksomhed med at holde styr på forsendelser. Personligt arkiv Underskrivere kan vælge at have et personligt arkiv, som giver dem adgang til alle deres underskrevne dokumenter. E-mail-skabeloner og -signaturer Tilpas dine e-mails med anmodning om underskrift, herunder en brugerdefineret e-mailsignatur. Penneo Sign fås på 8 sprog Dansk, engelsk, tysk, svensk, norsk, finsk, hollandsk & fransk. Tilpassede funktioner Branchespecifikke underskriftsflows Visse arbejdsopgaver (f.eks. årsrapporter) kræver underskrifter i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet af de rigtige personer i den rigtige rækkefølge. Penneo Sign indeholder et udvalg af typiske underskriftsflows, der hjælper med at lette de manuelle processer, der er involveret i at indsamle underskrifter i den rigtige rækkefølge. Tilpas udseende Tilpas Penneo Sign interfacet, så det passer til din virksomheds brandidentitet. Analytics Penneo Sign Dashboard Penneo Sign-dashboardet indeholder et udvalg af standarddata og analyser, f.eks. antal forsendelser, aktuel status for forsendelser, nyligt afsluttede forsendelser og meget mere. Forbrugsoversigt Du får et klart overblik over, hvordan Penneo Sign bliver brugt i din organisation, herunder de vigtigste tal: Hvor mange dokumenter er blevet underskrevet? Hvor aktive er jeres brugere? Og hvordan ændrer jeres aktivitet sig fra måned til måned? Integrationer og API SSO Brugere kan oprette en bruger eller logge ind med deres virksomheds Google- og Microsoft-konti. Integrationer (med undtagelse af Caseware) Penneo Sign er integreret med: Silverfin, Adminpulse, Ratios, Instaclause, M-Files, Anlisa, Advisor, Unik Bolig, Unik Advosys, EG AdvoPro, EG Strato, EG Bolig, ByteLab, KTP, Legis 365, ELO, Documendo, 4human, Emply, Talentech, TimePlan. Caseware-integration Ifølge aftalen med Caseware Denmark skal Penneo pålægge et integrationsgebyr på minimum 10 kr. pr. CVR/årsrapport, som kunden har. Vores minimumsgebyr er 500 kr. om måneden (6.000 kr. årligt). DKK 10 pr. CVR/annual report 10 kr. pr. CVR/årsrapport 10 kr. pr. CVR/årsrapport API-adgang Sandbox-adgang Support og ydelser Kundeservice Kontakt kundesupport via vores sagsstyringssystem, og få adgang til en oversigt, så du kan holde styr på dine åbne og afsluttede sager. Hjælpecenter Onboarding Webinarer Dedikeret supportline Står i med et akut problem? Kontakt vores supportlinje og tal direkte med en af vores produktspecialister. Personlig onboardingplan Vi skræddersyr jeres onboardingoplevelse, så den passer perfekt til jeres teams specifikke behov. 10,000 DKK 10,000 DKK Dedikeret sparringspartner Få en dedikeret partner, der er fokuseret på at hjælpe jer med at vokse. Med regelmæssige gennemgang af jeres konto vil vi identificere muligheder for forbedring og sikre, at jeres team udnytter Penneos fulde potentiale. Adgang til API Sandbox Giv jeres udviklere adgang til Penneos sandbox-miljø. Her kan I i trygge rammer simulere API-kald, teste forskellige scenarier og validere jeres kode. Det sikrer, at alt fungerer som forventet, inden I tager løsningen i brug. Kontinuerlig onboarding (pris pr. time) Kontinuerlig mulighed for onboarding af nye kollegaer, eller ifm. introduktion af nye funktioner. 1,200 DKK 1,200 DKK 1,200 DKK Add-ons Underskrift med itsme® (pris pr. signatur) 12 DKK 12 DKK 12 DKK Underskrift med pas (pris pr. signatur) 12 DKK 12 DKK 12 DKK Tilpassede underskriftsflows (pris pr. tilpasset underskriftsflow) Visse arbejdsprocesser kræver, at underskrifter foretages i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet i den rigtige rækkefølge. Vi tilbyder også skræddersyede underskrifsflows til din virksomheds specifikke behov. 20,000 DKK 20,000 DKK 20,000 DKK Formularer (ubegrænset adgang og oprettelse af formularer) 4,000 DKK 4,000 DKK 4,000 DKK Registreret brev (pris pr. brev) 10 DKK 10 DKK 10 DKK Vores kunder fortæller… “Det sidste skridt i vores digitaliseringsproces var at kunne sige, at vi tilbyder en 100% digital løsning. Det er, hvad Penneo har gjort muligt. Jo lettere vi kan gøre det for vores kunder at modtage, underskrive og returnere dokumenter, jo mere gnidningsløst bliver vores daglige arbejde.” – Julie van der Mast, revisor og direktør hos Finezz Accountants Ofte stillede spørgsmål Tilbyder Penneo produkttræning, onboarding og supporttjenester, og koster det noget? Penneo tilbyder online træning, tutorials og online onboarding-sessioner til alle nye kunder. Derudover tilbyder vi et omfattende hjælpecenter og support til alle kunder. Som kunde har du mulighed for at købe dedikeret onboarding, løbende onboarding af nye medarbejdere og adgang til premium-support, herunder telefon- og prioritetsservice. Hvor sikre er mine data med Penneo, og koster det noget at få ekstra sikkerhedsfunktioner? Penneo sørger for, at alle kundedata er beskyttet i henhold til de højeste standarder for informationssikkerhed. Penneo er certificeret i henhold til ISO 27001 og 27701. Disse certificeringer er gældende for vores arbejde med alle kunder, uden ekstra omkostninger. Er der volumenbaserede rabatter til store virksomheder? Vores pris pr. kunde (KYC) eller pris pr. underskrift (SIGN) varierer afhængigt af den mængde, du forpligter dig til. Hvis du forpligter dig til en større mængde, får du en billigere enhedspris. Du får altid den bedste samlede pris, hvis du forpligter dig til den mængde, du tror, du vil bruge. Hvad sker der, hvis mit forbrug overstiger mit abonnement? Hvis du bruger mere end den tildelte mængde i din pakke, vil du blive opkrævet det tilsvarende beløb (baseret på den aftalte enhedspris) ved udgangen af din abonnementsperiode eller ved fornyelse. Kan jeg foretage ændringer i mit abonnement baseret på forbrug? Hvis du forventer et højere forbrug, end du har forpligtet dig til, kan du til enhver tid opgradere dit abonnement til flere underskrifter/klienter, hvilket sandsynligvis vil føre til en bedre enhedspris. Det er kun muligt at nedgradere dit abonnement i slutningen af din abonnementsperiode. Hvornår/hvordan kan jeg opsige mit abonnement? Du kan opsige dit abonnement med mindst 3 måneders varsel, før dit abonnement fornyes. Hvad er betalingsbetingelserne, og hvilke betalingsformer accepteres? Penneos standardbetalingsfrist er 14 dage. Vi accepterer betalinger via bankoverførsel (standard) og kortbetaling (til de mindste kunder). Er der nogen ekstra omkostninger eller skjulte gebyrer? Alle priser vises tydeligt på vores hjemmeside. Men hvis du vælger at tilføje eller bruge tjenester ud over den pakke, du har købt, kan der påløbe ekstra gebyrer. Se hvad du kan opnå med Penneo FÅ ET TILBUD 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://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT2yQOeKUfGgJN6T8rjtiZCJv7xLZ8EiW-xewf5vqqnRZuEnkBErNWqmwwRcmcdssLY5-rUZPjCqgFhV7fYKDH61L_kQaJq-kFkkjIsGJKdVF5iJrJqUf1DnVBVlQ0MjwV55qTsNJt0VNFfOHBODo9OQk8JK_g | 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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/pt_br/AmazonCloudFront/latest/DeveloperGuide/kvs-with-functions-kvp.html | Trabalhar com dados de chave-valor - Amazon CloudFront Trabalhar com dados de chave-valor - Amazon CloudFront Documentação Amazon CloudFront Guia do Desenvolvedor Trabalhar com pares de chave-valor (console) Sobre o KeyValueStore do CloudFront Trabalhar com pares de chave-valor (AWS CLI) Trabalhar com pares de chave-valor (API) Trabalhar com dados de chave-valor Este tópico descreve como adicionar pares de chave-valor a um armazenamento de chave-valor existente. Para incluir pares de chave-valor ao criar inicialmente armazenamentos de chave-valor, consulte Criar um armazenamento de chave-valor . Tópicos Trabalhar com pares de chave-valor (console) Sobre o KeyValueStore do CloudFront Trabalhar com pares de chave-valor (AWS CLI) Trabalhar com pares de chave-valor (API) Trabalhar com pares de chave-valor (console) É possível usar o console do CloudFront para trabalhar com os seus pares de chave-valor. Como trabalhar com pares de chave-valor Faça login no Console de gerenciamento da AWS e abra a página Functions (Funções) no console do CloudFront em https://console.aws.amazon.com/cloudfront/v4/home#/functions . Selecione a guia KeyValueStores . Selecione o armazenamento de chave-valor que deseja alterar. Na seção Pares de chave-valor , selecione Editar . É possível adicionar um par de chave-valor, excluir um par de chave-valor ou alterar o valor de um par existente. Ao concluir, escolha Salvar alterações . Sobre o KeyValueStore do CloudFront dica A API KeyValueStore do CloudFront é um serviço global que usa o Signature Version 4A (SigV4A) para autenticação. O uso de credenciais temporárias com o SigV4A requer tokens de sessão da versão 2. Para ter mais informações, consulte Usar credenciais temporárias com a API KeyValueStore do CloudFront . Se você estiver usando a AWS Command Line Interface (AWS CLI) ou seu próprio código para chamar a API KeyValueStore do CloudFront, consulte as seções a seguir. Quando você trabalha com um armazenamento de chave-valor e seus pares de chave-valor, o serviço que você chama depende do seu caso de uso: Para trabalhar com pares de chave-valor em um armazenamento de chave-valor existente , use o serviço KeyValueStore do CloudFront. Para incluir pares de chave-valor no armazenamento de chave-valor ao criá-lo inicialmente , use o serviço CloudFront. Tanto a API do CloudFront quanto a API KeyValueStore do CloudFront têm uma operação DescribeKeyValueStore . Você pode chamá-los por diferentes motivos. Para entender as diferenças, consulte a tabela a seguir. API DescribeKeyValueStore do CloudFront API KeyValueStore DescribeKeyValueStore do CloudFront Dados sobre o armazenamento de chave-valor Retorna dados, como o status e a data em que o próprio armazenamento de chave-valor foi modificado pela última vez. Retorna dados sobre o conteúdo do recurso de armazenamento: os pares de chave-valor no armazenamento e o tamanho do conteúdo. Dados que identificam o armazenamento de chave-valor Exibe uma ETag , o UUID e o ARN do armazenamento de chave-valor. Exibe uma ETag e o ARN do armazenamento de chave-valor. Observações Cada operação DescribeKeyValueStore exibe uma ETag diferente . As ETags não são intercambiáveis. Ao chamar uma operação de API para concluir uma ação, é necessário especificar a ETag da API apropriada. Por exemplo, na operação DeleteKey do KeyValueStore do CloudFront, é possível especificar a ETag exibida da operação DescribeKeyValueStore do KeyValueStore do CloudFront. Quando você invoca CloudFront Functions usando o KeyValueStore do CloudFront, os valores no armazenamento de chave-valor não são atualizados nem alterados durante a invocação da função. As atualizações são processadas entre as invocações de uma função. Trabalhar com pares de chave-valor (AWS CLI) É possível executar os comandos da AWS Command Line Interface a seguir no KeyValueStore do CloudFront. Sumário Listar pares de chave-valor Obter pares de chave-valor Descrever um armazenamento de chave-valor Criar um par de chave-valor Excluir um par de chave-valor Atualizar pares de chave-valor Listar pares de chave-valor Para listar pares de chave-valor no armazenamento de chave-valor, execute o comando a seguir. aws cloudfront-keyvaluestore list-keys \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Resposta { "Items": [ { "Key": "key1", "Value": "value1" } ] } Obter pares de chave-valor Para obter um par de chave-valor no armazenamento de chave-valor, execute o comando a seguir. aws cloudfront-keyvaluestore get-key \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Resposta { "Key": "key1", "Value": "value1", "ItemCount": 1, "TotalSizeInBytes": 11 } Descrever um armazenamento de chave-valor Para descrever um armazenamento de chave-valor, execute o comando a seguir. aws cloudfront-keyvaluestore describe-key-value-store \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Resposta { "ETag": "KV1F83G8C2ARO7P", "ItemCount": 1, "TotalSizeInBytes": 11, "KvsARN": "arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example", "Created": "2024-05-08T07:48:45.381000-07:00", "LastModified": "2024-08-05T13:50:58.843000-07:00", "Status": "READY" } Criar um par de chave-valor Para criar um par de chave-valor no armazenamento de chave-valor, execute o comando a seguir. aws cloudfront-keyvaluestore put-key \ --if-match=KV1PA6795UKMFR9 \ --key=key2 \ --value=value2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Resposta { "ETag": "KV13V1IB3VIYZZH", "ItemCount": 3, "TotalSizeInBytes": 31 } Excluir um par de chave-valor Para excluir um par de chave-valor, execute o comando a seguir. aws cloudfront-keyvaluestore delete-key \ --if-match=KV13V1IB3VIYZZH \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Saída { "ETag": "KV1VC38T7YXB528", "ItemCount": 2, "TotalSizeInBytes": 22 } Atualizar pares de chave-valor É possível usar o comando update-keys para atualizar mais de um par de chave-valor. Por exemplo, para excluir um par de chave-valor e criar outro, execute o comando a seguir. aws cloudfront-keyvaluestore update-keys \ --if-match=KV2EUQ1WTGCTBG2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example \ --deletes '[ { "Key":"key2"}]' \ --puts '[ { "Key":"key3","Value":"value3"}]' Resposta { "ETag": "KV3AEGXETSR30VB", "ItemCount": 3, "TotalSizeInBytes": 28 } Trabalhar com pares de chave-valor (API) Siga esta seção para trabalhar com os pares de chave-valor de forma programática. Sumário Obter uma referência a um armazenamento de chave-valor Alterar pares de chave-valor em um armazenamento de chave-valor Exemplo de código de KeyValueStore do CloudFront Obter uma referência a um armazenamento de chave-valor Ao usar a API KeyValueStore do CloudFront para chamar uma operação de gravação, é necessário especificar o ARN e a ETag do armazenamento de chave-valor. Para obter esses dados, faça o seguinte: Como obter uma referência a um armazenamento de chave-valor Use a operação de API CloudFront ListKeyValueStores para obter uma lista de armazenamentos de chave-valor. Encontre o armazenamento de chave-valor que deseja alterar. Use a operação de API CloudFrontKeyValueStore DescribeKeyValueStore e especifique o armazenamento de chave-valor da etapa anterior. A resposta inclui o ARN e a ETag do armazenamento de chave-valor. O ARN inclui o número da Conta da AWS, o key-value-store constante e o UUID, como o seguinte exemplo: arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 Uma ETag que se parece com o seguinte exemplo: ETVABCEXAMPLE2 Alterar pares de chave-valor em um armazenamento de chave-valor É possível especificar o armazenamento de chave-valor que contém o par de chave-valor que você deseja atualizar. Veja as seguintes operações da API KeyValueStore do CloudFront: CloudFrontKeyValueStore DeleteKey : exclui um par de chave-valor CloudFrontKeyValueStore GetKey : retorna um par de chave-valor CloudFrontKeyValueStore ListKeys : retorna uma lista de pares de chave-valor CloudFrontKeyValueStore PutKey : é possível realizar as seguintes tarefar: Criar um par de chave-valor em um armazenamento de chave-valor especificando um novo nome e valor da chave. Defina um valor diferente em um par de chave-valor especificando um nome de chave existente e um novo valor de chave. CloudFrontKeyValueStore UpdateKeys : é possível executar uma ou mais das seguintes ações em uma operação de tudo ou nada: Excluir um ou mais pares de chave-valor. Criar um ou mais pares de chave-valor. Definir um valor diferente em um ou mais pares de chave-valor existentes. Exemplo de código de KeyValueStore do CloudFront O código a seguir mostra como chamar a operação de API DescribeKeyValueStore para um armazenamento de chave-valor. const { CloudFrontKeyValueStoreClient, DescribeKeyValueStoreCommand, } = require("@aws-sdk/client-cloudfront-keyvaluestore"); require("@aws-sdk/signature-v4-crt"); (async () => { try { const client = new CloudFrontKeyValueStoreClient( { region: "us-east-1" }); const input = { KvsARN: "arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111", }; const command = new DescribeKeyValueStoreCommand(input); const response = await client.send(command); } catch (e) { console.log(e); } })(); O Javascript está desativado ou não está disponível no seu navegador. Para usar a documentação da AWS, o Javascript deve estar ativado. Consulte as páginas de Ajuda do navegador para obter instruções. Convenções do documento Formato de arquivo para pares de chave-valor Personalizar com o Lambda@Edge Essa página foi útil? - Sim Obrigado por nos informar que estamos fazendo um bom trabalho! Se tiver tempo, conte-nos sobre o que você gostou para que possamos melhorar ainda mais. Essa página foi útil? - Não Obrigado por nos informar que precisamos melhorar a página. Lamentamos ter decepcionado você. Se tiver tempo, conte-nos como podemos melhorar a documentação. | 2026-01-13T09:30:34 |
https://www.php.net/x-myracloud-5958a2bbbed300a9b9ac631223924e0b/1768296244.752 | 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 |
https://young-programmers.blogspot.com/2009/08/superhappydevhouse-34-interviews-part.html | Young Programmers Podcast: SuperHappyDevHouse 34 Interviews, Part One skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Sunday, August 23, 2009 SuperHappyDevHouse 34 Interviews, Part One Interviews with programmers and hardware hackers from SuperHappyDevHouse 34. Joel Franusic introduces SuperHappyDevHouse and talks about how he learned programming from his dad, an embedded systems engineer. Joshua Neal shows an LED connected to an Arduino board. Jens Andersson shows a program, Colors!, for drawing on the Nintendo DS. Otavio Good shows a polar bear drawing he made using that program. Steve Okay shows an Arduino-controlled robot he built, and describes being inspired by the movie Tron to stay up all night and make a light cycle game. Ben McGraw talks about programming role playing games. Caroline Ratajski talks about how she started at age 9 with a BASIC text game, then learned web development and networking, and continued with a formal computer science education leading to her current work in communications signals analysis. More interviews follow in part two. at 1:32 PM Labels: arduino , interview , shdh , shdh34 Newer Post Older Post Home About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ►  2015 (1) ►  February (1) ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ▼  2009 (37) ►  December (4) ►  November (1) ►  September (7) ▼  August (11) SuperHappyDevHouse 34 Interviews, Part Two SuperHappyDevHouse 34 Interviews, Part One Jumping Man in Pygame Interviews with Professional Programmers, Part One Functions in Python Dave Briccetti Introduces the Podcast Using a Python Dictionary to Give Custom Greetings Mr. T Guess The Food Walkthrough Platform Example, Very Simple Cat Saves the Villager Scratch Project Walkthrough Bob Lee Videoconference With Dave Briccetti’s Coll... ►  July (14)   | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html#limits-web-distributions | Kuota - Amazon CloudFront Kuota - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Kuota umum Kuota umum di distribusi Kuotas Umum tentang Kebijakan Kuota pada mTL dan toko kepercayaan Kuota pada Fungsi CloudFront Kuota pada Fungsi Koneksi Kuota pada toko nilai utama Kuotas di Lambda@Edge Kuota pada sertifikat SSL Kuotas pada invalidasi Kuotas pada kelompok utama Kuota pada koneksi WebSocket Kuotas pada enkripsi tingkat lapangan Kuota pada cookie (pengaturan cache warisan) Kuota pada string kueri (pengaturan cache warisan) Kuota pada header Kuota pada distribusi multi-penyewa Informasi Terkait Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Kuota Anda dapat meminta kenaikan CloudFront kuota dengan menggunakan opsi berikut: Anda dapat menggunakan konsol Service Quotas atau. AWS Command Line Interface Untuk informasi selengkapnya, lihat topik berikut: Meminta peningkatan kuota pada Panduan Pengguna Service Quotas request-service-quota-increase dalam Referensi AWS CLI Perintah Jika CloudFront kuota tidak tersedia di Service Quotas, gunakan untuk membuat AWS Support Center Console kasus peningkatan kuota layanan . CloudFront tunduk pada kuota berikut. Topik Kuota umum Kuota umum di distribusi Kuotas Umum tentang Kebijakan Kuota pada mTL dan toko kepercayaan Kuota pada Fungsi CloudFront Kuota pada Fungsi Koneksi Kuota pada toko nilai utama Kuotas di Lambda@Edge Kuota pada sertifikat SSL Kuotas pada invalidasi Kuotas pada kelompok utama Kuota pada koneksi WebSocket Kuotas pada enkripsi tingkat lapangan Kuota pada cookie (pengaturan cache warisan) Kuota pada string kueri (pengaturan cache warisan) Kuota pada header Kuota pada distribusi multi-penyewa Informasi Terkait Kuota umum Entitas Kuota standar Laju transfer data per distribusi (Kuota ini tidak berlaku untuk distribusi yang berlangganan paket harga CloudFront flat-rate. Untuk informasi lebih lanjut, lihat CloudFront paket harga flat-rate .) 150 Gbps Minta kuota yang lebih tinggi Permintaan per detik per distribusi (Kuota ini tidak berlaku untuk distribusi yang berlangganan paket harga CloudFront flat-rate. Untuk informasi lebih lanjut, lihat CloudFront paket harga flat-rate .) 250.000 Minta kuota yang lebih tinggi Tanda yang dapat ditambahkan ke distribusi 50 Minta kuota yang lebih tinggi File yang dapat Anda sajikan per distribusi Tidak ada kuota Panjang maksimum permintaan atau respons asal, termasuk header dan string kueri, tetapi tidak termasuk isi isi 20.480 byte Panjang maksimal URL 8.192 byte Jumlah maksimum konfigurasi pengiriman log akses real-time per Akun AWS 150 Kuota umum di distribusi Entitas Kuota default Nama domain alternatif (CNAMEs) per distribusi Untuk informasi selengkapnya, lihat Gunakan kustom URLs dengan menambahkan nama domain alternatif (CNAMEs) . 100 Minta kuota yang lebih tinggi Perilaku Cache per distribusi 75 Minta kuota yang lebih tinggi Upaya koneksi per asal Untuk informasi selengkapnya, lihat Upaya koneksi . 1-3 Waktu habis penerbangan lanjutan per asal Untuk informasi selengkapnya, lihat Batas waktu koneksi . 1-10 detik Batas waktu respons per asal Ini juga dikenal sebagai batas waktu baca asal atau batas waktu permintaan asal . Untuk informasi selengkapnya, lihat Batas waktu respons . 1-120 detik Minta kuota yang lebih tinggi Keep-alive timeout per asal Untuk informasi selengkapnya, lihat Keep-alive timeout (khusus dan hanya asal VPC) . 1-120 detik Minta kuota yang lebih tinggi Distribusi per Akun AWS Untuk informasi selengkapnya, lihat Buat distribusi . 500 Minta kuota yang lebih tinggi Distribusi per kontrol akses asal 100 Minta kuota yang lebih tinggi Distribusi dalam rantai permintaan ke titik akhir asal Kami tidak menyarankan menempatkan satu distribusi di depan yang lain. Melebihi kuota ini menghasilkan kesalahan 403. 2 Kompresi file: berbagai ukuran file yang CloudFront dikompres Untuk informasi selengkapnya, lihat Sajikan file terkompresi . 1.000 hingga 10.000.000 byte Ukuran file cache maksimum per respons HTTP GET. Hanya tanggapan untuk HTTP GET yang di-cache. Tanggapan untuk POST atau PUT tidak di-cache. 50 GB Kontrol akses asal per Akun AWS 100 Minta kuota yang lebih tinggi Identitas akses asal per Akun AWS 100 Minta kuota yang lebih tinggi Kota Asal per distribusi 100 Minta kuota yang lebih tinggi Grup asal per distribusi 10 Minta kuota yang lebih tinggi Distribusi pementasan per Akun AWS Untuk informasi selengkapnya, lihat Gunakan penerapan CloudFront berkelanjutan untuk menguji perubahan konfigurasi CDN dengan aman . 20 Minta kuota yang lebih tinggi Distribusi yang terkait dengan asal VPC yang sama 50 Asal VPC per Akun AWS 25 Minta kuota yang lebih tinggi Jumlah maksimum distribusi yang dapat dikaitkan dengan satu daftar IP statis Anycast. 100 Minta kuota yang lebih tinggi Kuotas Umum tentang Kebijakan Entitas Kuota default Kebijakan cache khusus per Akun AWS (Tidak berlaku untuk kebijakan cache CloudFront terkelola ) 20 Minta kuota yang lebih tinggi Distribusi yang terkait dengan kebijakan cache yang sama 100 Kueri string per kebijakan cache 10 Minta kuota yang lebih tinggi Header sesuai kebijakan cache 10 Minta kuota yang lebih tinggi Kebijakan cookie per cache 10 Minta kuota yang lebih tinggi Total panjang gabungan dari semua string kueri, header, dan nama cookie dalam kebijakan cache 1024 Kebijakan permintaan asal kustom per Akun AWS (Tidak berlaku untuk kebijakan permintaan asal CloudFront terkelola ) 20 Minta kuota yang lebih tinggi Distribusi yang terkait dengan kebijakan permintaan asal yang sama 100 Kueri string per kebijakan permintaan asal 10 Minta kuota yang lebih tinggi Kebijakan permintaan header per asal 10 Minta kuota yang lebih tinggi Kebijakan permintaan cookie per asal 10 Minta kuota yang lebih tinggi Total panjang gabungan dari semua string kueri, header, dan nama cookie dalam kebijakan permintaan asal 1024 Kebijakan header respons kustom per Akun AWS (Tidak berlaku untuk kebijakan header respons CloudFront terkelola ) 20 Minta kuota yang lebih tinggi Distribusi yang terkait dengan kebijakan header respons yang sama 100 Minta kuota yang lebih tinggi Header kustom per kebijakan header respon 10 Minta kuota yang lebih tinggi Kebijakan penerapan berkelanjutan per Akun AWS 20 Minta kuota yang lebih tinggi Kuota pada mTL dan toko kepercayaan Entitas Kuota default Toko kepercayaan per Akun AWS 20 Minta kuota yang lebih tinggi Distribusi per toko kepercayaan 25 Ukuran bundel CA 64 KB Minta kuota yang lebih tinggi Ukuran sertifikat dalam bundel CA 16384 Minta kuota yang lebih tinggi Jumlah sertifikat dalam bundel CA 25 Kedalaman rantai sertifikat 4 Kuota pada Fungsi CloudFront Entitas Kuota default Fungsi per Akun AWS 100 Ukuran fungsi maksimum Kuota ini tidak dapat disesuaikan. Untuk menyimpan data tambahan untuk CloudFront Fungsi Anda, buat penyimpanan nilai kunci dan tambahkan pasangan nilai kunci Anda. Untuk informasi selengkapnya, lihat Amazon CloudFront KeyValueStore . 10 KB Memori fungsi maksimum 2 MB Distribusi yang terkait dengan fungsi yang sama 100 Selain kuota ini, ada beberapa batasan lain saat menggunakan CloudFront Fungsi. Untuk informasi selengkapnya, lihat Pembatasan CloudFront Fungsi . Kuota pada Fungsi Koneksi Entitas Kuota default Fungsi Koneksi per Akun AWS Untuk informasi selengkapnya, lihat Meminta peningkatan kuota Fungsi Koneksi . 0 Ukuran Fungsi Koneksi Maksimum Kuota ini tidak dapat disesuaikan. Untuk menyimpan data tambahan untuk Fungsi Koneksi Anda, buat penyimpanan nilai kunci dan tambahkan pasangan nilai kunci Anda. Untuk informasi selengkapnya, lihat Amazon CloudFront KeyValueStore . 10 KB Memori Fungsi Koneksi Maksimum 2 MB Distribusi yang terkait dengan Fungsi Koneksi yang sama 100 Selain kuota ini, ada beberapa batasan lain saat menggunakan Fungsi Koneksi. Untuk informasi selengkapnya, lihat Kaitkan Fungsi CloudFront Koneksi . Kuota pada toko nilai utama Entitas Kuota default Ukuran maksimum kunci dalam pasangan kunci-nilai 512 Byte Ukuran maksimum nilai dalam pasangan kunci-nilai 1 KB Pasangan nilai kunci maksimum yang dapat Anda perbarui dalam satu permintaan API 50 kunci atau muatan 3 MB, mana yang tercapai terlebih dahulu Ukuran maksimum penyimpanan nilai kunci individu 5 MB Jumlah maksimum fungsi yang dapat dikaitkan dengan satu penyimpanan nilai kunci 10 Jumlah maksimum penyimpanan nilai kunci per fungsi 1 Jumlah maksimum penyimpanan nilai kunci per akun 50 Minta kuota yang lebih tinggi Kuotas di Lambda@Edge Kuota umum Entitas Kuota default Distribusi per Akun AWS yang dapat memiliki fungsi Lambda @Edge 500 Minta kuota yang lebih tinggi Fungsi Lambda@Edge per distribusi 100 Minta kuota yang lebih tinggi Eksekusi yang bersamaan Catatan AWS Lambda mengelola kuota konkurensi untuk Lambda @Edge. Semua fungsi Lambda dalam Wilayah AWS berbagi kuota ini. Kami menyarankan Anda meninjau kuota eksekusi bersamaan di semua Wilayah AWS tempat yang Anda harapkan berasal dari permintaan pemirsa. Selain itu, setiap instance fungsi Lambda @Edge Anda dapat melayani hingga 10 permintaan per detik. Batas pemanggilan total adalah 10 kali batas konkurensi Anda. Untuk informasi selengkapnya, lihat topik berikut di Panduan AWS Lambda Pengembang : Memahami penskalaan fungsi Lambda Permintaan API Lambda 1.000 (masing-masing Wilayah AWS) Minta kuota yang lebih tinggi Distribusi yang terkait dengan fungsi yang sama 500 Ukuran maksimal terkompresi fungsi Lambda dan pustaka yang disertakan 50 MB Permintaan Lambda @Edge per detik (masing-masing didukung Wilayah AWS). Untuk informasi selengkapnya, lihat Kuota konkurensi di Panduan AWS Lambda Pengembang . 10.000 Kuota yang berbeda berdasarkan jenis peristiwa Entitas Peristiwa permintaan penampil dan respons penampil Peristiwa permintaan asal dan respons asal Ukuran memori fungsi 128 MB Sama seperti Kuota Lambda Waktu fungsi habis. Fungsi ini dapat melakukan panggilan jaringan ke sumber daya seperti bucket Amazon S3, tabel DynamoDB, atau instans Amazon di. EC2 Wilayah AWS 30 detik 30 detik Ukuran respons yang dihasilkan oleh fungsi Lambda, termasuk header dan tubuh 40 KB 1 MB Catatan Untuk daftar kuota Lambda @Edge tambahan yang dapat ditingkatkan dari Service Quotas, lihat titik akhir CloudFront Amazon dan kuota di. Referensi Umum AWS Selain kuota ini, ada beberapa pembatasan lain saat menggunakan fungsi Lambda@Edge. Untuk informasi selengkapnya, lihat Pembatasan Lambda@Edge . Kuota pada sertifikat SSL Entitas Kuota default Sertifikat SSL per Akun AWS saat melayani permintaan HTTPS menggunakan alamat IP khusus (tidak ada kuota saat melayani permintaan HTTPS menggunakan SNI) Untuk informasi selengkapnya, lihat Gunakan HTTPS dengan CloudFront . 2 Minta kuota yang lebih tinggi Sertifikat SSL yang dapat dikaitkan dengan distribusi CloudFront 1 Jika sertifikat SSL Anda khusus untuk komunikasi HTTPS antara pemirsa danCloudFront, dan jika Anda menggunakan AWS Certificate Manager (ACM) atau penyimpanan sertifikat IAM untuk menyediakan atau mengimpor sertifikat Anda, kuota tambahan berlaku. Untuk informasi selengkapnya, lihat Kuota tentang penggunaan SSL/TLS sertifikat dengan CloudFront (HTTPS antara pemirsa dan CloudFront hanya) . Ada juga kuota pada jumlah sertifikat SSL yang dapat Anda impor ke AWS Certificate Manager (ACM) atau upload ke AWS Identity and Access Management (IAM). Untuk informasi selengkapnya, lihat Meningkatkan kuota untuk sertifikat SSL/TLS . Kuotas pada invalidasi Entitas Kuota standar Ketidakabsahan file: jumlah maksimum file yang diperbolehkan dalam permintaan invalidasi aktif, tidak termasuk ketidakabsahan wildcard Untuk informasi selengkapnya, lihat Membatalkan file untuk menghapus konten . 3.000 Ketidakvalidan file: jumlah maksimum invalidasi wildcard aktif diperbolehkan 15 Tidak valid file: jumlah maksimum file yang dapat diproses oleh satu wildcard invalidation Tidak ada kuota Kuotas pada kelompok utama Entitas Kuota standar Kunci publik dalam satu kelompok kunci 5 Minta kuota yang lebih tinggi Grup kunci yang terkait dengan perilaku cache tunggal 4 Minta kuota yang lebih tinggi Grup kunci per Akun AWS 10 Minta kuota yang lebih tinggi Distribusi yang terkait dengan satu grup kunci 100 Minta kuota yang lebih tinggi Kuota pada koneksi WebSocket Entitas Kuota standar Waktu habis respons asal (waktu habis tunggal) 10 menit Jika CloudFront belum mendeteksi byte yang dikirim dari asal ke klien dalam 10 menit terakhir, koneksi dianggap idle dan ditutup. Kuotas pada enkripsi tingkat lapangan Entitas Kuota standar Panjang maksimum kolom untuk mengenkripsi Untuk informasi selengkapnya, lihat Gunakan enkripsi tingkat lapangan untuk membantu melindungi data sensitif . 16 KB Jumlah maksimum bidang dalam badan permintaan saat enkripsi tingkat bidang dikonfigurasi 10 Panjang maksimum badan permintaan saat enkripsi tingkat lapangan dikonfigurasi 1 MB Jumlah maksimum konfigurasi enkripsi tingkat lapangan yang dapat dikaitkan dengan satu Akun AWS 10 Jumlah maksimum profil enkripsi tingkat lapangan yang dapat dikaitkan dengan satu Akun AWS 10 Jumlah maksimum kunci publik yang dapat ditambahkan ke satu Akun AWS 10 Jumlah maksimum kolom untuk mengenkripsi yang dapat ditentukan dalam satu profil 10 Jumlah maksimum CloudFront distribusi yang dapat dikaitkan dengan konfigurasi enkripsi tingkat lapangan 20 Jumlah maksimum pemetaan profil argumen kueri yang dapat dimasukkan dalam konfigurasi enkripsi tingkat lapangan 5 Kuota pada cookie (pengaturan cache warisan) Kuota ini berlaku untuk CloudFront pengaturan cache lama. Sebaiknya gunakan kebijakan cache atau kebijakan permintaan asal alih-alih pengaturan lama. Entitas Kuota standar Cookie per perilaku cache Untuk informasi selengkapnya, lihat Konten cache berdasarkan cookie . 10 Minta kuota yang lebih tinggi Jumlah total byte dalam nama cookie (tidak berlaku jika Anda mengonfigurasi CloudFront untuk meneruskan semua cookie ke asal) 512 dikurangi jumlah cookie Kuota pada string kueri (pengaturan cache warisan) Kuota ini berlaku untuk CloudFront pengaturan cache lama. Sebaiknya gunakan kebijakan cache atau kebijakan permintaan asal alih-alih pengaturan lama. Entitas Kuota standar Jumlah karakter maksimum dalam string kueri 128 karakter Total jumlah maksimal karakter untuk semua string kueri dalam parameter yang sama 512 karakter String kueri per perilaku cache Untuk informasi selengkapnya, lihat Konten cache berdasarkan parameter string kueri . 10 Minta kuota yang lebih tinggi Kuota pada header Entitas Kuota standar Header per perilaku cache (pengaturan cache warisan) Untuk informasi selengkapnya, lihat Konten cache berdasarkan header permintaan . 10 Minta kuota yang lebih tinggi Teruskan header per perilaku cache 25 Minta kuota yang lebih tinggi Header khusus: jumlah maksimum header khusus yang dapat Anda konfigurasikan CloudFront untuk ditambahkan ke permintaan asal Untuk informasi selengkapnya, lihat Tambahkan header khusus ke permintaan asal . 30 Minta kuota yang lebih tinggi Header khusus: jumlah maksimum header kustom yang dapat Anda tambahkan ke kebijakan header respons 10 Minta kuota yang lebih tinggi Header kustom: panjang maksimum nama header 256 karakter Header kustom: panjang maksimum nilai header 1.783 karakter Header kustom: panjang maksimum untuk semua nilai header dan nama digabungkan 10.240 karakter Panjang maksimum nilai Content-Security-Policy header 1.783 karakter Minta kuota yang lebih tinggi Panjang maksimum nilai CORS (Access-Control-Allow-Origin) header 1.783 karakter Kuota pada distribusi multi-penyewa Entitas Kuota default Jumlah maksimum penyewa distribusi per Akun AWS 10.000 Minta kuota yang lebih tinggi Jumlah maksimum distribusi multi-tenant per Akun AWS 20 Minta kuota yang lebih tinggi Jumlah maksimum grup koneksi per Akun AWS 100 Minta kuota yang lebih tinggi Jumlah maksimum alias per penyewa distribusi 100 Minta kuota yang lebih tinggi Jumlah maksimum parameter per penyewa distribusi 5 Minta kuota yang lebih tinggi Jumlah maksimum parameter per distribusi multi-tenant 5 Minta kuota yang lebih tinggi Jumlah maksimum parameter dalam suatu bidang dalam distribusi multi-tenant 2 Minta kuota yang lebih tinggi Jumlah maksimum grup koneksi per daftar IP statis Anycast 5 Minta kuota yang lebih tinggi Untuk informasi selengkapnya tentang distribusi multi-penyewa, lihat. Memahami cara kerja distribusi multi-tenant Informasi Terkait Untuk informasi selengkapnya, lihat CloudFront titik akhir dan kuota Amazon di. Referensi Umum AWS Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Pengujian beban CloudFront Contoh kode 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://penneo.com/nl/ | Penneo: Veilige digitale ondertekening met itsme® en .beID Producten Penneo Sign Validator Waarom Penneo Integraties Oplossingen Toepassingen Digitaal ondertekenen Documentbeheer Vul en onderteken PDF-formulieren Automatisering van ondertekeningsprocessen eIDAS-conformiteit Branchen Audit en boekhouding Financiële sector Juridische sector Vastgoedsector Administratie en HR Prijzen Bronnen Knowledge hub Trust Center Productupdates SIGN Helpcentrum KYC Helpcentrum Systeem status LOG IN Bekijk hoe het werkt BOEK EEN AFSPRAAK NL DA EN NO FR Producten Penneo Sign Validator Waarom Penneo Integraties Oplossingen Audit en boekhouding Financiële sector Juridische sector Vastgoedsector Administratie en HR Toepassingen Digitaal ondertekenen Documentbeheer Vul en onderteken PDF-formulieren Automatisering van ondertekeningsprocessen eIDAS-conformiteit Prijzen Bronnen Knowledge hub Trust Center Productupdates SIGN Helpcentrum KYC Helpcentrum Systeem status BOEK EEN AFSPRAAK GRATIS UITPROBEREN LOG IN DA EN NO FR NL Penneo Sign Meld u aan bij Penneo Sign. LOG IN Penneo KYC Meld u aan bij Penneo KYC. LOG IN Versimpel je documentstromen met een veilige digitale ondertekening Met Penneo onderteken je documenten veilig, efficiënt en volledig conform eIDAS. Onze oplossing helpt organisaties om complexe processen te stroomlijnen en foutgevoelige handmatige stappen te elimineren. BOEK EEN AFSPRAAK Ontdek hoe het werkt Wij hebben het vertrouwen van meer dan 3.000 organisaties gewonnen Penneo Sign Een oplossing die elektronische handtekeningen gemakkelijk, handig en veilig maakt. Onderteken documenten met gekwalificeerde itsme®-handtekeningen of geavanceerde .beID-handtekeningen, automatiseer het ondertekeningsproces en valideer op een efficiënte en conforme manier de identiteit van de ondertekenaars. Meer informatie over Penneo Sign Integraties en open API Penneo integreert met de meest gebruikte digitale tools om ervoor te zorgen dat alle workflows met elkaar verbonden zijn in een technisch ecosysteem. Penneo biedt verschillende ingebouwde integraties met uiteenlopende softwaretoepassingen, zoals CRM- en ERP-systemen, .beID en itsme®. Meer informatie over onze integraties Met een CSAT van +88% delen onze klanten graag hun verhalen “We willen echt niet alleen een relatie tussen leverancier en klant, we voelen ons echt partners van Penneo. Want samenwerken levert voor ons beiden meerwaarde op en leidt tot een langdurige relatie.” – Charlotte Pille, Partner bij VGD MEER VERHALEN VAN KLANTEN BEKIJKEN Digitaal vertrouwen tussen partners Naarmate organisaties meer en meer digitaal met elkaar omgaan, is de behoefte aan vertrouwen groter dan ooit. Penneo zorgt voor vertrouwen tussen bedrijven en hun klanten door een platform te bieden dat voldoet aan de hoogste beveiligingsnormen, alsook aan de Europese en nationale wetgeving. BEZOEK ONS TRUST CENTER Bespaar tijd en middelen 81% van alle jaarverslagen in Denemarken worden ondertekend met Penneo. 7 miljoen documenten werden in 2024 ondertekend met Penneo. 60% van de documenten die met Penneo worden verzonden, worden binnen 24 uur ondertekend. Onze middelen verkennen Wat is een digitale handtekening? LEES MEER 9 essentiële kenmerken voor een digitaal ondertekenprogramma LEES MEER Bouw je digitaal ecosysteem: Penneo & Partners LEES MEER Kijk wat u kunt bereiken met Penneo BOEK EEN AFSPRAAK GRATIS UITPROBEREN Producten Penneo Sign Prijzen Integraties Open API Validator Waarom Penneo Oplossingen Audit en boekhouding Financiële sector Juridische sector Vastgoedsector Administratie en HR Toepassingen Digitaal ondertekenen Documentbeheer Vul en onderteken PDF-formulieren Automatisering van ondertekeningsprocessen eIDAS-conformiteit Bronnen Knowledge hub Trust Center Productupdates SUPPORT SIGN Helpcentrum KYC Helpcentrum Systeem status Bedrijf Over ons Vacatures Privacybeleid Voorwaarden Cookies Accessibility Statement Whistleblower Policy Neem contact op PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/es_es/AmazonCloudFront/latest/DeveloperGuide/lambda-generating-http-responses.html#lambda-updating-http-responses | Trabajo con solicitudes y respuestas - Amazon CloudFront Trabajo con solicitudes y respuestas - Amazon CloudFront Documentación Amazon CloudFront Guía para desarrolladores Uso de funciones con conmutación por error de origen Generación de respuestas HTTP en los desencadenadores de solicitud Actualización de respuestas HTTP en desencadenadores de respuesta de origen Acceso al cuerpo de la solicitud con la opción Incluir cuerpo Trabajo con solicitudes y respuestas Para utilizar las solicitudes y respuestas de Lambda@Edge, consulte los temas siguientes: Temas Uso de funciones de Lambda@Edge con conmutación por error de origen Generación de respuestas HTTP en los desencadenadores de solicitud Actualización de respuestas HTTP en desencadenadores de respuesta de origen Acceso al cuerpo de la solicitud con la opción Incluir cuerpo Uso de funciones de Lambda@Edge con conmutación por error de origen Puede utilizar las funciones de Lambda@Edge con distribuciones de CloudFront que ha configurado con grupos de origen, por ejemplo, para conmutación por error de origen que configure para ayudar a garantizar una alta disponibilidad. Para utilizar una función de Lambda con un grupo de origen, especifique la función en una solicitud de origen o un desencadenador de respuesta de origen para un grupo de origen al crear el comportamiento de la caché. Para obtener más información, consulte los siguientes temas: Creación de grupos de origen: Creación de un grupo de origen Cómo utilizar la conmutación por error de origen con Lambda@Edge: Utilizar la conmutación por error de origen con funciones de Lambda@Edge Generación de respuestas HTTP en los desencadenadores de solicitud Cuando CloudFront recibe una solicitud, es posible utilizar una función de Lambda para generar una respuesta HTTP que CloudFront devuelve directamente al lector sin enviarla al origen. La generación de respuestas HTTP reduce la carga en el origen, y normalmente también reduce la latencia para el espectador. Entre las situaciones más comunes para generar respuestas HTTP se incluyen las siguientes: Devolver una pequeña página web al lector Devolver un código de estado HTTP 301 o 302 para redirigir al usuario a otra página web Devolución de un código de estado HTTP 401 al espectador si el usuario no se ha autenticado Una función de Lambda@Edge puede generar una respuesta HTTP cuando ocurren los siguientes eventos de CloudFront: Eventos de solicitud del espectador Cuando un evento de solicitud del lector activa una función, CloudFront devuelve la respuesta al lector y no la almacena en caché. Eventos de solicitud al origen Cuando un evento de solicitud al origen activa una función, CloudFront busca en la caché de borde una respuesta generada previamente por la función. Si la respuesta está en la caché, la función no se ejecuta y CloudFront devuelve al lector la respuesta almacenada en la caché. Si la respuesta no está en la caché, la función se ejecuta, CloudFront devuelve la respuesta al lector y también la almacena en la caché. Para ver algunos ejemplos de código para generar respuestas HTTP, consulte Funciones de ejemplo de Lambda@Edge . También puede sustituir las respuestas HTTP en disparadores de respuesta. Para obtener más información, consulte Actualización de respuestas HTTP en desencadenadores de respuesta de origen . Modelo de programación En esta sección se describe el modelo de programación a seguir para usar Lambda@Edge con el fin de generar respuestas HTTP. Temas Objeto de respuesta Errores Campos obligatorios Objeto de respuesta La respuesta que devuelva como parámetro result del método callback debe tener la siguiente estructura (tenga en cuenta que solo es obligatorio el campo status ). 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' }; El objeto de respuesta puede incluir los siguientes valores: body El cuerpo, si lo hay, que desea que CloudFront devuelva en la respuesta generada. bodyEncoding La codificación del valor especificado en body . Las únicas codificaciones válidas son text y base64 . Si incluye body en el objeto response pero omite bodyEncoding , CloudFront trata el cuerpo como texto. Si especifica bodyEncoding como base64 pero el cuerpo no tiene una codificación base64 válida, CloudFront devuelve un error. headers Los encabezados que desea que devuelva CloudFront en la respuesta generada. Tenga en cuenta lo siguiente: Las claves del objeto headers son nombres de encabezado HTTP estándar en minúsculas. El uso de claves en minúsculas le proporciona acceso a los valores del encabezado sin diferenciar mayúsculas de minúsculas. Cada encabezado (por ejemplo, headers["accept"] or headers["host"] ) es una matriz de pares clave-valor. Para un encabezado determinado, la matriz contiene un par de clave-valor para cada valor de la respuesta generada. key (opcional) es el nombre del encabezado que diferencia mayúsculas de minúsculas tal como aparece en una solicitud HTTP; por ejemplo, accept u host . Especifique value como un valor de encabezado. Si no incluye la parte de clave de encabezado del par de clave-valor, Lambda@Edge insertará automáticamente una clave de encabezado utilizando el nombre de encabezado que proporcione. Independientemente de cómo haya formateado el nombre del encabezado, la clave de encabezado que se inserta automáticamente se formatea con mayúscula inicial para cada parte, separada por guiones (-). Por ejemplo, puede añadir un encabezado como el siguiente, sin una clave de encabezado: 'content-type': [ { value: 'text/html;charset=UTF-8' }] En este ejemplo, Lambda@Edge crea la siguiente clave de encabezado: Content-Type . Para obtener más información acerca de restricciones de uso de encabezados, consulte Restricciones en funciones de borde . status El código de estado HTTP. Proporcione el código de estado como una cadena. CloudFront utiliza el código de estado proporcionado para lo siguiente: Devolverlo en la respuesta Almacenarlo en la caché de borde de CloudFront cuando la respuesta la generó una función activada por un evento de solicitud al origen Inicie sesión en CloudFront Registros estándar (registros de acceso) Si el valor status no está comprendido entre 200 y 599, CloudFront devuelve un error al lector. statusDescription La descripción que desea que CloudFront devuelva en la respuesta, y que acompañará al código de estado HTTP. No es obligatorio utilizar descripciones estándar, como OK en un código de estado HTTP 200. Errores Los siguientes son posibles errores de respuestas HTTP generadas. La respuesta contiene un cuerpo y especifica un código de estado 204 (Sin contenido Cuando una solicitud del lector activa una función, CloudFront devuelve un código de estado HTTP 502 (Gateway incorrecta) al lector cuando se cumplen las dos condiciones siguientes: El valor de status es 204 (Sin contenido) La respuesta incluye un valor para body Esto se debe a que Lambda@Edge impone la restricción opcional de RFC 2616 que establece que una respuesta HTTP 204 no necesita contener cuerpo de mensaje. Restricciones en el tamaño de la respuesta generada El tamaño máximo de una respuesta generada por una función de Lambda depende del evento que desencadenó la función: Eventos de solicitud del lector : 40 KB Eventos de solicitud al origen : 1 MB Si la respuesta supera el tamaño permitido, CloudFront devuelve un código de estado HTTP 502 (Gateway incorrecta) al lector. Campos obligatorios El campo status es obligatorio. Todos los demás campos son opcionales. Actualización de respuestas HTTP en desencadenadores de respuesta de origen Cuando CloudFront recibe una respuesta HTTP desde el servidor de origen, si existe un desencadenador de respuesta del origen asociado al comportamiento de la caché, es posible modificar la respuesta HTTP para anular lo que ha devuelto el origen. Entre las situaciones más comunes para actualizar respuestas HTTP se incluyen las siguientes: Cambiar el estado para establecer un código de estado HTTP 200 y crear un cuerpo con contenido estático para devolverlo al espectador cuando un origen devuelva un código de estado de error (4xx o 5xx). Para ver código de muestra, consulte Ejemplo: Uso de un desencadenador de respuesta de origen para actualizar el código de estado de error a 200 . Cambiar el estado para establecer un código de estado HTTP 301 o 302, con objeto de redirigir al usuario a otro sitio web cuando un origen devuelve un código de estado de error (4xx o 5xx). Para ver código de muestra, consulte Ejemplo: Uso de un desencadenador de respuesta de origen para actualizar el código de estado de error a 302 . nota La función debe devolver un valor de estado entre 200 y 599 (incluidos); de lo contrario, CloudFront devuelve un error al espectador. También puede sustituir las respuestas HTTP en eventos de solicitud al origen y del espectador. Para obtener más información, consulte Generación de respuestas HTTP en los desencadenadores de solicitud . Cuando trabaja con la respuesta HTTP, Lambda@Edge no expone el cuerpo que devuelve el servidor de origen al desencadenador de respuesta del origen. Puede generar un cuerpo con contenido estático estableciéndolo en el valor deseado, o eliminar el cuerpo dentro de la función estableciendo un valor vacío. Si no actualiza el campo de cuerpo de la función, se devolverá al espectador el cuerpo original devuelto por el servidor de origen. Acceso al cuerpo de la solicitud con la opción Incluir cuerpo A partir de ahora, puede hacer que Lambda@Edge exponga el cuerpo de una solicitud en los métodos HTTP que permiten la escritura (POST, PUT, DELETE, etc.) para que puede tener acceso a él en la función de Lambda. Puede elegir acceso de solo lectura o puede especificar que sustituirá el cuerpo. Para habilitar esta opción, elija Incluir cuerpo al crear un desencadenador de CloudFront para la función que corresponde a un evento de solicitud al origen o del lector. Para obtener más información, consulte Adición de desencadenadores para una función de Lambda@Edge ; para obtener información acerca de cómo utilizar Incluir cuerpo con su función, consulte Estructura de eventos de Lambda@Edge . Entre los escenarios en los que es conveniente utilizar esta característica se incluyen los siguientes: Procesamiento de formularios web, como formularios de tipo "póngase en contacto con nosotros", sin devolver los datos de entrada de los clientes a los servidores de origen. Recopilación de datos de balizas web enviados por los navegadores de los espectadores y que se procesan en el borde. Para ver código de muestra, consulte Funciones de ejemplo de Lambda@Edge . nota Si el cuerpo de la solicitud es grande, Lambda@Edge lo trunca. Para obtener información detallada sobre el tamaño máximo y el truncamiento, consulte Restricciones para el cuerpo de la solicitud con la opción Incluir cuerpo . JavaScript está desactivado o no está disponible en su navegador. Para utilizar la documentación de AWS, debe estar habilitado JavaScript. Para obtener más información, consulte las páginas de ayuda de su navegador. Convenciones del documento Estructura de evento Funciones de ejemplo ¿Le ha servido de ayuda esta página? - Sí Gracias por hacernos saber que estamos haciendo un buen trabajo. Si tiene un momento, díganos qué es lo que le ha gustado para que podamos seguir trabajando en esa línea. ¿Le ha servido de ayuda esta página? - No Gracias por informarnos de que debemos trabajar en esta página. Lamentamos haberle defraudado. Si tiene un momento, díganos cómo podemos mejorar la documentación. | 2026-01-13T09:30:35 |
https://young-programmers.blogspot.com/search/label/shdh#sidebar | Young Programmers Podcast: shdh skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Showing posts with label shdh . Show all posts Showing posts with label shdh . Show all posts Sunday, August 23, 2009 SuperHappyDevHouse 34 Interviews, Part Two Interviews with programmers and hardware hackers from SuperHappyDevHouse 34, part 2 of 2. Kevin Gadd talks about his dad bringing home computers for him to play with, and learning to program them, and his career making videogames. Drew Perttula ’s dad brought home computers but no games, so Drew had to write his own. He got interested in visual effects and computer graphics. He works at DreamWorks Animation. Mike Lundy works for Nasa in Mountain View. He started programming around age 10 on a PCjr running BASIC. He works in the Intelligent Robotics Group at NASA. He hopes the software he works on will eventually run on the Moon or Mars. at 3:14 PM Labels: hacker , interview , programmer , shdh , shdh34 SuperHappyDevHouse 34 Interviews, Part One Interviews with programmers and hardware hackers from SuperHappyDevHouse 34. Joel Franusic introduces SuperHappyDevHouse and talks about how he learned programming from his dad, an embedded systems engineer. Joshua Neal shows an LED connected to an Arduino board. Jens Andersson shows a program, Colors!, for drawing on the Nintendo DS. Otavio Good shows a polar bear drawing he made using that program. Steve Okay shows an Arduino-controlled robot he built, and describes being inspired by the movie Tron to stay up all night and make a light cycle game. Ben McGraw talks about programming role playing games. Caroline Ratajski talks about how she started at age 9 with a BASIC text game, then learned web development and networking, and continued with a formal computer science education leading to her current work in communications signals analysis. More interviews follow in part two. at 1:32 PM Labels: arduino , interview , shdh , shdh34 Older Posts Home Subscribe to: Comments (Atom) About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ▼  2015 (1) ▼  February (1) This Podcast Moves to YouTube ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ►  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:35 |
https://vml.visma.ai/blog | Welcome to our Blog | Visma Machine Learning About us Who are we? Learn more about Visma Machine Learning What we do Learn more about the products we offer What our customers say Read our customers' testimonials Products Autosuggest Automate your workflow Smartscan Extract data from your documents Resources Blog Product news and showcases Showcase of prototypes Prototypes, ideas and experiments Support Get started Find out more about onboarding to Visma Machine Learning FAQ We have answers to your frequently asked questions. Privacy policy Learn how we handle your data and protect your privacy Cookie policy Learn about how we use cookies to enhance your experience API Documentation Contact Us About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Showcase of prototypes Support Get started FAQ Privacy policy Cookie policy API Documentation Loading... Gærtorvet 1-5 1799 Copenhagen Denmark E-mail: worksmarter@visma.com About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Prototypes Documentation Support Get started FAQ Privacy policy Cookie policy Security Information Operating Status © 2026 Visma Group. All rights reserved Loading... | 2026-01-13T09:30:35 |
https://www.iso.org/es/sectores/seguridad-proteccion-riesgo | ISO - Seguridad, protección y gestión de riesgos 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 Seguridad, protección y gestión de riesgos Gestión de riesgos Seguridad en el trabajo Seguridad de la información Protección contra el crimen Sistemas de alarma y advertencia Seguridad doméstica Control de accidentes y catástrofes Otros Las normas ISO sobre seguridad, protección y gestión de riesgos ayudan a las organizaciones a proteger a las personas, los activos y la información en diversos sectores. Estas normas brindan marcos sólidos para gestionar los riesgos, mejorar los protocolos de seguridad y garantizar la resiliencia frente a las amenazas. Con la adopción de estas normas, las organizaciones pueden mejorar la seguridad operacional, cumplir las regulaciones y fomentar la confianza en su capacidad para gestionar eficazmente los riesgos potenciales. Normas esenciales ISO/IEC 19790 Information security, cybersecurity and privacy protection — Security requirements for cryptographic modules Publicado en 2025 ISO/IEC 24759 Information security, cybersecurity and privacy protection — Test requirements for cryptographic modules Publicado en 2025 CHF 0 ISO/IEC 27001 Information security, cybersecurity and privacy protection — Information security management systems — Requirements Publicado en 2022 CHF 155 ISO/IEC 27000 Information technology — Security techniques — Information security management systems — Overview and vocabulary Publicado en 2018 CHF 0 ISO/IEC 27701 Information security, cybersecurity and privacy protection — Privacy information management systems — Requirements and guidance Publicado en 2025 CHF 225 ISO/IEC 11889-1 Information technology — Trusted platform module library Part 1: Architecture Revisado en 2021 ISO 45001 Sistemas de gestión de la seguridad y salud en el trabajo — Requisitos con orientación para su uso Publicado en 2018 CHF 196 Cargar más Perspectivas Seguridad de la información: pilar de resiliencia en la era digital En un mundo conectado digitalmente, los datos de su empresa no sólo son esenciales, sino que son la piedra angular de la creación de valor. Pero este recurso inestimable se enfrenta a ciberamenazas incesantes. Sistemas de gestión de la calidad: Introducción ¿Cómo prosperan las empresas exitosas en este mundo cada vez más competitivo? Hay un ingrediente que, tanto para la tienda de la esquina como para los gigantes financieros, es esencial para tener un éxito saludable a largo plazo. Calidad. Las ventajas de implementar un sistema de gestión ambiental para su empresa La priorización de la sostenibilidad ambiental no solo es tendencia: es una estrategia vital para garantizar la salud y la prosperidad de las organizaciones a largo plazo. Equilibrar el crecimiento con la gestión ambiental es más importante que nunca ahora que los impactos del cambio climático aumentan en magnitud y frecuencia. Sectores Seguridad, protección y gestión … 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:35 |
https://www.iso.org/es/perspectivas/lista-filtrada-salud-y-seguridad-en-el-trabajo | ISO - Seguridad y salud en el trabajo 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 Seguridad y salud en el trabajo Identificar peligros de SST y gestionar riesgos Las personas son la base de cualquier empresa. Por eso, es esencial ser plenamente consciente de los peligros de SST, desarrollar estrategias para reducir los riesgos y promover una cultura que mantenga protegido a su personal. Últimos artículos Identificar peligros de SST y gestionar riesgos Equipo de protección personal: proteger a los trabajadores en un lugar de trabajo en constante evolución Seguridad en el trabajo: una guía para proteger la salud de las personas en el trabajo 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 Seguridad y salud en el trabajo 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:35 |
https://young-programmers.blogspot.com/search/label/Web%20Services | Young Programmers Podcast: Web Services skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Showing posts with label Web Services . Show all posts Showing posts with label Web Services . Show all posts Saturday, September 26, 2009 Web app using Scala, Lift and Flickr to Show Pictures Dave Briccetti shows a very simple Web application he is working on for his mom's nature photography Web site, briccettiphoto.com . Written in Scala, it uses the lift Web application framework, and Flickr Web Services to find her pictures. The source code is on GitHub. at 1:40 AM Labels: Flickr , lift , Scala , Web Services Older Posts Home Subscribe to: Comments (Atom) About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ▼  2015 (1) ▼  February (1) This Podcast Moves to YouTube ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ►  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:35 |
http://young-programmers.blogspot.com/2009/07/twitters-doug-williams-visits-my.html | Young Programmers Podcast: Twitter’s Doug Williams Visits My Programming Class skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Sunday, July 19, 2009 Twitter’s Doug Williams Visits My Programming Class Twitter's Doug Williams describes how he got started programming. See Twitter’s Doug Williams Visits My Programming Class : http://briccetti.blogspot.com/2009/07/twitters-doug-williams-visits-my.html at 9:13 PM Labels: guest , interview , twitter Newer Post Older Post Home About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ►  2015 (1) ►  February (1) ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ▼  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ▼  July (14) Tor Norbye Shows JavaFX Recording Music for Computer Games Adding a Second Sprite to SimplePygame (Challenge 4) Solutions to SimplePygame Challenges 1–3 Xturtle With Loops to Make Polygons An Alice Object Reacts to Another Using GIMP to Make Graphics for Scratch and Alice Twitter’s Doug Williams Visits My Programming Class Random Number Problems and Python Solutions Random Numbers in Python: randint and choice Three Simple Python Problems and Their Solutions Power-Up and Shield Making Scratch Graphics with Inkscape Overview of Scratch, Alice, Python and Pygame   | 2026-01-13T09:30:35 |
https://phproundtable.com/show/all-about-web-apis-raml-oauth-hateoas | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 4: All About Web API's, RAML, OAuth, & HATEOAS Panelists: Matt Frost Jeremy Lindblom Mike Stowe Keith Casey Jr Andrew Curioso September 22 2014 All about web API's: designing your API with RAML, authentication with OAuth and discussing the hypermedia-constraint (HATEOAS). All about web api's, it's a very broad term...Application Programming Interface...it covers a lot of things but today we are talking about web api's. We're going to be exploring terms like REST and JSON, what you need to do to consume an api from a php pe About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:35 |
http://anh.cs.luc.edu/handsonPythonTutorial/strings3.html#object-orientation | 2.1. Strings, Part III — Hands-on Python Tutorial for Python 3 Navigation index next | previous | Hands-on Python Tutorial » 2. Objects and Methods » 2.1. Strings, Part III ¶ 2.1.1. Object Orientation ¶ Python is an object-oriented language. Every piece of data and even functions and types are objects. The term object-oriented is used to distinguish Python from earlier languages, classified as procedural languages, where types of data and the operations on them were not connected in the language. The functions we have used so far follow the older procedural programming syntax. In the newer paradigm of object-oriented programming, all data are in objects, and a core group of operations that can be done on some particular type of object are tightly bound to the object and called the object’s methods . For example, strings are objects, and strings “know how” to produce an uppercase version of themselves. Try in the Shell : s = 'Hello!' s . upper () Here upper is a method associated with strings. This means upper is a function that is bound to the string before the dot. This function is bound both logically, and as we see in the new notation, also syntactically. One way to think about it is that each type of data knows operations (methods) that can be applied to it. The expression s.upper() calls the method upper that is bound to the string s and returns a new uppercase string result based on s . Strings are immutable, so no string method can change the original string, it can only return a new string. Confirm this by entering each line individually in the Shell to see the original s is unchanged: s s2 = s . upper () s2 s We are using the new object syntax: object . method ( ) meaning that the method associated with the object’s type is applied to the object . This is just a special syntax for a function call with an object. Another string method is lower , analogous to upper, but producing a lowercase result. Test yourself : How would you write the expression to produce a lowercase version of the string s ? Answer: [1] Try it in the Shell . Test yourself in the Shell : How would you use this string s and both the lower and upper methods to create the string 'hello!HELLO!' ? Hint: [2] Answer: [3] Many methods also take additional parameters between the parentheses, using the more general syntax: object . method ( parameters ) The first of many such methods we will introduce is count : Syntax for count : s .count( sub ) Count and return the number of repetitions of a string sub that appear as substrings inside the string s . Read and make sure you see the answers are correct: >>> tale = 'This is the best of times.' >>> tale . count ( 'i' ) 3 >>> tale . count ( 'is' ) 2 >>> tale . count ( 'That' ) 0 >>> tale . count ( ' ' ) 5 There is a blank between the quotes in the line above. Blanks are characters like any other (except you can’t see them)! Just as the parameter can be replaced by a literal or any expression, the object to which a method is bound with the dot may also be given by a literal, or a variable name, or any expression that evaluates to the right kind of object in its place. This is true for any method call. Technically the dot between the object and the method name is an operator, and operators have different levels of precedence. It is important to realize that this dot operator has the highest possible precedence. Read and see the difference parentheses make in the expressions: >>> 'hello ' + 'there' . upper () 'hello THERE' >>> ( 'hello ' + 'there' ) . upper () 'HELLO THERE' To see if you understand this precedence, predict the results of each line and then test in the Shell : 3 * 'X' . count ( 'XXX' ) ( 3 * 'X' ) . count ( 'XXX' ) There are 0 ‘XXX’s in ‘X’, but 1 ‘XXX’ in ‘XXX’. Python lets you see all the methods that are bound to an object (and any object of its type) with the built-in function dir . To see all string methods, supply the dir function with any string. For example, try in the Shell : dir ( '' ) Many of the names in the list start and end with two underscores, like __add__. These are all associated with methods and pieces of data used internally by the Python interpreter. You can ignore them for now. The remaining entries in the list are all user-level methods for strings. You should see lower and upper among them. Some of the methods are much more commonly used than others. Object notation object . method ( parameters ) has been illustrated so far with just the object type str , but it applies to all types. Later in the tutorial methods such as the following will be discussed: If seq is a list , seq.append(element) appends element to the end of the list. If myData is a file , myData.read() will read and return the entire contents of the file.... 2.1.2. String Indices ¶ A string is a sequence of smaller components (individual characters), and it is often useful to deal with parts of strings. Python indexes the characters in a string, starting from 0, so for instance, the characters in the string 'computer' have indices: character c o m p u t e r index 0 1 2 3 4 5 6 7 Each index is associated with a character, and you reference the individual characters much like in a dictionary. Try the following. (You can skip the comments that make the indices explicit.) Enter in the Shell : # 01234567 s = 'computer' s [ 0 ] s [ 5 ] s [ 8 ] You cannot refer directly to a character that is not there. Indices only go to 7 in the example above. Recall the len function, which gives the length of a sequence. It works on strings. Guess the following value, and test in the Shell : len ( s ) A common error is to think the last index will be the same as the length of the string, but as you saw above, that leads to an execution error. If the length of some string is 5, what is the index of its last character? What if the length is 35? Hopefully you did not count by ones all the way from 0. The indices for a string of length n are the elements of the sequence range(n) , which goes from 0 through n-1, or the length of the string minus one, which is 5-1=4 or 35-1 = 34 in these examples. Sometimes you are interested in the last few elements of a string and do not want to do calculations like this. Python makes it easy. You can index from the right end of the string. Since positive integers are used to index from the front, negative integers are used to index from the right end, so the more complete table of indices for 'computer' gives two alternatives for each character: character c o m p u t e r index 0 1 2 3 4 5 6 7 index from the right end -8 -7 -6 -5 -4 -3 -2 -1 Predict and test each individual line, continuing in the Shell : s [ - 1 ] s [ - 3 ] s [ - 10 ] it = 'horse' len ( it ) it [ - 1 ] it [ 1 ] Be careful - remember what the initial index is! 2.1.3. String Slices ¶ It is also useful to extract larger pieces of a string than a single character. That brings us to slices . Try this expression using slice notation, continuing in the Shell : s [ 0 : 4 ] Note that s[4] is the first character past the slice. The simplest syntax for a slice of a string s is: s[ startIndex : pastIndex ] This refers to the substring of s starting at index startIndex and stopping just before index pastIndex. Warning It confuses many people that the index after the colon is not the index of the final character in the slice. The second index is past the end of the slice. Predict and try each line individually in the Shell : s [ 2 : 5 ] s [ 1 : 3 ] If you omit the first index, the slice starts from the beginning. If you omit the second index, the slice goes all the way to the end. Predict and try each line individually in the Shell : s [: 3 ] s [ 5 :] s [:] Predict and try each line individually in the Shell : word = 'program' word [ 2 : 4 ] word [ 1 : - 3 ] word [ 3 :] word [ 3 : 3 ] word [: 1 ] + word [ 4 :] Python evaluates slices in a more forgiving manner than when indexing single characters. In a slice, if you give an index past a limit of where it could be, Python assumes you mean the actual end. Predict and try each line individually in the Shell : word [: 9 ] word [ 8 : 10 ] Enter a slice expression using the variable word from above that produces 'gra' . A useful string method that uses the ideas of indices and slices is find . Syntax options for find method with a string s : s .find( sub ) s .find( sub , start ) s .find( sub , start , end ) Return the integer index in the string s of the beginning of the first complete occurrence of the substring sub . If sub does not appear inside s, return -1. The value -1 would be an impossible result if sub were found, so if -1 is returned, sub must not have been found. If parameters start and end are not included in the parameter list, the search is through the whole string s . If an integer value is given for start , the search starts at index start . If an integer value is given for end , the search ends before index end . In other words if start and end appear, then the search is through the slice s [ start : end ], but the index returned is still counted from the beginning of s . For example, check that the following make sense. The comment line is just there to help you count: >>> # 01234567890 >>> s = 'Mississippi' >>> s . find ( 'i' ) 1 >>> s . find ( 'si' ) 3 >>> s . find ( 'sa' ) -1 >>> s . find ( 'si' , 4 ) 6 Predict and try each line in the Shell : # 0123456789012 line = 'Hello, there!' line . find ( 'e' ) line . find ( 'he' ) line . find ( 'e' , 10 ) line . find ( 'he' , 10 ) We will consider more string methods later, but we can already do useful things with the ones introduced. Inside the Shell, you can look up documentation on any of the methods listed with the dir function. Here is a place that you want to refer to the method itself, not invoke the method, so note that you get help for s.find not for s.find() . Assuming you defined the string s in the Shell earlier, try in the Shell help ( s . find ) The Python documentation uses square brackets to indicate optional elements which get a default value if you leave them out. This shortens the syntax descriptions. If you want method documentation when you do not have a variable of the type created, you can also use the type name. Try in the Shell : dir ( str ) help ( str . capitalize ) In the help documentation for a function with one or more parameters, you may see what looks like a final parameter / . Ignore it. It documents a technical restriction on parameters. It is not actually a parameter. Indexing and slicing works on any kind of Python sequence, so you can index or slice lists also.* Read* this Shell session: >>> vals = [ 5 , 7 , 9 , 22 , 6 , 8 ] >>> vals [ 1 ] 7 >>> vals [ - 2 ] 6 >>> vals [ 1 : 4 ] [7, 9, 22] Unlike strings, lists are mutable, as you will see in Appending to a List . Indices and slices can also be used in assignment statements to change lists, but in this tutorial we not need list indexing, and we will not discuss this subject further. 2.1.4. Index Variables ¶ All the concrete examples in the last two sections used literal numbers for the indices. That is fine for learning the idea, but in practice, variables or expressions are almost always used for indices. As usual the variable or expression is evaluated before being used. Try in Idle and see that the example program index1.py makes sense: s = 'word' print ( 'The full string is: ' , s ) n = len ( s ) for i in range ( n ): print () print ( 'i =' , i ) print ( 'The letter at index i:' , s [ i ]) print ( 'The part before index i (if any):' , s [: i ]) print ( 'The part before index i+2:' , s [: i + 2 ]) We will use index variables in more practical situations as we explain more operations with strings. 2.1.5. split ¶ Syntax options for the split method with a string s : s .split() s .split( sep ) The first version splits s at any sequence of whitespace (blanks, newlines, tabs) and returns the remaining parts of s as a list. If a string sep is specified, it is the separator that gets removed from between the parts of the list. For example, read and follow: >>> tale = 'This is the best of times.' >>> tale . split () ['This', 'is', 'the', 'best', 'of', 'times.'] >>> s = 'Mississippi' >>> s . split ( 'i' ) ['M', 'ss', 'ss', 'pp', ''] >>> s . split () # no white space ['Mississippi'] Predict and test each line in the Shell : line = 'Go: Tear some strings apart!' seq = line . split () seq line . split ( ':' ) line . split ( 'ar' ) lines = 'This includes \\ nsome new \\ nlines.' lines . split () 2.1.6. join ¶ Join is roughly the reverse of split. It joins together a sequence of strings. The syntax is rather different. The separator sep comes first, since it has the right type (a string). Syntax for the join method: sep .join( sequence ) Return a new string obtained by joining together the sequence of strings into one string, interleaving the string sep between sequence elements. For example (continuing in the Shell from the previous section, using seq ), follow: >>> ' ' . join ( seq ) 'Go: Tear some strings apart!' >>> '' . join ( seq ) 'Go:Tearsomestringsapart!' >>> '//' . join ( seq ) 'Go://Tear//some//strings//apart!' Predict and try each line, continuing in the Shell : '##' . join ( seq ) ':' . join ([ 'one' , 'two' , 'three' ]) The methods split and join are often used in sequence: 2.1.6.1. Underscore Exercise ¶ Write a program underscores.py that would input a phrase from the user and print out the phrase with the white space between words replaced by an underscore. For instance if the input is the best one , then it would print the_best_one . The conversion can be done in one or two statements using the recent string methods. 2.1.6.2. Acronym Exercise ¶ * An acronym is a string of capital letters formed by taking the first letters from a phrase. For example, SADD is an acronym for ‘students against drunk driving’. Note that the acronym should be composed of all capital letters even if the original words are not. Write a program acronym.py that has the user input a phrase and then prints the corresponding acronym. To get you started, here are some things you will need to do. First check that you understand the basic syntax to accomplish the different individual tasks: Indicate the proper syntax using a Python function or operation will allow you to accomplish each task. Invent appropriate variable names for the different parts. These are not complete instructions! The idea is to make sure you know the basic syntax to use in all these situations. See the questions after the list to help you put together the final program. What type of data will the input be? What type of data will the output be? Get the phrase from the user. Convert to upper case. Divide the phrase into words. Initialize a new empty list, letters . Get the first letter of each word. Append the first letter to the list letters . Join the letters together, with no space between them. Print the acronym. Which of these steps is in a loop? What for statement controls this loop? Put these ideas together and write and test your program acronym.py . Make sure you use names for the objects that are consistent from one line to the next! (You might not have done that when you first considered the syntax and ideas needed for 1-9 above individually.) 2.1.7. Further Exploration ¶ As the dir('') list showed, there are many more operations on strings than we have discussed, and there are further variations of the ones above with more parameters. Methods startswith , endswith , and replace are discussed later in More String Methods . If you want to reach a systematic reference from inside Idle, go to Help ‣ Python Docs ‣ Library Reference , and find the section Built-in Types, and then the subsection for type str. Many methods use features we have not discussed yet, but currently accessible methods are capitalize , title , strip , rfind , .... [1] s.lower() [2] Use a plus sign to concatenate the pieces. [3] s.lower() + s.upper() Table Of Contents 2.1. Strings, Part III 2.1.1. Object Orientation 2.1.2. String Indices 2.1.3. String Slices 2.1.4. Index Variables 2.1.5. split 2.1.6. join 2.1.6.1. Underscore Exercise 2.1.6.2. Acronym Exercise 2.1.7. Further Exploration Previous topic 2. Objects and Methods Next topic 2.2. More Classes and Methods This Page Show Source Quick search Enter search terms or a module, class or function name. Navigation index next | previous | Hands-on Python Tutorial » 2. Objects and Methods » © Copyright 2019, Dr. Andrew N. Harrington. Last updated on Jan 05, 2020. Created using Sphinx 1.3.1+. | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-event-request-response.html | Fonctionnement de Lambda@Edge avec les demandes et les réponses - Amazon CloudFront Fonctionnement de Lambda@Edge avec les demandes et les réponses - 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. Fonctionnement de Lambda@Edge avec les demandes et les réponses Lorsque vous associez une CloudFront distribution à une fonction Lambda @Edge, elle CloudFront intercepte les demandes et les réponses à CloudFront des emplacements périphériques. Vous pouvez exécuter des fonctions Lambda lorsque les CloudFront événements suivants se produisent : Quand CloudFront reçoit une demande d'un téléspectateur (demande du téléspectateur) Avant CloudFront de transmettre une demande à l'origine (demande d'origine) Quand CloudFront reçoit une réponse de l'origine (réponse d'origine) Before CloudFront renvoie la réponse au spectateur (réponse du spectateur) Si vous l'utilisez AWS WAF, la demande du visualiseur Lambda @Edge est exécutée une fois les AWS WAF règles appliquées. Pour plus d’informations, consultez Utilisation des demandes et des réponses et Structure d'événement Lambda@Edge . 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 Personnalisation avec Lambda@Edge Comment utiliser Lambda@Edge 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:35 |
https://young-programmers.blogspot.com/search/label/shdh#main | Young Programmers Podcast: shdh skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Showing posts with label shdh . Show all posts Showing posts with label shdh . Show all posts Sunday, August 23, 2009 SuperHappyDevHouse 34 Interviews, Part Two Interviews with programmers and hardware hackers from SuperHappyDevHouse 34, part 2 of 2. Kevin Gadd talks about his dad bringing home computers for him to play with, and learning to program them, and his career making videogames. Drew Perttula ’s dad brought home computers but no games, so Drew had to write his own. He got interested in visual effects and computer graphics. He works at DreamWorks Animation. Mike Lundy works for Nasa in Mountain View. He started programming around age 10 on a PCjr running BASIC. He works in the Intelligent Robotics Group at NASA. He hopes the software he works on will eventually run on the Moon or Mars. at 3:14 PM Labels: hacker , interview , programmer , shdh , shdh34 SuperHappyDevHouse 34 Interviews, Part One Interviews with programmers and hardware hackers from SuperHappyDevHouse 34. Joel Franusic introduces SuperHappyDevHouse and talks about how he learned programming from his dad, an embedded systems engineer. Joshua Neal shows an LED connected to an Arduino board. Jens Andersson shows a program, Colors!, for drawing on the Nintendo DS. Otavio Good shows a polar bear drawing he made using that program. Steve Okay shows an Arduino-controlled robot he built, and describes being inspired by the movie Tron to stay up all night and make a light cycle game. Ben McGraw talks about programming role playing games. Caroline Ratajski talks about how she started at age 9 with a BASIC text game, then learned web development and networking, and continued with a formal computer science education leading to her current work in communications signals analysis. More interviews follow in part two. at 1:32 PM Labels: arduino , interview , shdh , shdh34 Older Posts Home Subscribe to: Comments (Atom) About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ▼  2015 (1) ▼  February (1) This Podcast Moves to YouTube ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ►  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:35 |
https://penneo.com/nl/ | Penneo: Veilige digitale ondertekening met itsme® en .beID Producten Penneo Sign Validator Waarom Penneo Integraties Oplossingen Toepassingen Digitaal ondertekenen Documentbeheer Vul en onderteken PDF-formulieren Automatisering van ondertekeningsprocessen eIDAS-conformiteit Branchen Audit en boekhouding Financiële sector Juridische sector Vastgoedsector Administratie en HR Prijzen Bronnen Knowledge hub Trust Center Productupdates SIGN Helpcentrum KYC Helpcentrum Systeem status LOG IN Bekijk hoe het werkt BOEK EEN AFSPRAAK NL DA EN NO FR Producten Penneo Sign Validator Waarom Penneo Integraties Oplossingen Audit en boekhouding Financiële sector Juridische sector Vastgoedsector Administratie en HR Toepassingen Digitaal ondertekenen Documentbeheer Vul en onderteken PDF-formulieren Automatisering van ondertekeningsprocessen eIDAS-conformiteit Prijzen Bronnen Knowledge hub Trust Center Productupdates SIGN Helpcentrum KYC Helpcentrum Systeem status BOEK EEN AFSPRAAK GRATIS UITPROBEREN LOG IN DA EN NO FR NL Penneo Sign Meld u aan bij Penneo Sign. LOG IN Penneo KYC Meld u aan bij Penneo KYC. LOG IN Versimpel je documentstromen met een veilige digitale ondertekening Met Penneo onderteken je documenten veilig, efficiënt en volledig conform eIDAS. Onze oplossing helpt organisaties om complexe processen te stroomlijnen en foutgevoelige handmatige stappen te elimineren. BOEK EEN AFSPRAAK Ontdek hoe het werkt Wij hebben het vertrouwen van meer dan 3.000 organisaties gewonnen Penneo Sign Een oplossing die elektronische handtekeningen gemakkelijk, handig en veilig maakt. Onderteken documenten met gekwalificeerde itsme®-handtekeningen of geavanceerde .beID-handtekeningen, automatiseer het ondertekeningsproces en valideer op een efficiënte en conforme manier de identiteit van de ondertekenaars. Meer informatie over Penneo Sign Integraties en open API Penneo integreert met de meest gebruikte digitale tools om ervoor te zorgen dat alle workflows met elkaar verbonden zijn in een technisch ecosysteem. Penneo biedt verschillende ingebouwde integraties met uiteenlopende softwaretoepassingen, zoals CRM- en ERP-systemen, .beID en itsme®. Meer informatie over onze integraties Met een CSAT van +88% delen onze klanten graag hun verhalen “We willen echt niet alleen een relatie tussen leverancier en klant, we voelen ons echt partners van Penneo. Want samenwerken levert voor ons beiden meerwaarde op en leidt tot een langdurige relatie.” – Charlotte Pille, Partner bij VGD MEER VERHALEN VAN KLANTEN BEKIJKEN Digitaal vertrouwen tussen partners Naarmate organisaties meer en meer digitaal met elkaar omgaan, is de behoefte aan vertrouwen groter dan ooit. Penneo zorgt voor vertrouwen tussen bedrijven en hun klanten door een platform te bieden dat voldoet aan de hoogste beveiligingsnormen, alsook aan de Europese en nationale wetgeving. BEZOEK ONS TRUST CENTER Bespaar tijd en middelen 81% van alle jaarverslagen in Denemarken worden ondertekend met Penneo. 7 miljoen documenten werden in 2024 ondertekend met Penneo. 60% van de documenten die met Penneo worden verzonden, worden binnen 24 uur ondertekend. Onze middelen verkennen Wat is een digitale handtekening? LEES MEER 9 essentiële kenmerken voor een digitaal ondertekenprogramma LEES MEER Bouw je digitaal ecosysteem: Penneo & Partners LEES MEER Kijk wat u kunt bereiken met Penneo BOEK EEN AFSPRAAK GRATIS UITPROBEREN Producten Penneo Sign Prijzen Integraties Open API Validator Waarom Penneo Oplossingen Audit en boekhouding Financiële sector Juridische sector Vastgoedsector Administratie en HR Toepassingen Digitaal ondertekenen Documentbeheer Vul en onderteken PDF-formulieren Automatisering van ondertekeningsprocessen eIDAS-conformiteit Bronnen Knowledge hub Trust Center Productupdates SUPPORT SIGN Helpcentrum KYC Helpcentrum Systeem status Bedrijf Over ons Vacatures Privacybeleid Voorwaarden Cookies Accessibility Statement Whistleblower Policy Neem contact op PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:35 |
https://young-programmers.blogspot.com/search/label/scratch#main | Young Programmers Podcast: scratch skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Showing posts with label scratch . Show all posts Showing posts with label scratch . Show all posts Friday, December 25, 2009 Invisible Player Escapes Maze Escape the maze. You are invisible, and so are all the obstacles unless they are close to you. Illustrates use of the ghost effect, and broadcast. http://scratch.mit.edu/projects/davebric/818925 at 1:37 PM Labels: scratch Thursday, December 24, 2009 Growing Player Escapes Maze Escape the maze before you grow too big. Illustrates use of the timer, and “if touching color.” The Scratch project is here: http://scratch.mit.edu/projects/davebric/818258 at 2:59 PM Labels: scratch Wednesday, September 30, 2009 Sound Flies a Helicopter in Scratch Sound (your voice, perhaps) controls the altitude of a helicopter which you try to keep from hitting the mountains. at 3:25 AM Labels: scratch , sound Tuesday, August 4, 2009 Platform Example, Very Simple Here is a sprite that will drop onto red platforms, and gains the ability to fly from a power-up. Scratch project file . at 1:51 AM Labels: scratch Sunday, August 2, 2009 Cat Saves the Villager Scratch Project Walkthrough Here’s a walkthrough of Cat Saves the Villager . It shows several characters that deliver lines and interact using broadcast . Dave Briccetti created it in 35 minutes with six students in class at DVC College for Kids. at 7:31 PM Labels: scratch Friday, July 24, 2009 Recording Music for Computer Games Student, cellist, guitarist and programmer Ethan Kuefner (@jazzcello on Twitter) visited my programming classes and showed how to record music and sound effects, and put them into computer games. We used Scratch, Python and Pygame, GarageBand and Audacity. at 7:15 PM Labels: audacity , garageband , music , pygame , python , scratch , sound Tuesday, July 21, 2009 Using GIMP to Make Graphics for Scratch and Alice Shows using the GIMP (GNU Image Manipulation Program) to create a costume for a Scratch sprite, and a texture for Alice. at 11:16 AM Labels: alice , GIMP , scratch Sunday, July 19, 2009 Power-Up and Shield Shows how to have your character power up with a shield, which diminishes over time and can be reacquired with another power-up. at 1:04 PM Labels: scratch Making Scratch Graphics with Inkscape Shows making a simple drawing with Inkscape, exporting it as a bitmap, and then importing the image into Scratch. at 1:02 PM Labels: art , inkscape , scratch Overview of Scratch, Alice, Python and Pygame Software developer and teacher Dave Briccetti demonstrates software he uses to teach programming to kids: Scratch, Alice, Python and Pygame. at 12:18 PM Labels: alice , pygame , python , scratch Home Subscribe to: Comments (Atom) About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ▼  2015 (1) ▼  February (1) This Podcast Moves to YouTube ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ►  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:35 |
https://www.iso.org/es/contents/data/sdg/SDG15.html | ISO - Life on Land 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 15 Life on Land 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 15: Life on Land Protect, restore and promote sustainable use of terrestrial ecosystems, sustainably manage forests, combat desertification, and halt and reverse land degradation and halt biodiversity loss Sustainable Development Goal 15 (SDG 15) aims to protect, restore and promote sustainable use of terrestrial ecosystems. This goal is crucial for preserving biodiversity, ensuring sustainable forest management, and combating land degradation. At ISO, we are committed to supporting SDG 15 through our standards, which provide frameworks and solutions that promote sustainable land use practices and protect terrestrial ecosystems. How ISO Standards Support SDG 15 ISO standards play a vital role in supporting SDG 15 by addressing key aspects of terrestrial ecosystem management and biodiversity conservation. Our standards help organizations implement sustainable practices, manage natural resources responsibly, and protect biodiversity. Here are some of the relevant standards: ISO 14055-1: Environmental management — Guidelines for establishing good practices for combatting land degradation and desertification — Part 1: Good practices framework Provides guidelines for establishing good practices to combat land degradation and desertification. Helps organizations and communities implement effective strategies for sustainable land management and ecosystem restoration. ISO 38200: Chain of custody of wood and wood-based products Specifies requirements for a chain of custody of wood and wood-based products. Supports sustainable forest management by ensuring the traceability of wood products throughout the supply chain, promoting responsible sourcing practices. Take Action: Implement ISO Standards to Support SDG 15 Interested in learning how your organization can contribute to protecting life on land through the implementation of ISO standards? Download our comprehensive guide to understand the role of ISO standards in achieving SDG 15 and other global goals. Together, we can work towards sustainable terrestrial ecosystems and biodiversity conservation. ISO and agriculture Learn about the valuable role that ISO International Standards play in agriculture and an overview of the many standards available. Normas ODS Objetivo 15: 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:35 |
https://docs.aws.amazon.com/ja_jp/AmazonCloudFront/latest/DeveloperGuide/kvs-with-functions-kvp.html | キーと値のデータを操作する - Amazon CloudFront キーと値のデータを操作する - Amazon CloudFront ドキュメント Amazon CloudFront デベロッパーガイド key-value ペアを使用する (コンソール) CloudFront KeyValueStore について key-value ペアを使用する (AWS CLI) key-value ペアを使用する (API) キーと値のデータを操作する このトピックでは、既存のキーバリューストアにキーと値のペアを追加する方法について説明します。キーバリューストアを最初に作成するときに、キーと値のペアを含めるには、「 キーバリューストアの作成 」を参照してください。 トピック key-value ペアを使用する (コンソール) CloudFront KeyValueStore について key-value ペアを使用する (AWS CLI) key-value ペアを使用する (API) key-value ペアを使用する (コンソール) CloudFront コンソールを使用してキーと値のペアを操作できます。 キーと値のペアを使用するには AWS マネジメントコンソールにサインインし、 https://console.aws.amazon.com/cloudfront/v4/home#/functions で CloudFront コンソールの [関数] ページを開きます。 [KeyValueStores] タブを選択します。 変更するキーバリューストアを選択します。 [キーと値のペア] セクションで、 [編集] を選択します。 キーと値のペアを追加または削除したり、既存のキーと値のペアの値を変更したりできます。 完了したら、[ 変更の保存 ] を選択します。 CloudFront KeyValueStore について ヒント CloudFront KeyValueStore API は、認証に Signature Version 4A (SigV4A) を使用するグローバルサービスです。SigV4A で一時的な認証情報を使用するには、Version 2 のセッショントークンが必要です。詳細については、「 CloudFront KeyValueStore API での一時的な認証情報の使用 」を参照してください。 AWS Command Line Interface (AWS CLI) または独自のコードを使用して CloudFront KeyValueStore API を呼び出す場合は、以降のセクションを参照してください。 キーバリューストアとそのキーと値のペアを操作する場合、呼び出すサービスはユースケースによって異なります。 既存のキーバリューストア内の key-value ペアをプログラムで操作するには、CloudFront KeyValueStore サービスを使用します。 キーバリューストアを最初に作成するときに、キーバリューストアにキーと値のペアを含めるには、CloudFront サービスを使用します。 CloudFront API と CloudFront KeyValueStore API の両方に DescribeKeyValueStore オペレーションがあります。さまざまな理由でこれらを呼び出すことができます。違いを理解するには、次の表を参照してください。 CloudFront DescribeKeyValueStore API CloudFront KeyValueStore DescribeKeyValueStore API キーバリューストアに関するデータ キーバリューストア自体の最終変更時のステータスや日付などのデータを返します。 ストレージリソースのコンテンツに関するデータ (ストア内のキーと値のペア、コンテンツのサイズ) を返します。 キーバリューストアを識別するデータ キーバリューストアの ETag 、UUID、ARN を返します。 キーバリューストアの ETag と ARN を返します。 メモ 各 DescribeKeyValueStore オペレーションは、別々の ETag を返します。 ETags は置き換え可能ではありません。 API オペレーションを呼び出してアクションを実行する際は、適切な API から ETag を指定する必要があります。例えば、CloudFront KeyValueStore の DeleteKey オペレーションでは、CloudFront KeyValueStore DescribeKeyValueStore オペレーションから返された ETag を指定します。 CloudFront KeyValueStore を使用して CloudFront Functions を呼び出す場合、キーバリューストアの値は関数の呼び出し中に更新または変更されません。更新は、関数の呼び出しの合間に処理されます。 key-value ペアを使用する (AWS CLI) CloudFront KeyValueStore に関しては、以下の AWS Command Line Interface コマンドを実行できます。 目次 key-value ペアの一覧表示 key-value ペアの取得 キーバリューストアの説明 key-value ペアの作成 key-value ペアの削除 key-value ペアの更新 key-value ペアの一覧表示 キーバリューストアの key-value ペアを一覧表示するには、次のコマンドを実行します。 aws cloudfront-keyvaluestore list-keys \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example レスポンス { "Items": [ { "Key": "key1", "Value": "value1" } ] } key-value ペアの取得 キーバリューストアの key-value ペアを取得するには、次のコマンドを実行します。 aws cloudfront-keyvaluestore get-key \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example レスポンス { "Key": "key1", "Value": "value1", "ItemCount": 1, "TotalSizeInBytes": 11 } キーバリューストアの説明 キーバリューストアの説明を取得するには、次のコマンドを実行します。 aws cloudfront-keyvaluestore describe-key-value-store \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example レスポンス { "ETag": "KV1F83G8C2ARO7P", "ItemCount": 1, "TotalSizeInBytes": 11, "KvsARN": "arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example", "Created": "2024-05-08T07:48:45.381000-07:00", "LastModified": "2024-08-05T13:50:58.843000-07:00", "Status": "READY" } key-value ペアの作成 キーバリューストアで key-value ペアを作成するには、次のコマンドを実行します。 aws cloudfront-keyvaluestore put-key \ --if-match=KV1PA6795UKMFR9 \ --key=key2 \ --value=value2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example レスポンス { "ETag": "KV13V1IB3VIYZZH", "ItemCount": 3, "TotalSizeInBytes": 31 } key-value ペアの削除 key-value ペアのを削除するには、次のコマンドを実行します。 aws cloudfront-keyvaluestore delete-key \ --if-match=KV13V1IB3VIYZZH \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example 出力 { "ETag": "KV1VC38T7YXB528", "ItemCount": 2, "TotalSizeInBytes": 22 } key-value ペアの更新 単数または複数の key-value ペアを更新するには、 update-keys コマンドを使用します。例えば、既存の key-value ペアを削除して別の key-value ペアを作成するには、次のコマンドを実行します。 aws cloudfront-keyvaluestore update-keys \ --if-match=KV2EUQ1WTGCTBG2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example \ --deletes '[ { "Key":"key2"}]' \ --puts '[ { "Key":"key3","Value":"value3"}]' レスポンス { "ETag": "KV3AEGXETSR30VB", "ItemCount": 3, "TotalSizeInBytes": 28 } key-value ペアを使用する (API) キーと値のペアをプログラムで操作するには、このセクションに従います。 目次 キーバリューストアへの参照の取得 キーバリューストア内のキーと値のペアを変更する CloudFront KeyValueStore のコード例 キーバリューストアへの参照の取得 CloudFront KeyValueStore API を使用して書き込みオペレーションを呼び出す際は、キーバリューストアの ARN と ETag を指定する必要があります。このデータを取得するには、以下を実行します。 キーバリューストアへの参照を取得するには CloudFront ListKeyValueStores API オペレーションを使用して、キーバリューストアのリストを取得します。変更するキーバリューストアを見つけます。 CloudFrontKeyValueStore DescribeKeyValueStore API オペレーション を使用して、前のステップからのキーバリューストアを指定します。 この応答には、キーバリューストアの ARNと ETag が含まれます。 ARN には、次の例に示すように AWS アカウント 番号、定数 key-value-store 、UUID が含まれます。 arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 ETag は、次の例のようになります。 ETVABCEXAMPLE2 キーバリューストア内のキーと値のペアを変更する 更新するキーと値のペアを含むキーバリューストアを指定できます。 次の CloudFront KeyValueStore API オペレーションを参照してください。 CloudFrontKeyValueStore DeleteKey – キーと値のペアを削除します。 CloudFrontKeyValueStore GetKey – キーと値のペアを返します。 CloudFrontKeyValueStore ListKeys – キーと値のペアのリストを返します。 CloudFrontKeyValueStore PutKey – 以下のタスクを実行できます。 1 つのキーバリューストアに 1 つのキーと値のペアを作成する: この場合は、新しいキー名と値を指定します。 1 つの既存のキーと値のペアに別の値を設定する: この場合は、既存のキー名と新しいキー値を指定します。 CloudFrontKeyValueStore UpdateKeys – 1 つの all-or-nothing オペレーションで、以下の 1 つ以上のアクションを実行できます。 1 つ以上のキーと値のペアを削除する 1 つ以上のキーと値のペアを新規作成する 1 つ以上の既存のキーと値のペアに別の値を設定する CloudFront KeyValueStore のコード例 次のコードは、キーバリューストアの DescribeKeyValueStore API オペレーションを呼び出す方法を示しています。 const { CloudFrontKeyValueStoreClient, DescribeKeyValueStoreCommand, } = require("@aws-sdk/client-cloudfront-keyvaluestore"); require("@aws-sdk/signature-v4-crt"); (async () => { try { const client = new CloudFrontKeyValueStoreClient( { region: "us-east-1" }); const input = { KvsARN: "arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111", }; const command = new DescribeKeyValueStoreCommand(input); const response = await client.send(command); } catch (e) { console.log(e); } })(); ブラウザで JavaScript が無効になっているか、使用できません。 AWS ドキュメントを使用するには、JavaScript を有効にする必要があります。手順については、使用するブラウザのヘルプページを参照してください。 ドキュメントの表記規則 キーと値のペアのファイル形式 Lambda@Edge でカスタマイズする このページは役に立ちましたか? - はい ページが役に立ったことをお知らせいただき、ありがとうございます。 お時間がある場合は、何が良かったかお知らせください。今後の参考にさせていただきます。 このページは役に立ちましたか? - いいえ このページは修正が必要なことをお知らせいただき、ありがとうございます。ご期待に沿うことができず申し訳ありません。 お時間がある場合は、ドキュメントを改善する方法についてお知らせください。 | 2026-01-13T09:30:35 |
https://aws.amazon.com/es/waf/ | Firewall de aplicaciones web - Protección de API web - AWS WAF - AWS Saltar al contenido principal Filter: Todo English Contáctenos AWS Marketplace Soporte Mi cuenta Búsqueda Filter: Todo Iniciar sesión en la consola Crear cuenta AWS Web Application Firewall Información general Características Precios Introducción Recursos Más Productos › Seguridad, identidad y cumplimiento › AWS WAF Obtenga 10 millones de solicitudes habituales de control de bots al mes con el nivel gratuito de AWS → AWS WAF Proteja sus aplicaciones web contra exploits comunes Introducción a AWS WAF Ventajas que ofrece AWS WAF Ahorre tiempo con las reglas administradas Ahorre tiempo con las reglas administradas para que pueda dedicar más tiempo a la creación de aplicaciones. Supervise, bloquee o limite la velocidad de los bots Supervise, bloquee o limite con mayor facilidad los bots comunes y omnipresentes. Reduzca los pasos de configuración de seguridad Acelere la configuración de seguridad compleja con una interfaz consolidada que reduce la complejidad y los pasos de configuración de la implementación de la seguridad hasta en un 80 %. Visibilidad centralizada y procesable Una interfaz única e integral combina las funciones de seguridad principales con protecciones especializadas para socios para mejorar la visibilidad y los controles de seguridad. Este enfoque unificado transforma los datos de seguridad en información procesable, lo que elimina la fricción operativa y acelera la respuesta a los riesgos. Refuerce la postura de seguridad Los paquetes de protección preconfigurados aprovechan la experiencia en seguridad de AWS para ofrecer plantillas de protección instantáneas para sectores y tipos de carga de trabajo específicos, como API, aplicaciones PHP y servicios web. Estas plantillas se optimizan de forma continua para garantizar una seguridad actualizada sin necesidad de contar con una amplia experiencia en implementación. Obtenga recomendaciones de seguridad continuas para reforzar la postura general de seguridad. ¿Por qué utilizar AWS WAF? AWS WAF le permite crear reglas de seguridad que controlan el tráfico de bots y bloquean los patrones de ataque comunes, como la inyección de código SQL o el scripting entre sitios (XSS). Reproducir Casos de uso Filtre el tráfico web Cree reglas para filtrar las solicitudes web en función de condiciones como la dirección IP, los encabezados y cuerpos HTTP o los URI personalizados. Obtenga más información sobre la creación de reglas Prevenga el fraude por toma de posesión de cuentas Supervise la página de inicio de sesión de su aplicación para detectar el acceso no autorizado a las cuentas de usuario mediante credenciales comprometidas. Obtenga más información sobre la prevención del fraude Protección automática contra DDoS de capa 7 Diseñado para supervisar continuamente y mitigar de manera automática los eventos de denegación de servicio distribuida (DDoS) de la capa de aplicación (capa 7) en cuestión de segundos. Implementación rápida de la seguridad Lance nuevas aplicaciones con confianza mediante la configuración de incorporación guiada optimizada, con una interfaz de una sola página para activar los valores predeterminados de seguridad preconfigurados y adaptados a sus necesidades. Refuerce la postura de seguridad A través de paquetes de reglas seleccionados por expertos, visibilidad consolidada y recomendaciones continuas, obtendrá protección inmediata para optimizar su postura de seguridad. Introducción a AWS WAF Introducción a AWS WAF Explore AWS WAF Contacte a un experto Contacte con nosotros Cree una cuenta de AWS Aprender ¿Qué es AWS? ¿Qué es la computación en la nube? ¿Qué es la IA agéntica? Centro de conceptos de computación en la nube Seguridad en la nube de AWS Novedades Blogs Notas de prensa Recursos Introducción Formación Centro de confianza de AWS Biblioteca de soluciones de AWS Centro de arquitectura Preguntas frecuentes sobre cuestiones técnicas y productos Informes de analistas Socios de AWS Desarrolladores Centro de creadores SDK y herramientas .NET en AWS Python en AWS Java en AWS PHP en AWS JavaScript en AWS Ayuda Contacto Abra un ticket de soporte técnico AWS re:Post Centro de conocimientos Información general de AWS Support Reciba ayuda de expertos Accesibilidad de AWS Asuntos jurídicos English Volver arriba Amazon es un empleador que ofrece igualdad de oportunidades: minorías, mujeres, discapacitados, veteranos, identidad de género, orientación sexual y edad. x facebook linkedin instagram twitch youtube podcasts email Privacidad Términos del sitio Preferencias de cookies © 2026, Amazon Web Services, Inc. o sus empresas afiliadas. Todos los derechos reservados. | 2026-01-13T09:30:35 |
https://www.php.net/manual/fr/function.mailparse-uudecode-all.php | PHP: mailparse_uudecode_all - 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 Extensions sur les mathématiques » « mailparse_stream_encode Manuel PHP Référence des fonctions Extensions relatives aux emails Mailparse Fonctions Mailparse Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other mailparse_uudecode_all (PECL mailparse >= 0.9.0) mailparse_uudecode_all — Scanne les données du fichier et extrait tous les fichiers encodés qui s'y trouvent Description mailparse_uudecode_all ( resource $fp ): array Scanne les données du fichier fourni et extrait, dans un fichier temporaire, tous les fichiers encodés qui s'y trouvent. Liste de paramètres fp Un pointeur de fichier valide. Valeurs de retour Retourne un tableau de tableaux associatifs listant les informations sur les noms de fichiers. filename Chemin vers le fichier temporaire à créer origfilename Le nom de fichier original, pour les sections uuencoded uniquement La première entrée du fichier est le corps du message. Les entrées suivantes sont les fichiers décodés uuencoded. Exemples Exemple #1 Exemple avec mailparse_uudecode_all() <?php $text = <<<EOD To: fred@example.com hello, this is some text hello. blah blah blah. begin 644 test.txt /=&AI<R!I<R!A('1E<W0* ` end EOD; $fp = tmpfile (); fwrite ( $fp , $text ); $data = mailparse_uudecode_all ( $fp ); echo "BODY\n" ; readfile ( $data [ 0 ][ "filename" ]); echo "UUE ( { $data [ 1 ][ 'origfilename' ]} )\n" ; readfile ( $data [ 1 ][ "filename" ]); // Nettoyage unlink ( $data [ 0 ][ "filename" ]); unlink ( $data [ 1 ][ "filename" ]); ?> L'exemple ci-dessus va afficher : BODY To: fred@example.com hello, this is some text hello. blah blah blah. UUE (test.txt) this is a test Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 1 note up down 0 mat at phpconsulting dot com ¶ 22 years ago As an alternative, uudecode() can be called as static function as follows: $file =& Mail_mimeDecode::uudecode($some_text); This will return the following arrays: @param string Input body to look for attachments in @return array Decoded bodies, filenames and permissions ＋ add a note Fonctions Mailparse mailparse_​determine_​best_​xfer_​encoding mailparse_​msg_​create mailparse_​msg_​extract_​part mailparse_​msg_​extract_​part_​file mailparse_​msg_​extract_​whole_​part_​file mailparse_​msg_​free mailparse_​msg_​get_​part mailparse_​msg_​get_​part_​data mailparse_​msg_​get_​structure mailparse_​msg_​parse mailparse_​msg_​parse_​file mailparse_​rfc822_​parse_​addresses mailparse_​stream_​encode mailparse_​uudecode_​all 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:35 |
https://aws.amazon.com/tw/waf/ | Web 應用程式防火牆 – Web API 保護 – AWS WAF – AWS 跳至主要內容 Filter: 全部 English 聯絡我們 AWS Marketplace 支援 我的帳戶 搜尋 Filter: 全部 登入主控台 建立帳戶 AWS Web Application Firewall 概觀 功能 定價 入門 資源 更高的 產品 › 安全、身分及合規 › AWS WAF 使用 AWS 免費方案，取得每月 1,000 萬次機器人控制功能請求 → AWS WAF 保護您的 Web 應用程式免受常見 Web 入侵程式的危害 開始使用 AWS WAF AWS WAF 的優勢 使用受管規則來節省時間 使用受管規則節省時間，讓您有更多時間建置應用程式。 監控、封鎖機器人或限制其速率 更加輕鬆地監控、封鎖常見和普遍的機器人攻擊或限制其速率。 減少安全組態設定步驟 藉助整合式介面，對複雜的安全組態設定進行加速，進而將安全部署組態複雜度及步驟減少高達 80%。 集中且切實可行的可見度 藉助單一的綜合性介面，並與核心安全功能及專用合作夥伴保護功能相結合，來增強安全可見度與控制。利用此統一的方法，將安全資料轉換為切實可行的洞察，從而去除運作摩擦以及加速風險回應。 增強安全狀態 預先設定的保護套件善用 AWS 的安全專業技術，針對特定產業及工作負載類型提供即時的保護範本，例如 API、PHP 應用程式及 Web 服務等。這些範本經持續優化，無需精深的部署專業知識，即可確保最新式的安全性。獲得持續的安全建議，進而增強整體安全狀態。 為何選擇 AWS WAF？ 藉助 AWS WAF，您可以建立安全規則來控制機器人流量，並阻止常見的攻擊模式，如 SQL injection 隱碼攻擊 或跨網站指令碼 (XSS)。 娛樂 使用案例 篩選 Web 流量 建立規則以根據各種條件篩選 Web 請求，例如 IP 地址、HTTP 標頭和內文，或自訂 URI。 進一步了解如何建立規則 防止帳戶接管詐騙 監控應用程式的登入頁面，偵測以盜用憑證對使用者帳戶進行的未經授權存取。 進一步了解欺詐預防措施 自動化第 7 層 DDoS 防護 經過專門設計，只需幾秒鐘時間，即可持續監控及自動緩解應用程式層 (第 7 層) 分散式阻斷服務 (DDoS) 攻擊事件。 迅速實作安全性 藉助精簡的引導式佈設設定，以及單一頁面介面，滿懷自信地啟動全新應用程式，進而根據您的需求，啟用量身定製的預先設定安全預設功能。 增強安全狀態 憑藉經專家策管的規則套件、整合式可見度與持續性推薦，您可獲得即時保護，進而優化您的安全狀態。 開始使用 AWS WAF 開始使用 AWS WAF 探索 AWS WAF 與專家聯絡 聯絡我們 建立 AWS 帳戶 了解 什麼是 AWS？ 什麼是雲端運算？ 什麼是代理式 AI？ 雲端運算概念中心 AWS 雲端安全 最新消息 部落格 新聞稿 資源 入門 培訓 AWS 信任中心 AWS 解決方案程式庫 架構中心 產品和技術常見問答集 分析師報告 AWS 合作夥伴 開發人員 建置者中心 軟體開發套件與工具 .NET on AWS 在 AWS 上執行的 Python 在 AWS 上執行的 Java 在 AWS 上執行的 PHP 在 AWS 上執行的 JavaScript 說明 聯絡我們 提交支援申請單 AWS re:Post 知識中心 AWS Support 概觀 取得專家協助 AWS 可存取性 法律 English 回到頁首 Amazon 是支持平等就業機會的雇主：少數民族/女性/殘障人士/退伍軍人/性別認同/性取向/年齡。 x facebook linkedin instagram twitch youtube podcasts email 隱私權 網站條款 Cookie 偏好設定 © 2026, Amazon Web Services, Inc. 或其關係企業。保留所有權利。 | 2026-01-13T09:30:35 |
https://vi-vn.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 hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-testing-debugging.html#lambda-edge-testing-debugging-determine-region | Uji dan debug fungsi Lambda @Edge - Amazon CloudFront Uji dan debug fungsi Lambda @Edge - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Uji fungsi Lambda @Edge Anda Identifikasi kesalahan fungsi Lambda @Edge di CloudFront Memecahkan masalah respons fungsi Lambda @Edge yang tidak valid (kesalahan validasi) Memecahkan masalah kesalahan eksekusi fungsi Lambda @Edge Tentukan Wilayah Lambda @Edge Tentukan apakah akun Anda mendorong log ke CloudWatch Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Uji dan debug fungsi Lambda @Edge Penting untuk menguji kode fungsi Lambda @Edge Anda secara mandiri, untuk memastikan bahwa itu menyelesaikan tugas yang dimaksudkan, dan untuk melakukan pengujian integrasi, untuk memastikan bahwa fungsi berfungsi dengan benar. CloudFront Selama pengujian integrasi atau setelah fungsi Anda di-deploy, Anda mungkin perlu men-debug CloudFront kesalahan, seperti kesalahan HTTP 5xx. Kesalahan dapat menjadi respons tidak valid yang dikembalikan dari fungsi Lambda, kesalahan eksekusi saat fungsi dipicu, atau kesalahan akibat perotasian eksekusi oleh layanan Lambda. Bagian-bagian dalam topik ini membagikan strategi untuk menentukan jenis kegagalan mana yang menjadi masalahnya, kemudian langkah-langkah yang dapat Anda ambil untuk memperbaiki masalah. catatan Saat Anda meninjau file CloudWatch log atau metrik saat Anda memecahkan masalah kesalahan, ketahuilah bahwa kesalahan tersebut ditampilkan atau disimpan di lokasi Wilayah AWS terdekat dengan lokasi di mana fungsi dijalankan. Jadi, jika Anda memiliki situs web atau aplikasi web dengan pengguna di Britania Raya, dan Anda memiliki fungsi Lambda yang terkait dengan distribusi Anda, misalnya, Anda harus mengubah Wilayah untuk CloudWatch melihat metrik atau file log untuk London. Wilayah AWS Untuk informasi selengkapnya, lihat Tentukan Wilayah Lambda @Edge . Topik Uji fungsi Lambda @Edge Anda Identifikasi kesalahan fungsi Lambda @Edge di CloudFront Memecahkan masalah respons fungsi Lambda @Edge yang tidak valid (kesalahan validasi) Memecahkan masalah kesalahan eksekusi fungsi Lambda @Edge Tentukan Wilayah Lambda @Edge Tentukan apakah akun Anda mendorong log ke CloudWatch Uji fungsi Lambda @Edge Anda Terdapat dua langkah untuk menguji fungsi Lambda Anda: pengujian mandiri dan pengujian integrasi. Uji fungsionalitas mandiri Sebelum Anda menambahkan fungsi Lambda CloudFront, pastikan untuk menguji fungsionalitas terlebih dahulu dengan menggunakan kemampuan pengujian di konsol Lambda atau dengan menggunakan metode lain. Untuk informasi selengkapnya tentang pengujian di konsol Lambda, lihat Memanggil fungsi Lambda menggunakan konsol di Panduan Pengembang .AWS Lambda Uji operasi fungsi Anda di CloudFront Penting untuk menyelesaikan pengujian integrasi, di mana fungsi Anda dikaitkan dengan distribusi dan berjalan berdasarkan CloudFront peristiwa. Pastikan bahwa fungsi dipicu untuk acara yang tepat, dan mengembalikan respons yang valid dan benar untuk CloudFront. Misalnya, pastikan bahwa struktur acara sudah benar, bahwa hanya header yang valid yang disertakan, dan sebagainya. Saat Anda mengulangi pengujian integrasi dengan fungsi Anda di konsol Lambda, lihat langkah-langkah dalam tutorial Lambda @Edge saat Anda memodifikasi kode atau mengubah CloudFront pemicu yang memanggil fungsi Anda. Misalnya, pastikan bahwa Anda bekerja dalam versi bernomor dari fungsi Anda, seperti yang dijelaskan dalam langkah tutorial ini: Langkah 4: Tambahkan CloudFront pemicu untuk menjalankan fungsi . Saat Anda membuat perubahan dan menerapkannya, ketahuilah bahwa fungsi dan CloudFront pemicu Anda yang diperbarui akan memakan waktu beberapa menit untuk mereplikasi di semua Wilayah. Ini biasanya memerlukan waktu beberapa menit, tetapi dapat memakan waktu hingga 15 menit. Anda dapat memeriksa untuk melihat apakah replikasi selesai dengan membuka CloudFront konsol dan melihat distribusi Anda. Untuk memeriksa apakah replikasi Anda telah selesai digunakan Buka CloudFront konsol di https://console.aws.amazon.com/cloudfront/v4/home . Pilih nama distribusi. Periksa status distribusi yang akan diubah dari Sedang Berlangsung kembali ke Diterapkan , yang berarti fungsi Anda telah direplikasi. Kemudian ikuti langkah-langkah di bagian berikutnya untuk memverifikasi bahwa fungsi berfungsi. Ketahuilah bahwa pengujian di konsol hanya memvalidasi logika fungsi Anda, dan tidak menerapkan kuota layanan apa pun (sebelumnya dikenal sebagai batas) yang khusus untuk Lambda @Edge. Identifikasi kesalahan fungsi Lambda @Edge di CloudFront Setelah Anda memverifikasi bahwa logika fungsi Anda berfungsi dengan benar, Anda mungkin masih melihat kesalahan HTTP 5xx saat fungsi Anda berjalan. CloudFront Kesalahan HTTP 5xx dapat dikembalikan karena berbagai alasan, yang dapat mencakup kesalahan fungsi Lambda atau masalah lain di dalamnya. CloudFront Jika Anda menggunakan fungsi Lambda @Edge, Anda dapat menggunakan grafik di CloudFront konsol untuk membantu melacak penyebab kesalahan, dan kemudian bekerja untuk memperbaikinya. Misalnya, Anda dapat melihat apakah kesalahan HTTP 5xx disebabkan oleh CloudFront atau oleh fungsi Lambda, dan kemudian, untuk fungsi tertentu, Anda dapat melihat file log terkait untuk menyelidiki masalah tersebut. Untuk memecahkan masalah kesalahan HTTP secara umum di CloudFront, lihat langkah-langkah pemecahan masalah dalam topik berikut:. Memecahkan masalah kode status respons kesalahan di CloudFront Apa yang menyebabkan kesalahan fungsi Lambda @Edge di CloudFront Ada beberapa alasan mengapa fungsi Lambda dapat menyebabkan kesalahan HTTP 5xx, dan langkah-langkah pemecahan masalah yang harus Anda ambil bergantung pada jenis kesalahan. Kesalahan dapat dikategorikan sebagai berikut: Kesalahan eksekusi fungsi Lambda Kesalahan eksekusi terjadi ketika CloudFront tidak mendapatkan respons dari Lambda karena ada pengecualian yang tidak tertangani dalam fungsi atau ada kesalahan dalam kode. Misalnya, jika kode menyertakan callback(Kesalahan). Respons fungsi Lambda yang tidak valid dikembalikan ke CloudFront Setelah fungsi berjalan, CloudFront menerima respons dari Lambda. Kesalahan dikembalikan jika struktur objek tanggapan tidak sesuai dengan Struktur acara Lambda @Edge , atau respons berisi header yang tidak valid atau kolom tidak valid lainnya. Eksekusi di CloudFront dibatasi karena kuota layanan Lambda (sebelumnya dikenal sebagai batas) Eksekusi throttle layanan Lambda di setiap Wilayah, dan menghasilkan kesalahan jika Anda melebihi kuota. Untuk informasi selengkapnya, lihat Kuotas di Lambda@Edge . Cara menentukan jenis kegagalan Untuk membantu Anda memutuskan di mana harus fokus saat Anda men-debug dan bekerja untuk menyelesaikan kesalahan yang dikembalikan oleh CloudFront, akan sangat membantu untuk mengidentifikasi CloudFront mengapa mengembalikan kesalahan HTTP. Untuk memulai, Anda dapat menggunakan grafik yang disediakan di bagian Pemantauan CloudFront konsol di Konsol Manajemen AWS. Untuk informasi selengkapnya tentang melihat grafik di bagian Pemantauan CloudFront konsol, lihat Pantau CloudFront metrik dengan Amazon CloudWatch . Grafik berikut akan sangat membantu ketika Anda ingin melacak apakah kesalahan dikembalikan oleh asal atau fungsi Lambda, dan untuk mempersempit jenis masalah ketika itu adalah kesalahan dari fungsi Lambda. Grafik harga kesalahan Salah satu grafik yang dapat Anda lihat pada Ikhtisar untuk setiap distribusi Anda adalah Tingkat kesalahan grafik. Grafik ini menampilkan tingkat kesalahan sebagai persentase dari total permintaan yang datang ke distribusi Anda. Grafik menunjukkan tingkat kesalahan total, total 4xx kesalahan, total 5xx kesalahan, dan total 5xx kesalahan dari fungsi Lambda. Berdasarkan jenis dan volume kesalahan, Anda dapat mengambil langkah untuk menyelidiki dan memecahkan masalah penyebab. Jika Anda melihat kesalahan Lambda, Anda dapat menyelidiki lebih lanjut dengan melihat jenis kesalahan tertentu yang dikembalikan oleh fungsi tersebut. Kesalahan Lambda@Edge tab menyertakan grafik yang mengategorikan kesalahan fungsi berdasarkan jenis untuk membantu Anda menemukan masalah dari fungsi tertentu. Jika Anda melihat CloudFront kesalahan, Anda dapat memecahkan masalah dan bekerja untuk memperbaiki kesalahan asal atau mengubah konfigurasi Anda CloudFront . Untuk informasi selengkapnya, lihat Memecahkan masalah kode status respons kesalahan di CloudFront . Grafik kesalahan pelaksanaan dan respons fungsi tidak valid Kesalahan Lambda@Edge tab mencakup grafik yang mengkategorikan kesalahan Lambda@Edge untuk distribusi tertentu, berdasarkan jenis. Misalnya, satu grafik menunjukkan semua kesalahan eksekusi oleh Wilayah AWS. Untuk mempermudah pemecahan masalah, Anda dapat mencari masalah tertentu dengan membuka dan memeriksa file log untuk fungsi tertentu berdasarkan Wilayah. Untuk melihat file log untuk fungsi tertentu menurut Wilayah Pada tab kesalahan Lambda @Edge , di bawah fungsi Lambda @Edge Terkait, pilih nama fungsi, lalu pilih Lihat metrik. Selanjutnya, pada halaman dengan nama fungsi Anda, di sudut kanan atas, pilih Lihat log fungsi , lalu pilih Region. Misalnya, jika Anda melihat masalah dalam grafik Kesalahan untuk Wilayah AS Barat (Oregon), pilih Wilayah itu dari daftar tarik-turun. Ini membuka CloudWatch konsol Amazon. Di CloudWatch konsol untuk Wilayah itu, di bawah Aliran log , pilih aliran log untuk melihat peristiwa untuk fungsi tersebut. Selain itu, baca bagian berikut dalam bab ini untuk rekomendasi lebih lanjut tentang pemecahan masalah dan memperbaiki kesalahan. Grafik trotel Kesalahan Lambda@Edge juga mencakup Trotel grafik. Terkadang, layanan Lambda merombak invokasi fungsi Anda dengan basis per Wilayah, jika Anda mencapai kuota konkurensi regional (sebelumnya disebut batas). Jika Anda melihat kesalahan yang melebihi , fungsi Anda telah mencapai kuota yang dikenakan layanan Lambda pada eksekusi di Wilayah. Untuk informasi lebih lanjut, termasuk cara meminta peningkatan kuota, lihat Kuotas di Lambda@Edge . Sebagai contoh tentang cara menggunakan informasi ini dalam mengatasi masalah kesalahan HTTP, lihat Empat langkah untuk melakukan debug pengiriman konten Anda di AWS . Memecahkan masalah respons fungsi Lambda @Edge yang tidak valid (kesalahan validasi) Jika Anda mengidentifikasi bahwa masalah Anda adalah kesalahan validasi Lambda, itu berarti bahwa fungsi Lambda Anda mengembalikan respons yang tidak valid. CloudFront Ikuti panduan di bagian ini untuk mengambil langkah-langkah untuk meninjau fungsi Anda dan memastikan bahwa respons Anda sesuai dengan CloudFront persyaratan. CloudFront memvalidasi respons dari fungsi Lambda dengan dua cara: Respon Lambda harus sesuai dengan struktur objek yang diperlukan. Contoh struktur objek yang buruk mencakup hal berikut: JSON yang tidak dapat dipisahkan, kolom wajib yang hilang, dan objek tidak valid dalam respons. Untuk informasi lebih lanjut, lihat Struktur acara Lambda @Edge . Respons harus menyertakan hanya nilai objek yang valid. Kesalahan akan terjadi jika respons mencakup objek valid tetapi memiliki nilai yang tidak didukung. Contohnya meliputi yang berikut ini: menambahkan atau memperbarui header yang masuk daftar tidak diizinkan atau hanya baca (lihat Pembatasan pada fungsi edge ), melebihi ukuran izi maksimum (lihat dalam Pembatasan Ukuran Respons yang Dihasilkan dalam topic Kesalahan Lambda@Edge) dan karakter atau nilai tidak valid (lihat Struktur acara Lambda @Edge ). Ketika Lambda mengembalikan respons yang tidak valid CloudFront, pesan kesalahan ditulis ke file log yang CloudFront mendorong ke CloudWatch Wilayah tempat fungsi Lambda dijalankan. Ini adalah perilaku default untuk mengirim file log CloudWatch ketika ada respons yang tidak valid. Namun, jika Anda mengaitkan fungsi Lambda CloudFront sebelum fungsionalitas dirilis, fungsi tersebut mungkin tidak diaktifkan untuk fungsi Anda. Untuk informasi lebih lanjut, lihat Tentukan apakah Akun Anda Mendorong Log ke CloudWatch nanti dalam topik. CloudFront mendorong file log ke Wilayah yang sesuai dengan tempat fungsi Anda dijalankan, di grup log yang terkait dengan distribusi Anda. Grup log memiliki format berikut: /aws/cloudfront/LambdaEdge/ DistributionId , di DistributionId mana ID distribusi Anda. Untuk menentukan Wilayah tempat Anda dapat menemukan file CloudWatch log, lihat Menentukan Wilayah Lambda @Edge nanti dalam topik ini. Jika kesalahan dapat direproduksi, Anda dapat membuat permintaan baru yang menghasilkan kesalahan dan kemudian menemukan id permintaan dalam CloudFront respons gagal ( X-Amz-Cf-Id header) untuk menemukan satu kegagalan dalam file log. Entri file log mencakup informasi yang dapat membantu Anda mengidentifikasi mengapa kesalahan dikembalikan, dan juga mencantumkan id permintaan Lambda yang sesuai sehingga Anda dapat menganalisis akar masalah dalam konteks permintaan tunggal. Jika kesalahan terputus-putus, Anda dapat menggunakan log CloudFront akses untuk menemukan id permintaan untuk permintaan yang gagal, dan kemudian mencari CloudWatch log untuk pesan kesalahan yang sesuai. Untuk informasi lebih lanjut, lihat bagian sebelumnya, Menentukan Jenis Kegagalan . Memecahkan masalah kesalahan eksekusi fungsi Lambda @Edge Jika masalahnya adalah kesalahan eksekusi Lambda, akan sangat membantu untuk membuat pernyataan logging untuk fungsi Lambda, untuk menulis pesan ke file CloudWatch log yang memantau eksekusi fungsi Anda CloudFront dan menentukan apakah berfungsi seperti yang diharapkan. Kemudian Anda dapat mencari pernyataan tersebut di file CloudWatch log untuk memverifikasi bahwa fungsi Anda berfungsi. catatan Bahkan jika Anda belum mengubah fungsi Lambda@Edge Anda, pembaruan pada lingkungan pelaksanaan fungsi Lambda dapat memengaruhinya dan dapat mengembalikan kesalahan pelaksanaan. Untuk informasi tentang pengujian dan migrasi ke versi yang lebih baru, lihat Pembaruan mendatang untuk lingkungan eksekusi AWS Lambda dan AWS Lambda @Edge . Tentukan Wilayah Lambda @Edge Untuk melihat Wilayah tempat fungsi Lambda @Edge Anda menerima lalu lintas, lihat metrik untuk fungsi di CloudFront konsol di. Konsol Manajemen AWS Metrik ditampilkan untuk setiap AWS Wilayah. Di halaman yang sama, Anda dapat memilih Wilayah dan melihat file log untuk Wilayah tersebut sehingga Anda dapat menyelidiki masalah. Anda harus meninjau file CloudWatch log di AWS Wilayah yang benar untuk melihat file log yang dibuat saat CloudFront menjalankan fungsi Lambda Anda. Untuk informasi selengkapnya tentang melihat grafik di bagian Pemantauan CloudFront konsol, lihat Pantau CloudFront metrik dengan Amazon CloudWatch . Tentukan apakah akun Anda mendorong log ke CloudWatch Secara default, CloudFront memungkinkan pencatatan respons fungsi Lambda yang tidak valid, dan mendorong file log ke CloudWatch dengan menggunakan salah satu file. Peran terkait layanan untuk Lambda @Edge Jika Anda memiliki fungsi Lambda @Edge yang Anda tambahkan CloudFront sebelum fitur log respons fungsi Lambda yang tidak valid dirilis, logging diaktifkan saat Anda memperbarui konfigurasi Lambda @Edge Anda, misalnya, dengan menambahkan pemicu. CloudFront Anda dapat memverifikasi bahwa mendorong file log ke CloudWatch diaktifkan untuk akun Anda dengan melakukan hal berikut: Periksa untuk melihat apakah log muncul CloudWatch — Pastikan Anda melihat di Wilayah tempat fungsi Lambda @Edge dijalankan. Untuk informasi selengkapnya, lihat Tentukan Wilayah Lambda @Edge . Tentukan apakah peran terkait layanan terkait ada di akun Anda di IAM — Anda harus memiliki peran AWSServiceRoleForCloudFrontLogger IAM di akun Anda. Untuk informasi selengkapnya tentang peran ini, silakan lihat Peran terkait layanan untuk Lambda @Edge . Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Tambahkan pemicu ke fungsi Lambda @Edge Hapus fungsi dan replika 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:35 |
https://www.php.net/manual/fr/book.bc.php | PHP: BC Math - 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 Introduction » « Extensions sur les mathématiques Manuel PHP Référence des fonctions Extensions sur les mathématiques Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other Fonctions BCMath Introduction Installation/Configuration Installation Configuration à l'exécution Fonctions BC Math bcadd — Additionne deux nombres de grande taille bcceil — Arrondit au supérieur un nombre de précision arbitraire bccomp — Compare deux nombres de grande taille bcdiv — Divise deux nombres de grande taille bcdivmod — Renvoie le quotient et le reste d'un nombre de précision arbitraire bcfloor — Arrondit à l'inférieur un nombre de précision arbitraire bcmod — Retourne le reste d'une division entre nombres de grande taille bcmul — Multiplie deux nombres de grande taille bcpow — Élève un nombre à une puissance donnée bcpowmod — Calcule le reste modulo d'un nombre élevé à une puissance bcround — Arrondit un nombre de précision arbitraire bcscale — Définit ou récupère la précision par défaut pour toutes les fonctions bc math bcsqrt — Récupère la racine carrée d'un nombre de grande taille bcsub — Soustrait un nombre de grande taille d'un autre BcMath\Number — La classe BcMath\Number BcMath\Number::add — Ajouter un nombre de précision arbitraire BcMath\Number::ceil — Arrondit au supérieur un nombre de précision arbitraire BcMath\Number::compare — Compare deux nombres de précision arbitraire BcMath\Number::__construct — Créer un objet BcMath\Number BcMath\Number::div — Divise par un nombre de précision arbitraire BcMath\Number::divmod — Renvoie le quotient et le modulo d'un nombre de précision arbitraire BcMath\Number::floor — Arrondit à l'inférieur un nombre de précision arbitraire BcMath\Number::mod — Renvoie le modulo d'un nombre de précision arbitraire BcMath\Number::mul — Multiplie un nombre de précision arbitraire BcMath\Number::pow — Elève un nombre de précision arbitraire BcMath\Number::powmod — Elève une nombre de précision arbitraire, réduit par un modulo spécifié BcMath\Number::round — Arrondit un nombre de précision arbitraire BcMath\Number::__serialize — Sérialise un objet BcMath\Number BcMath\Number::sqrt — Renvoie la racine carré d'un nombre de précision arbitraire BcMath\Number::sub — Soustrait un nombre de précision arbitraire BcMath\Number::__toString — Convertie un BcMath\Number en chaîne BcMath\Number::__unserialize — Désérialise un paramètre de données en un objet BcMath\Number Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 3 notes up down 75 Hayley Watson ¶ 10 years ago This extension is an interface to the GNU implementation as a library of the Basic Calculator utility by Philip Nelson; hence the name. up down 22 volek at adamv dot cz ¶ 10 years ago Note that when you use implementation of factorial that ClaudiuS made, you get results even if you try to calculate factorial of number that you normally can't, e.g. 2.5, -2, etc. Here is safer implementation: <?php /** * Calculates a factorial of given number. * @param string|int $num * @throws InvalidArgumentException * @return string */ function bcfact ( $num ) { if (! filter_var ( $num , FILTER_VALIDATE_INT ) || $num <= 0 ) { throw new InvalidArgumentException ( sprintf ( 'Argument must be natural number, "%s" given.' , $num )); } for ( $result = '1' ; $num > 0 ; $num --) { $result = bcmul ( $result , $num ); } return $result ; } ?> up down 20 ClaudiuS ¶ 12 years ago Needed to compute some permutations and found the BC extension great but poor on functions, so untill this gets implemented here's the factorial function: <?php /* BC FACTORIAL * n! = n * (n-1) * (n-2) .. 1 [eg. 5! = 5 * 4 * 3 * 2 * 1 = 120] */ function bcfact ( $n ){ $factorial = $n ; while (-- $n > 1 ) $factorial = bcmul ( $factorial , $n ); return $factorial ; } print bcfact ( 50 ); //30414093201713378043612608166064768844377641568960512000000000000 ?> ＋ add a note Extensions sur les mathématiques BC Math GMP Math Statistics Trader 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:35 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html#lambda-examples-content-based-routing-examples | Lambda @Edge contoh fungsi - Amazon CloudFront Lambda @Edge contoh fungsi - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Contoh Umum Hasilkan tanggapan - contoh String kueri - contoh Personalisasi konten berdasarkan header negara atau jenis perangkat - contoh Pemilihan asal dinamis berbasis konten - contoh Perbarui status kesalahan - contoh Akses badan permintaan - contoh Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Lambda @Edge contoh fungsi Lihat contoh berikut untuk menggunakan fungsi Lambda dengan Amazon. CloudFront catatan Jika Anda memilih runtime Node.js 18 atau yang lebih baru untuk fungsi Lambda @Edge Anda, index.mjs file dibuat untuk Anda secara otomatis. Untuk menggunakan contoh kode berikut, ganti nama index.mjs file menjadi index.js sebagai gantinya. Topik Contoh Umum Hasilkan tanggapan - contoh String kueri - contoh Personalisasi konten berdasarkan header negara atau jenis perangkat - contoh Pemilihan asal dinamis berbasis konten - contoh Perbarui status kesalahan - contoh Akses badan permintaan - contoh Contoh Umum Contoh berikut menunjukkan cara umum untuk menggunakan Lambda @Edge di. CloudFront Topik Contoh: A/B pengujian Contoh: Ganti header respons Contoh: A/B pengujian Anda dapat menggunakan contoh berikut untuk menguji dua versi citra yang berbeda tanpa membuat pengalihan atau mengubah URL. Contoh ini membaca cookie di permintaan penampil dan memodifikasi URL permintaan dengan sesuai. Jika penampil tidak mengirim cookie dengan salah satu nilai yang diharapkan, contoh secara acak akan menetapkan penampil ke salah satu. URLs Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request Contoh: Ganti header respons Contoh berikut menunjukkan cara mengubah nilai header respons berdasarkan nilai header lain. Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response Hasilkan tanggapan - contoh Contoh berikut menunjukkan bagaimana Anda dapat menggunakan Lambda @Edge untuk menghasilkan tanggapan. Topik Contoh: Sajikan konten statis (respons yang dihasilkan) Contoh: Menghasilkan pengalihan HTTP (respons yang dihasilkan) Contoh: Sajikan konten statis (respons yang dihasilkan) Contoh berikut menunjukkan cara menggunakan fungsi Lambda untuk melayani konten situs web statis, yang mengurangi beban pada server asal dan mengurangi latensi keseluruhan. catatan Anda dapat membuat tanggapan HTTP untuk permintaan penampil dan peristiwa permintaan asal. Untuk informasi selengkapnya, lihat Hasilkan respons HTTP dalam pemicu permintaan . Anda juga dapat mengganti atau menghapus isi respons HTTP dalam peristiwa respons asal. Untuk informasi selengkapnya, lihat Perbarui tanggapan HTTP di pemicu respons asal . Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response Contoh: Menghasilkan pengalihan HTTP (respons yang dihasilkan) Contoh berikut ini menunjukkan cara membuat pengalihan HTTP. catatan Anda dapat membuat tanggapan HTTP untuk permintaan penampil dan peristiwa permintaan asal. Untuk informasi selengkapnya, lihat Hasilkan respons HTTP dalam pemicu permintaan . Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response String kueri - contoh Contoh berikut menunjukkan cara Anda dapat menggunakan Lambda @Edge dengan string kueri. Topik Contoh: Tambahkan header berdasarkan parameter string kueri Contoh: Normalisasi parameter string kueri untuk meningkatkan rasio hit cache Contoh: Mengarahkan pengguna yang tidak diautentikasi ke halaman login Contoh: Tambahkan header berdasarkan parameter string kueri Contoh berikut menunjukkan cara mendapatkan pasangan nilai kunci dari parameter string pencarian, kemudian menambahkan header berdasarkan nilai tersebut. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request Contoh: Normalisasi parameter string kueri untuk meningkatkan rasio hit cache Contoh berikut menunjukkan cara meningkatkan rasio hit cache Anda dengan membuat perubahan berikut pada string kueri sebelum CloudFront meneruskan permintaan ke asal Anda: Berikan kombinasi nilai kunci dengan nama parameter. Ubah kasus pasangan yang bernilai kunci menjadi huruf kecil. Untuk informasi selengkapnya, lihat Konten cache berdasarkan parameter string kueri . Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request Contoh: Mengarahkan pengguna yang tidak diautentikasi ke halaman login Contoh berikut menunjukkan cara mengalihkan pengguna ke halaman masuk jika mereka belum memasukkan kredensial mereka. Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response Personalisasi konten berdasarkan header negara atau jenis perangkat - contoh Contoh berikut menunjukkan bagaimana Anda dapat menggunakan Lambda @Edge untuk menyesuaikan perilaku berdasarkan lokasi atau jenis perangkat yang digunakan oleh penampil. Topik Contoh: Mengarahkan permintaan penampil ke URL khusus negara Contoh: Sajikan berbagai versi objek berdasarkan perangkat Contoh: Mengarahkan permintaan penampil ke URL khusus negara Contoh berikut menunjukkan cara membuat respons pengalihan HTTP dengan URL khusus negara dan mengembalikan respons ke penampil. Ini berguna saat Anda ingin memberikan tanggapan khusus negara. Sebagai contoh: Jika Anda memiliki subdomain spesifik negara, seperti kami.example.com dan tw.example.com, Anda dapat membuat respons pengalihan saat penampil meminta contoh.com. Jika Anda melakukan streaming video tetapi tidak memiliki hak untuk melakukan streaming konten di negara tertentu, Anda dapat mengarahkan pengguna di negara tersebut ke halaman yang menjelaskan mengapa mereka tidak dapat melihat video tersebut. Perhatikan hal-hal berikut: Anda harus mengonfigurasi distribusi Anda ke cache berdasarkan CloudFront-Viewer-Country header. Untuk informasi selengkapnya, lihat Cache berdasarkan header permintaan yang dipilih . CloudFront menambahkan CloudFront-Viewer-Country header setelah acara permintaan penampil. Untuk menggunakan contoh ini, Anda harus membuat pemicu untuk kejadian permintaan asal. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response Contoh: Sajikan berbagai versi objek berdasarkan perangkat Contoh berikut ini menunjukkan cara menyajikan versi objek berbeda berdasarkan jenis perangkat yang digunakan pengguna, misalnya, perangkat seluler atau tablet. Perhatikan hal-hal berikut: Anda harus mengonfigurasi distribusi Anda ke cache berdasarkan CloudFront-Is-*-Viewer yang berbeda. Untuk informasi selengkapnya, lihat Cache berdasarkan header permintaan yang dipilih . CloudFront menambahkan CloudFront-Is-*-Viewer header setelah acara permintaan penampil. Untuk menggunakan contoh ini, Anda harus membuat pemicu untuk kejadian permintaan asal. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request Pemilihan asal dinamis berbasis konten - contoh Contoh berikut menunjukkan bagaimana Anda dapat menggunakan Lambda @Edge untuk merutekan ke asal yang berbeda berdasarkan informasi dalam permintaan. Topik Contoh: Menggunakan pemicu permintaan asal untuk mengubah dari asal kustom ke asal Amazon S3 Contoh: Gunakan pemicu permintaan asal untuk mengubah Wilayah asal Amazon S3 Contoh: Menggunakan pemicu permintaan asal untuk mengubah dari asal Amazon S3 ke asal kustom Contoh: Gunakan pemicu permintaan asal untuk mentransfer lalu lintas secara bertahap dari satu bucket Amazon S3 ke bucket lainnya Contoh: Gunakan pemicu permintaan asal untuk mengubah nama domain asal berdasarkan header negara Contoh: Menggunakan pemicu permintaan asal untuk mengubah dari asal kustom ke asal Amazon S3 Fungsi ini mendemonstrasikan bagaimana pemicu permintaan asal dapat digunakan untuk mengubah dari asal kustom ke asal Amazon S3 dari mana konten diambil, berdasarkan properti permintaan. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request Contoh: Gunakan pemicu permintaan asal untuk mengubah Wilayah asal Amazon S3 Fungsi ini menunjukkan bagaimana pemicu permintaan asal dapat digunakan untuk mengubah asal Amazon S3 dari mana konten diambil, berdasarkan properti permintaan. Dalam contoh ini, kami menggunakan nilai CloudFront-Viewer-Country header untuk memperbarui nama domain bucket S3 ke bucket di Region yang lebih dekat dengan penampil. Ini dapat berguna dalam beberapa cara: Ini mengurangi keterlambatan saat Wilayah yang ditentukan lebih dekat ke negara penampil. Ini menyediakan kedaulatan data dengan memastikan bahwa data dilayani dari asal yang berada di negara yang sama dengan asal permintaan tersebut. Untuk menggunakan contoh ini, Anda harus melakukan hal berikut: Konfigurasikan distribusi Anda ke cache berdasarkan CloudFront-Viewer-Country header. Untuk informasi selengkapnya, lihat Cache berdasarkan header permintaan yang dipilih . Buat pemicu untuk fungsi ini di acara permintaan asal. CloudFrontmenambahkan CloudFront-Viewer-Country header setelah peristiwa permintaan penampil, jadi untuk menggunakan contoh ini, Anda harus memastikan bahwa fungsi tersebut dijalankan untuk permintaan asal. catatan Kode contoh berikut menggunakan identitas akses asal (OAI) yang sama untuk semua bucket S3 yang Anda gunakan untuk asal Anda. Untuk informasi selengkapnya, lihat Identitas akses asal . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Contoh: Menggunakan pemicu permintaan asal untuk mengubah dari asal Amazon S3 ke asal kustom Fungsi ini menunjukkan bagaimana pemicu permintaan asal dapat digunakan untuk mengubah asal kustom dari mana konten diambil, berdasarkan sifat permintaan. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request Contoh: Gunakan pemicu permintaan asal untuk mentransfer lalu lintas secara bertahap dari satu bucket Amazon S3 ke bucket lainnya Fungsi ini menunjukkan bagaimana Anda dapat secara bertahap mentransfer lalu lintas dari satu bucket Amazon S3 ke bucket lain dengan cara yang terkontrol. Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Contoh: Gunakan pemicu permintaan asal untuk mengubah nama domain asal berdasarkan header negara Fungsi ini menunjukkan bagaimana Anda dapat mengubah nama domain asal berdasarkan CloudFront-Viewer-Country header, sehingga konten disajikan dari asal yang lebih dekat ke negara pemirsa. Mengimplementasikan fungsi ini untuk distribusi Anda dapat memiliki keuntungan seperti berikut ini: Mengurangi keterlambatan jika Wilayah yang ditentukan lebih dekat dengan negara penampil Memberikan kedaulatan data dengan memastikan bahwa data tersebut berasal dari negara yang sama dengan negara asal permintaan Perhatikan bahwa untuk mengaktifkan fungsi ini, Anda harus mengonfigurasi distribusi Anda ke cache berdasarkan CloudFront-Viewer-Country header. Untuk informasi selengkapnya, lihat Cache berdasarkan header permintaan yang dipilih . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Perbarui status kesalahan - contoh Contoh berikut memberikan panduan bagaimana Anda dapat menggunakan Lambda @Edge untuk mengubah status kesalahan yang dikembalikan ke pengguna. Topik Contoh: Gunakan pemicu respons asal untuk memperbarui kode status kesalahan ke 200 Contoh: Gunakan pemicu respons asal untuk memperbarui kode status kesalahan ke 302 Contoh: Gunakan pemicu respons asal untuk memperbarui kode status kesalahan ke 200 Fungsi ini menunjukkan bagaimana Anda dapat memperbarui status respons menjadi 200 dan menghasilkan konten tubuh statis untuk kembali ke penampil dalam skenario berikut: Fungsi dipicu dalam respons asal. Status respons dari server asal adalah kode status kesalahan (4xx atau 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response Contoh: Gunakan pemicu respons asal untuk memperbarui kode status kesalahan ke 302 Fungsi ini menunjukkan cara Anda dapat memperbarui kode status HTTP ke 302 untuk mengalihkan ke jalur lain (perilaku kesalahan) yang memiliki asal berbeda yang dikonfigurasi. Perhatikan hal-hal berikut: Fungsi dipicu dalam respons asal. Status respons dari server asal adalah kode status kesalahan (4xx atau 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response Akses badan permintaan - contoh Contoh berikut menunjukkan bagaimana Anda dapat menggunakan Lambda @Edge untuk bekerja dengan permintaan POST. catatan Untuk menggunakan contoh ini, Anda harus mengaktifkan opsi include body dalam asosiasi fungsi Lambda distribusi. Ini tidak diaktifkan secara default. Untuk mengaktifkan pengaturan ini di CloudFront konsol, pilih kotak centang untuk Sertakan Tubuh di Asosiasi Fungsi Lambda . Untuk mengaktifkan pengaturan ini di CloudFront API atau dengan CloudFormation, atur IncludeBody bidang ke true in LambdaFunctionAssociation . Topik Contoh: Gunakan pemicu permintaan untuk membaca formulir HTML Contoh: Gunakan pemicu permintaan untuk memodifikasi formulir HTML Contoh: Gunakan pemicu permintaan untuk membaca formulir HTML Fungsi ini menunjukkan bagaimana Anda dapat memproses isi permintaan POST yang dibuat oleh formulir HTML (formulir web), seperti formulir “hubungi kami”. Misalnya, Anda mungkin memiliki formulir HTML seperti berikut ini: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> Untuk fungsi contoh berikut, fungsi harus dipicu dalam CloudFront permintaan penampil atau permintaan asal. Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request Contoh: Gunakan pemicu permintaan untuk memodifikasi formulir HTML Fungsi ini menunjukkan bagaimana Anda dapat memodifikasi isi permintaan POST yang dibuat oleh formulir HTML (formulir web). Fungsi ini dipicu dalam permintaan CloudFront penampil atau permintaan asal. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action to 'replace' 2) body.encoding to the encoding of the new data. Set to one of the following values: text - denotes that the generated body is in text format. Lambda@Edge will propagate this as is. base64 - denotes that the generated body is base64 encoded. Lambda@Edge will base64 decode the data before sending it to the origin. 3) body.data to the new body. ''' request['body']['action'] = 'replace' request['body']['encoding'] = 'text' request['body']['data'] = getUpdatedBody(request) return request def getUpdatedBody(request): # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} # For demonstration purposes, we're adding one more param # You can put your custom logic here. For example, you can truncate long # bodies from malicious requests params['new-param-name'] = 'new-param-value' return urlencode(params) Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Bekerja dengan permintaan dan tanggapan Pembatasan pada fungsi 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:35 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT2MTPVrUO9FTvIVxvj2DjxI-VvLubxIfftQjPnWxHmhppCnMOmwxcmKbYKYPURvdiqoshAPao8Z_ygYOZcxdo90WL4ymSwtrYBnuQjZ9-_C7OfX4pkcEwfuumdlhTBugtWFYZvzGBVwswlt | 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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:35 |
https://phproundtable.com/show/functional-programming-non-blocking-asynchronous-event-driven-in-php | PHPRoundtable PHPRoundtable The PHP podcast where everyone has a seat. Guests Library Sponsors About Us 2: Functional Programming, Non-Blocking, Asynchronous & Event-Driven In PHP Panelists: Jeremy Mikola Chris Boden Glen Hinkle Kyle Schatzle September 8 2014 We explore what functional programming looks like in PHP. We also touch on non-blocking, asynchronous, & event-driven concepts. Sammy's B.S. in Linguistics does not help him pronounce Jeremy 's last name properly. How to wrap our heads around functional programming: "Functional programming is to imperative programming as a curve is to a deriv About Us Sponsors © 2026 PHPRoundtable Proud member of the php[architect] family | 2026-01-13T09:30:35 |
https://aws.amazon.com/waf/#aws-page-content-main | Web Application Firewall - Web API Protection - AWS WAF - 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 › Security, Identity and Compliance › AWS WAF Get 10 million common bot control requests per month with the AWS Free Tier → AWS WAF Protect your web applications from common exploits Get started with AWS WAF Benefits of AWS WAF Save time with managed rules Save time with managed rules so you can spend more time building applications. Monitor, block, or rate-limit bots More easily monitor, block, or rate-limit common and pervasive bots. Reduce security configuration steps Accelerate complex security configuration with a consolidated interface that reduces security deployment configuration complexity and steps by up to 80%. Centralized and actionable visibility A single, comprehensive interface combines core security functions with specialized partner protections to enhance security visibility and controls. This unified approach transforms security data into actionable insights, eliminating operational friction and accelerating risk response. Strengthen security posture Preconfigured protection packs leverage AWS's security expertise to deliver instant protection templates for specific industries and workload types like APIs, PHP applications, and web services. These templates are continuously optimized to ensure up-to date security without requiring deep deployment expertise. Gain continuous security recommendations to strengthen overall security posture. Why AWS WAF? With AWS WAF, you can create security rules that control bot traffic and block common attack patterns such as SQL injection or cross-site scripting (XSS). Play Use cases Filter web traffic Create rules to filter web requests based on conditions such as IP addresses, HTTP headers and body, or custom URIs. Learn more about creating rules Prevent account takeover fraud Monitor your application’s login page for unauthorized access to user accounts using compromised credentials. Learn more about fraud prevention Automatic layer 7 DDoS protection Designed to continously monitor and automatically mitigate application layer (layer 7) Distributed Denial of Service (DDoS) events within seconds. Rapid security implementation Launch new applications with confidence using the streamlined guided onboarding setup with a single-page interface to activate preconfigured security defaults tailored to your needs. Strengthen security posture Through expert-curated rule packs, consolidated visibility, and ongoing recommendations, you get immediate protection to optimize your security posture. 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:35 |
https://docs.aws.amazon.com/zh_cn/AmazonCloudFront/latest/DeveloperGuide/kvs-with-functions-kvp.html | 处理键值数据 - Amazon CloudFront 处理键值数据 - Amazon CloudFront 文档 Amazon CloudFront 开发人员指南 使用键值对（控制台） 关于 CloudFront KeyValueStore 使用键值对（AWS CLI） 使用键值对（API） 处理键值数据 本主题介绍如何将键值对添加到现有的键值存储。要在最初创建键值存储时包含键值对，请参阅 创建键值存储 。 主题 使用键值对（控制台） 关于 CloudFront KeyValueStore 使用键值对（AWS CLI） 使用键值对（API） 使用键值对（控制台） 您可以使用 CloudFront 控制台处理键值对。 使用键值对 登录到 AWS 管理控制台 并通过以下网址打开 CloudFront 控制台中的 函数 页面： https://console.aws.amazon.com/cloudfront/v4/home#/functions 。 选择 KeyValueStores 选项卡。 选择要更改的键值存储。 在 键值对 部分，选择 编辑 。 您可以添加键值对、删除键值对或更改现有键值对的值。 完成后，选择 保存更改 。 关于 CloudFront KeyValueStore 提示 CloudFront KeyValueStore API 是一项使用签名版本 4A（SigV4A）进行身份验证的全局服务。在 SigV4A 中使用临时凭证需要版本 2 会话令牌。有关更多信息，请参阅 将临时凭证与 CloudFront KeyValueStore API 结合使用 。 如果您使用 AWS Command Line Interface（AWS CLI）或自己的代码调用 CloudFront KeyValueStore API，请参阅以下各节。 在使用键值存储及其键值对时，您调用的服务取决于您的使用案例： 要在 现有 键值存储中使用键值对，可以使用 CloudFront KeyValueStore 服务。 要在 最初 创建键值存储时在键值存储中包含键值对，可以使用 CloudFront 服务。 CloudFront API 和 CloudFront KeyValueStore API 都有一项 DescribeKeyValueStore 操作。您出于不同的原因来调用它们。要了解差异，请参阅下表。 CloudFront DescribeKeyValueStore API CloudFront KeyValueStore DescribeKeyValueStore API 有关键值存储的数据 返回数据，例如状态以及键值存储本身上次被修改的日期。 返回有关存储资源的 内容 的数据，即存储中的键值对以及内容的大小。 标识键值存储的数据 返回键值存储的 ETag 、UUID 和 ARN。 返回键值存储的 ETag 和 ARN。 备注 每个 DescribeKeyValueStore 操作都会返回一个 不同的 ETag 。 ETags 不可互换。 当您调用 API 操作以完成某项操作时，您必须从相应的 API 指定 ETag 。例如，在 CloudFront KeyValueStore DeleteKey 操作中，您可以指定从 CloudFront KeyValueStore DescribeKeyValueStore 操作返回的 ETag 。 当您使用 CloudFront KeyValueStore 调用 CloudFront Functions 时，在调用函数期间，不会更新或更改键值存储中的值。更新是在函数的两次调用之间进行处理的。 使用键值对（AWS CLI） 您可以为 CloudFront KeyValueStore 运行以下 AWS Command Line Interface 命令。 目录 列出键值对 获取键值对 描述键值存储 创建键值对 删除键值对 更新键值对 列出键值对 要列出键值存储中的键值对，请运行以下命令。 aws cloudfront-keyvaluestore list-keys \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example 响应 { "Items": [ { "Key": "key1", "Value": "value1" } ] } 获取键值对 要获取键值存储中的键值对，请运行以下命令。 aws cloudfront-keyvaluestore get-key \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example 响应 { "Key": "key1", "Value": "value1", "ItemCount": 1, "TotalSizeInBytes": 11 } 描述键值存储 要描述键值存储，请运行以下命令。 aws cloudfront-keyvaluestore describe-key-value-store \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example 响应 { "ETag": "KV1F83G8C2ARO7P", "ItemCount": 1, "TotalSizeInBytes": 11, "KvsARN": "arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example", "Created": "2024-05-08T07:48:45.381000-07:00", "LastModified": "2024-08-05T13:50:58.843000-07:00", "Status": "READY" } 创建键值对 要在键值存储中创建键值对，请运行以下命令。 aws cloudfront-keyvaluestore put-key \ --if-match=KV1PA6795UKMFR9 \ --key=key2 \ --value=value2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example 响应 { "ETag": "KV13V1IB3VIYZZH", "ItemCount": 3, "TotalSizeInBytes": 31 } 删除键值对 要删除键值对，请运行以下命令： aws cloudfront-keyvaluestore delete-key \ --if-match=KV13V1IB3VIYZZH \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example 输出 { "ETag": "KV1VC38T7YXB528", "ItemCount": 2, "TotalSizeInBytes": 22 } 更新键值对 可以使用 update-keys 命令来更新多个键值对。例如，要删除现有键值对并创建另一个键值对，请运行以下命令。 aws cloudfront-keyvaluestore update-keys \ --if-match=KV2EUQ1WTGCTBG2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example \ --deletes '[ { "Key":"key2"}]' \ --puts '[ { "Key":"key3","Value":"value3"}]' 响应 { "ETag": "KV3AEGXETSR30VB", "ItemCount": 3, "TotalSizeInBytes": 28 } 使用键值对（API） 请按照本节内容以编程方式处理键值对。 目录 获取对键值存储的引用 更改键值存储中的键值对 CloudFront KeyValueStore 代码示例 获取对键值存储的引用 使用 CloudFront KeyValueStore API 调用写入操作时，需要指定键值存储的 ARN 和 ETag 。要获取此数据，请执行以下操作： 获取对键值存储的引用 使用 CloudFront ListKeyValueStores API 操作获取键值存储列表。找到要更改的键值存储。 使用 CloudFrontKeyValueStore DescribeKeyValueStore API 操作 并指定上一步中返回的键值存储。 响应包括键值存储的 ARN 和 ETag 。 ARN 包含 AWS 账户编号、常量 key-value-store 和 UUID，类似于以下示例： arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 一个 ETag ，类似于以下示例： ETVABCEXAMPLE2 更改键值存储中的键值对 您可以指定包含要更新的键值对的键值存储。 请参阅以下 CloudFront keyValueStore API 操作： CloudFrontKeyValueStore DeleteKey – 删除键值对 CloudFrontKeyValueStore GetKey – 返回键值对 CloudFrontKeyValueStore ListKeys – 返回键值对列表 CloudFrontKeyValueStore PutKey – 您可以执行以下任务： 通过指定新的键名和键值，在一个键值存储中创建键值对。 通过指定现有键名和新键值，在现有键值对中设置不同的值。 CloudFrontKeyValueStore UpdateKeys –您可以通过一项“要么全有，要么全无”操作执行以下一项或多项操作： 删除一个或多个键值对 创建一个或多个新的键值对 在一个或多个现有键值对中设置不同的值 CloudFront KeyValueStore 代码示例 以下代码演示了如何为键值存储调用 DescribeKeyValueStore API 操作。 const { CloudFrontKeyValueStoreClient, DescribeKeyValueStoreCommand, } = require("@aws-sdk/client-cloudfront-keyvaluestore"); require("@aws-sdk/signature-v4-crt"); (async () => { try { const client = new CloudFrontKeyValueStoreClient( { region: "us-east-1" }); const input = { KvsARN: "arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111", }; const command = new DescribeKeyValueStoreCommand(input); const response = await client.send(command); } catch (e) { console.log(e); } })(); Javascript 在您的浏览器中被禁用或不可用。 要使用 Amazon Web Services 文档，必须启用 Javascript。请参阅浏览器的帮助页面以了解相关说明。 文档惯例 键值对的文件格式 使用 Lambda@Edge 进行自定义 此页面对您有帮助吗？- 是 感谢您对我们工作的肯定！ 如果不耽误您的时间，请告诉我们做得好的地方，让我们做得更好。 此页面对您有帮助吗？- 否 感谢您告诉我们本页内容还需要完善。很抱歉让您失望了。 如果不耽误您的时间，请告诉我们如何改进文档。 | 2026-01-13T09:30:35 |
https://vml.visma.ai/autosuggest | Autosuggest - Automate your workflow About us Who are we? Learn more about Visma Machine Learning What we do Learn more about the products we offer What our customers say Read our customers' testimonials Products Autosuggest Automate your workflow Smartscan Extract data from your documents Resources Blog Product news and showcases Showcase of prototypes Prototypes, ideas and experiments Support Get started Find out more about onboarding to Visma Machine Learning FAQ We have answers to your frequently asked questions. Privacy policy Learn how we handle your data and protect your privacy Cookie policy Learn about how we use cookies to enhance your experience API Documentation Contact Us About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Showcase of prototypes Support Get started FAQ Privacy policy Cookie policy API Documentation Loading... Gærtorvet 1-5 1799 Copenhagen Denmark E-mail: worksmarter@visma.com About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Prototypes Documentation Support Get started FAQ Privacy policy Cookie policy Security Information Operating Status © 2026 Visma Group. All rights reserved Automate your workflow with Autosuggest Autosuggest is the simplest way to automate manual decisions you make in your transaction flows. Simplify everyday life for end-users and accounting offices, saving valuable time and increasing control. Stop guessing, and let the data do the work. Contact us See documentation What is Autosuggest ? AutoSuggest learns the bookkeeping behaviour of our customers through an extremely simple and fully automated learning loop. Designed for learning administrative actions to take on transaction data - invoices, e-invoices or bank transactions, AutoSuggest is designed to be simple, robust and affordable. Autosuggest is currently providing automation for hundreds of thousands of Visma’s customers. What can Autosuggest do for you? AutoSuggest is open ended in the tasks it can perform - but focused on automation for transaction processing. Use cases range from workflow routing and invoice handling to expense management. Typical suggestions include (but not limited to): Expense and service type Bookkeeping accounts GL accounts Cost units Cost centres VAT codes Project numbers Approvers How does it work? Using AutoSuggest simplifies the data science process for teams without dedicated data science skills. All of the mechanics of the Train-Predict-Evaluate loop from typical machine learning workflows are handled through a simple streaming API. Just, stream task examples to AutoSuggest and a model will be automatically trained and continuously optimised. Data science expertise is baked into AutoSuggest with model management, continuous evaluation testing, and baked in precision and recall metrics. How to use Autosuggest? Manage expenses on the fly Set up automation so that your users can take pictures or receipts with their mobile phone, anytime and anywhere. With just a few clicks, your users can quickly register an expense with the help from automatic suggestions. The user takes a photo of the receipt Fields such as supplier name, date, and amount are automatically extracted with Smartscan The expense type is automatically suggested with the help of Autosuggest The registration is completed and sent for approval digitally! Read more about this use case on Dinero's website . Effective bank reconciliation with automatic suggestions Machine Learning can be used to assist in the bank reconciliation process. Use Autosuggest to e.g. fill out accounts for a customer based on bank transfer statements. This can provide a good degree of automation without the effort of defining and maintaining rules! Offer intelligent suggestions for how the bank entries should be posted Automatic suggestions for your bookkeeping, based on past actions Avoid manual typing and give your users more control Read more about this use case on e-conomic's website . Questions? Are you using a Visma product but you are missing Autosuggest or Smartscan capabilities? Talk to your sales contact, if you have one, and ask for Autosuggest or Smartscan. Email us at worksmarter@visma.com to let us know which product you have and we'll get things rolling. Contact us | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/kvs-with-functions-kvp.html | Bekerja dengan data nilai kunci - Amazon CloudFront Bekerja dengan data nilai kunci - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Bekerja dengan pasangan nilai kunci (konsol) Tentang CloudFront KeyValueStore Bekerja dengan pasangan nilai kunci ()AWS CLI Bekerja dengan pasangan nilai kunci (API) Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Bekerja dengan data nilai kunci Topik ini menjelaskan cara menambahkan pasangan nilai kunci ke penyimpanan nilai kunci yang ada. Untuk menyertakan pasangan kunci-nilai saat Anda awalnya membuat penyimpanan nilai kunci, lihat. Buat penyimpanan nilai kunci Topik Bekerja dengan pasangan nilai kunci (konsol) Tentang CloudFront KeyValueStore Bekerja dengan pasangan nilai kunci ()AWS CLI Bekerja dengan pasangan nilai kunci (API) Bekerja dengan pasangan nilai kunci (konsol) Anda dapat menggunakan CloudFront konsol untuk bekerja dengan pasangan nilai kunci Anda. Untuk bekerja dengan pasangan kunci-nilai Masuk ke Konsol Manajemen AWS dan buka halaman Fungsi di CloudFront konsol di https://console.aws.amazon.com/cloudfront/v4/home#/functions . Pilih KeyValueStores tab. Pilih penyimpanan nilai kunci yang ingin Anda ubah. Di bagian Pasangan nilai kunci , pilih Edit . Anda dapat menambahkan pasangan kunci-nilai, menghapus pasangan kunci-nilai, atau mengubah nilai untuk pasangan kunci-nilai yang ada. Setelah Anda selesai, pilih Simpan perubahan . Tentang CloudFront KeyValueStore Tip CloudFront KeyValueStore API adalah layanan global yang menggunakan Signature Version 4A (Sigv4a) untuk otentikasi. Menggunakan kredensi sementara dengan Sigv4a memerlukan token sesi versi 2. Untuk informasi selengkapnya, lihat Menggunakan kredensil sementara dengan API CloudFront KeyValueStore . Jika Anda menggunakan AWS Command Line Interface (AWS CLI) atau kode Anda sendiri untuk memanggil CloudFront KeyValueStore API, lihat bagian berikut. Saat Anda bekerja dengan penyimpan nilai kunci dan pasangan nilai kunci-nya, layanan yang Anda panggil bergantung pada kasus penggunaan Anda: Untuk bekerja dengan pasangan nilai kunci di penyimpanan nilai kunci yang ada , gunakan layanan. CloudFront KeyValueStore Untuk menyertakan pasangan kunci-nilai di penyimpanan nilai kunci saat Anda pertama kali membuat penyimpanan nilai kunci, gunakan layanan. CloudFront Baik CloudFront API dan CloudFront KeyValueStore API memiliki DescribeKeyValueStore operasi. Anda memanggil mereka untuk alasan yang berbeda. Untuk memahami perbedaannya, lihat tabel berikut. CloudFront DescribeKeyValueStore API CloudFront KeyValueStore DescribeKeyValueStore API Data tentang penyimpanan nilai kunci Mengembalikan data, seperti status dan tanggal penyimpanan nilai kunci itu sendiri terakhir diubah. Mengembalikan data tentang isi sumber daya penyimpanan — pasangan kunci-nilai di toko, dan ukuran konten. Data yang mengidentifikasi penyimpanan nilai kunci Mengembalikan ETag , UUID, dan ARN dari penyimpanan nilai kunci. Mengembalikan ETag dan ARN dari penyimpanan nilai kunci. Catatan Masing-masing DescribeKeyValueStore operasi mengembalikan yang berbeda ETag . Itu ETags tidak bisa dipertukarkan. Saat Anda memanggil operasi API untuk menyelesaikan suatu tindakan, Anda harus menentukan ETag dari API yang sesuai. Misalnya, dalam CloudFront KeyValueStore DeleteKey operasi, Anda menentukan ETag yang Anda kembalikan dari CloudFront KeyValueStore DescribeKeyValueStore operasi. Saat Anda memanggil CloudFront Fungsi dengan menggunakan CloudFront KeyValueStore, nilai di penyimpanan nilai kunci tidak diperbarui atau diubah selama pemanggilan fungsi. Pembaruan diproses di antara pemanggilan fungsi. Bekerja dengan pasangan nilai kunci ()AWS CLI Anda dapat menjalankan AWS Command Line Interface perintah berikut untuk CloudFront KeyValueStore. Daftar Isi Daftar pasangan kunci-nilai Dapatkan pasangan kunci-nilai Jelaskan penyimpanan nilai kunci Buat pasangan kunci-nilai Hapus pasangan kunci-nilai Perbarui pasangan nilai kunci Daftar pasangan kunci-nilai Untuk membuat daftar pasangan kunci-nilai di penyimpanan nilai kunci Anda, jalankan perintah berikut. aws cloudfront-keyvaluestore list-keys \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Respons { "Items": [ { "Key": "key1", "Value": "value1" } ] } Dapatkan pasangan kunci-nilai Untuk mendapatkan pasangan kunci-nilai di penyimpanan nilai kunci Anda, jalankan perintah berikut. aws cloudfront-keyvaluestore get-key \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Respons { "Key": "key1", "Value": "value1", "ItemCount": 1, "TotalSizeInBytes": 11 } Jelaskan penyimpanan nilai kunci Untuk menggambarkan penyimpanan nilai kunci, jalankan perintah berikut. aws cloudfront-keyvaluestore describe-key-value-store \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Respons { "ETag": "KV1F83G8C2ARO7P", "ItemCount": 1, "TotalSizeInBytes": 11, "KvsARN": "arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example", "Created": "2024-05-08T07:48:45.381000-07:00", "LastModified": "2024-08-05T13:50:58.843000-07:00", "Status": "READY" } Buat pasangan kunci-nilai Untuk membuat pasangan kunci-nilai di penyimpanan nilai kunci Anda, jalankan perintah berikut. aws cloudfront-keyvaluestore put-key \ --if-match=KV1PA6795UKMFR9 \ --key=key2 \ --value=value2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Respons { "ETag": "KV13V1IB3VIYZZH", "ItemCount": 3, "TotalSizeInBytes": 31 } Hapus pasangan kunci-nilai Untuk menghapus pasangan kunci-nilai, jalankan perintah berikut. aws cloudfront-keyvaluestore delete-key \ --if-match=KV13V1IB3VIYZZH \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Keluaran { "ETag": "KV1VC38T7YXB528", "ItemCount": 2, "TotalSizeInBytes": 22 } Perbarui pasangan nilai kunci Anda dapat menggunakan update-keys perintah untuk memperbarui lebih dari satu pasangan kunci-nilai. Misalnya, untuk menghapus pasangan kunci-nilai yang ada dan membuat yang lain, jalankan perintah berikut. aws cloudfront-keyvaluestore update-keys \ --if-match=KV2EUQ1WTGCTBG2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example \ --deletes '[ { "Key":"key2"}]' \ --puts '[ { "Key":"key3","Value":"value3"}]' Respons { "ETag": "KV3AEGXETSR30VB", "ItemCount": 3, "TotalSizeInBytes": 28 } Bekerja dengan pasangan nilai kunci (API) Ikuti bagian ini untuk bekerja dengan pasangan nilai kunci Anda secara terprogram. Daftar Isi Dapatkan referensi ke penyimpanan nilai kunci Ubah pasangan kunci-nilai di penyimpanan nilai kunci Contoh kode untuk CloudFront KeyValueStore Dapatkan referensi ke penyimpanan nilai kunci Saat Anda menggunakan CloudFront KeyValueStore API untuk memanggil operasi tulis, Anda perlu menentukan ARN dan penyimpanan ETag nilai kunci. Untuk mendapatkan data ini, lakukan hal berikut: Untuk mendapatkan referensi ke penyimpanan nilai kunci Gunakan CloudFront ListKeyValueStores Operasi API untuk mendapatkan daftar penyimpanan nilai kunci. Temukan penyimpanan nilai kunci yang ingin Anda ubah. Gunakan CloudFrontKeyValueStore DescribeKeyValueStore Operasi API dan tentukan penyimpanan nilai kunci dari langkah sebelumnya. Respons termasuk ARN dan penyimpanan ETag nilai kunci. ARN mencakup Akun AWS angka, konstanta key-value-store , dan UUID, seperti contoh berikut: arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 An ETag yang terlihat seperti contoh berikut: ETVABCEXAMPLE2 Ubah pasangan kunci-nilai di penyimpanan nilai kunci Anda dapat menentukan penyimpanan nilai kunci yang berisi pasangan kunci-nilai yang ingin Anda perbarui. Lihat operasi CloudFront KeyValueStore API berikut: CloudFrontKeyValueStore DeleteKey — Menghapus pasangan kunci-nilai CloudFrontKeyValueStore GetKey — Mengembalikan pasangan kunci-nilai CloudFrontKeyValueStore ListKeys — Mengembalikan daftar pasangan kunci-nilai CloudFrontKeyValueStore PutKey — Anda dapat melakukan tugas-tugas berikut: Buat pasangan kunci-nilai dalam satu penyimpanan nilai kunci dengan menentukan nama dan nilai kunci baru. Tetapkan nilai yang berbeda dalam pasangan kunci-nilai yang ada dengan menentukan nama kunci yang ada, dan nilai kunci baru. CloudFrontKeyValueStore UpdateKeys — Anda dapat melakukan satu atau lebih tindakan berikut dalam satu all-or-nothing operasi: Hapus satu atau lebih pasangan nilai kunci Buat satu atau lebih pasangan nilai kunci baru Tetapkan nilai yang berbeda dalam satu atau lebih pasangan kunci-nilai yang ada Contoh kode untuk CloudFront KeyValueStore Kode berikut menunjukkan cara memanggil operasi DescribeKeyValueStore API untuk penyimpanan nilai kunci. const { CloudFrontKeyValueStoreClient, DescribeKeyValueStoreCommand, } = require("@aws-sdk/client-cloudfront-keyvaluestore"); require("@aws-sdk/signature-v4-crt"); (async () => { try { const client = new CloudFrontKeyValueStoreClient( { region: "us-east-1" }); const input = { KvsARN: "arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111", }; const command = new DescribeKeyValueStoreCommand(input); const response = await client.send(command); } catch (e) { console.log(e); } })(); Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Format file untuk pasangan nilai kunci Sesuaikan dengan Fungsi CloudFront Koneksi 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:35 |
https://docs.aws.amazon.com/zh_cn/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 在 CloudFront 边缘站点中截获请求和响应。当发生以下 CloudFront 事件时，您可以执行 Lambda 函数： 在 CloudFront 收到查看器的请求时 (查看器请求) 在 CloudFront 将请求转发到源之前（源请求） 在 CloudFront 收到来自源的响应时（源响应） 在 CloudFront 将响应返回到查看器之前（查看器响应） 如果您使用的是 AWS WAF，则会在应用任何 AWS WAF 规则后执行 Lambda@Edge 查看器请求。 有关更多信息，请参阅 使用请求和响应 和 Lambda@Edge 事件结构 。 Javascript 在您的浏览器中被禁用或不可用。 要使用 Amazon Web Services 文档，必须启用 Javascript。请参阅浏览器的帮助页面以了解相关说明。 文档惯例 使用 Lambda@Edge 进行自定义 使用 Lambda@Edge 的方法 此页面对您有帮助吗？- 是 感谢您对我们工作的肯定！ 如果不耽误您的时间，请告诉我们做得好的地方，让我们做得更好。 此页面对您有帮助吗？- 否 感谢您告诉我们本页内容还需要完善。很抱歉让您失望了。 如果不耽误您的时间，请告诉我们如何改进文档。 | 2026-01-13T09:30:35 |
https://penneo.com/da/law/ | Advokatydelser - 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 digital underskrift og reducer de administrative byrder Penneo hjælper jurister med at reducere den manuelle administration i forbindelse med dokumentunderskrifter, så de kan bruge mere tid på det, der virkelig betyder noget – at rådgive deres klienter. UDFORSK PENNEO Hvordan spænder manuelle processer ben for advokater? Manuelle processer kan holde jurister tilbage på flere kritiske områder. Det kan være en udfordring at tiltrække og fastholde talenter, da unge professionelle forventer, at teknologien understøtter fjernarbejde og fleksibelt samarbejde. Ud over potentielle personalemæssige udfordringer skaber manuelle arbejdsgange ineffektivitet – fx når dokumenter skal printes, underskrives i hånden, scannes og sendes frem og tilbage, hvilket både forsinker sagsbehandlingen og øger risikoen for fejl. Se, hvordan Penneo kan hjælpe dig Øg effektivitet ved at integrere Penneo med andre værktøjer Ved at integrere Penneo med dine eksisterende værktøjer kan du strømline arbejdsgange og øge effektiviteten. Penneo tilbyder integrationer med juridisk software som Advisor, Unik Advosys, EG AdvoPro og Legis 365 . Derudover kan du oprette tilpassede integrationer, der er skræddersyet til dine specifikke behov, ved hjælp af Penneos åbne API. Se alle vores integrationer Automatiser underskriftsprocesser og øg sikkerheden af dine dokumenter Penneo strømliner underskriftsprocessen for jurister ved at: Muliggøre sikre elektroniske signaturer med MitID, MitID Erhverv, pas eller andre eID’er Automatisere arbejdsgange – fremskynde underskrivelsen af aftalebreve, købsaftaler, fortrolighedsaftaler, databehandlingsaftaler og andre juridiske dokumenter Sikre sikkerhed og compliance – opbevar underskrevne dokumenter sikkert og beskyt dem mod uautoriseret adgang Se alle funktioner Optimér processer med Penneo Reducer manuel dataindtastning, forbedr nøjagtigheden, og spar tid med integrationer og automatiserede underskriftsflows. Penneo er GDPR-kompatibel, ISO 27001- og 27701-certificeret og bruger kryptering til at beskytte data og dokumenter. 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 fejl og øg effektiviteten med standardiserede processer for dokumentunderskrift – understøttet af detaljerede aktivitetslogfiler, der sikrer fuld sporbarhed. Giv dine kunder mulighed for at underskrive dokumenter digitalt – nemt, bekvemt og når det passer dem. 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 3000 virksomheder, herunder førende advokatfirmaer Opdag, hvordan Penneo kan hjælpe dig BOOK ET UFORPLIGTENDE 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:35 |
https://support.microsoft.com/nl-nl/microsoft-edge/microsoft-edge-browsegegevens-en-privacy-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd | Microsoft Edge, browsegegevens en privacy - Microsoft Ondersteuning Overslaan naar hoofdinhoud Microsoft Ondersteuning Ondersteuning Ondersteuning Startpagina Microsoft 365 Office Producten Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows meer... Apparaten Surface Pc-accessoires Xbox Pc-gaming HoloLens Surface Hub Hardwaregarantie Account & facturering Account Microsoft Store en facturering Bronnen Wat is er nieuw Communityfora Microsoft 365-beheerders Portal voor kleine bedrijven Ontwikkelaar Onderwijs Oplichtingspraktijk met ondersteuning rapporteren Productveiligheid Meer Microsoft 365 kopen Alles van Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox speciale aanbiedingen Midden- en kleinbedrijf Ondersteuning Software Software Windows-apps AI OneDrive Outlook Overstappen van Skype naar Teams OneNote Microsoft Teams PCs & Apparaten PCs & Apparaten Naar Xbox store Accessoires Entertainment Entertainment Xbox Game Pass Ultimate Xbox & games Pc-games Zakelijk Zakelijk Microsoft Beveiliging Azure Dynamics 365 Microsoft 365 voor bedrijven Microsoft Industry Microsoft Power Platform Windows 365 Ontwikkelaar & IT Ontwikkelaar & IT Microsoft-ontwikkelaar Microsoft Learn Ondersteuning voor AI-marketplace-apps Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Overig Overig Microsoft Rewards Gratis downloads & beveiliging Onderwijs Cadeaubonnen Licentieverlening Bekijk het siteoverzicht Zoeken Zoeken naar hulp Geen resultaten Annuleren Aanmelden Aanmelden met Microsoft Meld u aan of maak een account. Hallo, Selecteer een ander account. U hebt meerdere accounts Kies het account waarmee u zich wilt aanmelden. Microsoft Edge, browsegegevens en privacy Van toepassing op Privacy Microsoft Edge Windows 10 Windows 11 Met Microsoft Edge kunt u bladeren, zoeken, online winkelen en meer. Net als met alle moderne browsers kunt u met Microsoft Edge specifieke gegevens, zoals cookies, verzamelen en opslaan op uw apparaat. Ook kunt u informatie, zoals de browsegeschiedenis, naar ons sturen zodat we uw ervaring zo uitgebreid, snel en persoonlijk mogelijk kunnen maken. Wanneer we gegevens verzamelen, willen we ervoor zorgen dat dit de juiste keuze voor u is. Sommige mensen maken zich zorgen over het feit dat informatie wordt verzameld over hun browsegeschiedenis. Daarom vertellen we u welke gegevens op uw apparaat zijn opgeslagen of door ons worden verzameld. We bieden u keuzes waarmee u kunt bepalen welke gegevens er worden verzameld. Voor meer informatie over privacy in Microsoft Edge kunt u het beste onze Privacyverklaring raadplegen. Welke gegevens worden verzameld en opgeslagen en waarom Microsoft gebruikt diagnostische gegevens om onze producten en services te verbeteren. We gebruiken deze gegevens om beter te begrijpen hoe onze producten presteren en waar verbeteringen moeten worden aangebracht. Microsoft Edge verzamelt een reeks vereiste diagnostische gegevens om Microsoft Edge veilig en up-to-date te houden en te laten presteren zoals verwacht. Microsoft gelooft in het tot een minimum beperken van de verzamelde informatie en handelt daar ook naar. We streven ernaar om alleen de benodigde informatie te verzamelen en deze alleen op te slaan zolang deze nodig is om een service te bieden of voor analyse. Daarnaast kunt u zelf bepalen of optionele diagnostische gegevens die aan uw apparaat zijn gekoppeld worden gedeeld met Microsoft om productproblemen op te lossen en om Microsoft-producten en -services te verbeteren. Wanneer u gebruikmaakt van functies en services in Microsoft Edge, worden diagnostische gegevens over hoe u deze functies gebruikt naar Microsoft verzonden. Met Microsoft Edge wordt uw browsegeschiedenis opgeslagen op uw apparaat. Deze geschiedenis omvat de websites die u bezoekt. Afhankelijk van uw instellingen, wordt deze browsegeschiedenis naar Microsoft verzonden, zodat problemen kunnen worden gedetecteerd en opgelost en onze producten en services kunnen worden verbeterd voor alle gebruikers. U kunt het verzamelen van optionele diagnostische gegevens in de browser beheren door Instellingen en meer > Instellingen > Privacy, zoeken en services > Privacy te selecteren en optionele diagnostische gegevens verzenden in of uit te schakelen om Microsoft-producten te verbeteren . Dit omvat gegevens van het testen van nieuwe ervaringen. Start Microsoft Edge opnieuw om het aanbrengen van wijzigingen in deze instelling te voltooien. Als u deze instelling inschakelt, kunnen deze optionele diagnostische gegevens worden gedeeld met Microsoft vanuit andere toepassingen die Microsoft Edge gebruiken, zoals een videostreaming-app die het Microsoft Edge-webplatform host om de video te streamen. Het Microsoft Edge-webplatform stuurt informatie naar Microsoft over hoe u het webplatform en de sites die u in de applicatie bezoekt, gebruikt. Deze gegevensverzameling wordt bepaald door uw optionele instelling voor diagnostische gegevens in de instellingen voor privacy, zoeken en services in Microsoft Edge. In Windows 10 worden deze instellingen bepaald door uw instelling voor Windows diagnostische gegevens. Als u de instelling voor diagnostische gegevens wilt wijzigen, selecteert u Start > Instellingen > Privacy > Diagnostische gegevens & feedback . Vanaf 6 maart 2024 worden diagnostische gegevens van Microsoft Edge afzonderlijk verzameld van diagnostische gegevens van Windows op apparaten met Windows 10 (versie 22H2 en hoger) en Windows 11 (versie 23H2 en nieuwer) in de Europese Economische Ruimte. Voor deze Windows-versies en op alle andere platforms kunt u uw instellingen wijzigen in Microsoft Edge door Instellingen en meer te selecteren > Instellingen > Privacy, zoeken en services . In sommige gevallen worden uw instellingen voor diagnostische gegevens mogelijk beheerd door uw organisatie. Wanneer u iets zoekt, kan Microsoft Edge suggesties geven over wat u zoekt. Als u deze functie wilt inschakelen, selecteert u Instellingen en meer > Instellingen > Privacy, zoeken en services > Zoeken en verbonden ervaringen > Adresbalk en zoeken > Zoeksuggesties en filters , en schakelt u Zoek - en sitesuggesties weergeven met behulp van mijn getypte tekens in. Terwijl u begint te typen, wordt de informatie die u in de adresbalk typt, naar uw standaard zoekmachine gestuurd, zodat u meteen zoek- en websitesuggesties ontvangt. Wanneer u InPrivate-browse- of gastmodus gebruikt, verzamelt Microsoft Edge enige informatie over hoe u de browser gebruikt, afhankelijk van uw instelling voor diagnostische Gegevens van Windows of Microsoft Edge-privacyinstellingen, maar automatische suggesties worden uitgeschakeld en informatie over websites die u bezoekt, wordt niet verzameld. Met Microsoft Edge worden zowel uw browsegeschiedenis, cookies en sitegegevens als wachtwoorden, adressen en formuliergegevens verwijderd als u alle InPrivate-vensters sluit. U kunt een nieuwe InPrivate-sessie starten door Instellingen en meer te selecteren op een computers of Tabbladen op een mobiel apparaat. Microsoft Edge heeft ook functies die u en uw inhoud online beveiligen. Windows Defender SmartScreen blokkeert automatisch websites en downloads van inhoud die als schadelijk worden gerapporteerd. Windows Defender SmartScreen vergelijkt het adres van de website die u bezoekt met een lijst met adressen van websites opgeslagen op uw apparaat die Microsoft als legitiem beschouwt. Adressen die niet op de lijst van uw apparaat staan en de adressen van bestanden die u downloadt, worden verzonden naar Microsoft en gecontroleerd op een regelmatig bijgewerkte lijst met webpagina's en downloads die zijn gerapporteerd aan Microsoft als onveilig of verdacht. Microsoft Edge kan gegevens opslaan om tijdrovende klusjes als het invullen van formulieren en wachtwoorden makkelijker te maken. Als u ervoor kiest deze functies te gebruiken, slaat Microsoft Edge de informatie op uw apparaat op. Als u synchronisatie hebt ingeschakeld voor het invullen van formulieren zoals adressen of wachtwoorden, worden deze gegevens verzonden naar de Microsoft-cloud en opgeslagen met uw Microsoft-account om te worden gesynchroniseerd met al uw aangemelde versies van Microsoft Edge. U kunt deze gegevens beheren vanuit Instellingen en meer > Instellingen > Profielen > Sync . Om uw browse-ervaring te integreren met andere activiteiten die u op uw apparaat uitvoert, deelt Microsoft Edge uw browsegeschiedenis met Microsoft Windows via de indexeerfunctie. Deze informatie wordt lokaal opgeslagen op het apparaat. Het bevat URL's, een categorie waarin de URL mogelijk relevant is, zoals 'meest bezocht', 'recent bezocht' of 'recent gesloten', en ook een relatieve frequentie of actualiteit binnen elke categorie. Websites die u in de InPrivate-modus bezoekt, worden niet gedeeld. Deze informatie is vervolgens beschikbaar voor andere toepassingen op het apparaat, zoals het startmenu of de taakbalk. U kunt deze functie beheren door Instellingen en meer > Instellingen > Profielen te selecteren en Browsegegevens delen met andere Windows-functies in of uit te schakelen. Als deze optie is uitgeschakeld, worden eerder gedeelde gegevens verwijderd. Sommige streamingwebsites slaan DRM-gegevens (Digital Rights Management), inclusief een unieke id en medialicenties, op uw apparaat op om video- en muziekinhoud te beveiligen tegen kopiëren. Als u naar een van deze websites gaat, worden de DRM-gegevens opgehaald om te controleren of u over de rechten beschikt om de inhoud te gebruiken. Microsoft Edge slaat ook cookies op. Dit zijn kleine bestanden die op uw apparaat worden gezet terwijl u surft op het web. Veel websites gebruiken cookies om informatie op te slaan over uw voorkeuren en instellingen, zoals de items in uw winkelwagen, zodat u deze niet bij elk bezoek aan de website hoeft toe te voegen. Sommige websites gebruiken ook cookies om informatie te verzamelen over uw online activiteiten, zodat advertenties kunnen worden weergegeven op basis van uw interesses. Microsoft Edge biedt u opties om cookies te wissen en toekomstige cookies van bepaalde websites te blokkeren. Microsoft Edge verzendt Niet volgen-verzoeken naar websites wanneer de instelling Niet volgen-verzoeken verzenden is ingeschakeld. Deze instelling is beschikbaar op Instellingen en meer > Instellingen > Privacy, zoeken en services > Privacy > Do Not Track-aanvragen verzenden. Websites kunnen uw activiteiten echter nog steeds volgen, ook als er een Niet volgen-verzoek is verzonden. Gegevens wissen die zijn opgeslagen door Microsoft Edge Ga als volgt te werk als u browsegegevens wilt wissen die op uw apparaat zijn opgeslagen, zoals wachtwoorden of cookies: Selecteer in Microsoft Edge Instellingen en meer > Instellingen > Privacy, zoeken en services > Browsegegevens wissen . Selecteer Kiezen wat u wilt wissen naast Browsegegevens nu wissen. Kies onder Tijdsbereik een tijdsbereik. Schakel het selectievakje in naast elk gegevenstype dat u wilt wissen en selecteer vervolgens Nu wissen . Als u wilt, kunt u Kiezen wat u wilt wissen selecteren telkens wanneer u de browser sluit en kiezen welke gegevenstypen moeten worden gewist. Meer informatie over wat er wordt verwijderd voor elk item in de browsergeschiedenis . Browsegeschiedenis wissen die is verzameld door Microsoft: Als u de browsegeschiedenis die is gekoppeld aan uw account wilt bekijken, meld u zich aan bij uw account op account.microsoft.com . Bovendien hebt u ook de mogelijkheid om uw browsegegevens te wissen die Microsoft heeft verzameld met behulp van het Microsoft-privacydashboard . Als u uw browsegeschiedenis en andere diagnostische gegevens die zijn gekoppeld aan uw Windows 10 apparaat wilt verwijderen, selecteert u Start > Instellingen > Privacy > Diagnostische gegevens & feedback en selecteert u vervolgens Verwijderen onder Diagnostische gegevens verwijderen . Browsegeschiedenis wissen die is gedeeld met andere Microsoft-functies op het lokale apparaat: Selecteer in Microsoft Edge Instellingen en meer > Instellingen > Profielen . Selecteer Browsegegevens delen met andere Windows-functies . Zet deze instelling op uit . Uw privacyinstellingen beheren in Microsoft Edge Als u uw privacyinstellingen wilt controleren en aanpassen, selecteert u Instellingen en meer > Instellingen > Privacy, zoeken en services . > Privacy. Voor meer informatie over privacy in Microsoft Edge, gaat u naar Microsoft Edge-whitepaper . RSS-FEEDS ABONNEREN Meer hulp nodig? Meer opties? Ontdekken Community Neem contact met ons op Verken abonnementsvoordelen, blader door trainingscursussen, leer hoe u uw apparaat kunt beveiligen en meer. Voordelen van Microsoft 365-abonnementen Microsoft 365-training Microsoft-beveiliging Toegankelijkheidscentrum Community's helpen u vragen te stellen en te beantwoorden, feedback te geven en te leren van experts met uitgebreide kennis. Stel een vraag aan de Microsoft-Community Microsoft Tech Community Windows Insiders Microsoft 365 Insiders Zoek oplossingen voor veelvoorkomende problemen of krijg hulp van een ondersteuningsagent. Online-ondersteuning Was deze informatie nuttig? Ja Nee Hartelijk dank. Hebt u verder nog feedback voor Microsoft? Kunt u ons helpen verbeteren? (Stuur feedback naar Microsoft zodat we u kunnen helpen.) Hoe tevreden bent u met de taalkwaliteit? Wat heeft uw ervaring beïnvloed? Mijn probleem is opgelost Duidelijke instructies Gemakkelijk te volgen Geen jargon Afbeeldingen hebben geholpen Vertaalkwaliteit Komt niet overeen met mijn scherm Onjuiste instructies Te technisch Onvoldoende informatie Onvoldoende afbeeldingen Vertaalkwaliteit Hebt u aanvullende feedback? (Optioneel) Feedback verzenden Als u op Verzenden klikt, wordt uw feedback gebruikt om producten en services van Microsoft te verbeteren. Uw IT-beheerder kan deze gegevens verzamelen. Privacyverklaring. Hartelijk dank voor uw feedback. × Nieuw Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot voor organisaties Copilot voor persoonlijk gebruik Microsoft 365 Bekijk Microsoft-producten Windows 11-apps Microsoft Store Accountprofiel Downloadcentrum Ondersteuning Microsoft Store Terugzendingen Bestelling traceren Recyclage Commerciële garanties Onderwijs Microsoft Education Apparaten voor het onderwijs Microsoft Teams for Education Microsoft 365 Education Office Education Educator-training en -ontwikkeling Aanbiedingen voor studenten en ouders Azure voor studenten Zakelijk Microsoft Beveiliging Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Midden- en kleinbedrijf Ontwikkelaar en IT Microsoft-ontwikkelaar Microsoft Learn Ondersteuning voor AI-marketplace-apps Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Bedrijf Vacatures Privacy bij Microsoft Investeerders Duurzaamheid Nederlands (Nederland) Pictogram Uw privacykeuzes afmelden Uw privacykeuzes Pictogram Uw privacykeuzes afmelden Uw privacykeuzes Privacy van consumentenstatus Contact opnemen met Microsoft Privacy Cookies beheren Gebruiksvoorwaarden Handelsmerken Over onze advertenties EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:35 |
https://young-programmers.blogspot.com/2015/ | Young Programmers Podcast: 2015 skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Thursday, February 12, 2015 This Podcast Moves to YouTube Hi all. I have moved to YouTube: https://www.youtube.com/user/dcbriccetti To this playlist, specifically: https://www.youtube.com/playlist?list=PLA87D270FAD3A8C73 See you there. at 7:12 PM Newer Posts Older Posts Home Subscribe to: Comments (Atom) About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ▼  2015 (1) ▼  February (1) This Podcast Moves to YouTube ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ►  2009 (37) ►  December (4) ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Lambda@Edge example functions - Amazon CloudFront Lambda@Edge example functions - Amazon CloudFront Documentation Amazon CloudFront Developer Guide General examples Generate responses - examples Query strings - examples Personalize content by country or device type headers - examples Content-based dynamic origin selection - examples Update error statuses - examples Access the request body - examples Lambda@Edge example functions See the following examples to use Lambda functions with Amazon CloudFront. Note If you choose runtime Node.js 18 or later for your Lambda@Edge function, an index.mjs file is created for you automatically. To use the following code examples, rename the index.mjs file to index.js instead. Topics General examples Generate responses - examples Query strings - examples Personalize content by country or device type headers - examples Content-based dynamic origin selection - examples Update error statuses - examples Access the request body - examples General examples The following examples show common ways to use Lambda@Edge in CloudFront. Topics Example: A/B testing Example: Override a response header Example: A/B testing You can use the following example to test two different versions of an image without creating redirects or changing the URL. This example reads the cookies in the viewer request and modifies the request URL accordingly. If the viewer doesn't send a cookie with one of the expected values, the example randomly assigns the viewer to one of the URLs. Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request Example: Override a response header The following example shows how to change the value of a response header based on the value of another header. Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response Generate responses - examples The following examples show how you can use Lambda@Edge to generate responses. Topics Example: Serve static content (generated response) Example: Generate an HTTP redirect (generated response) Example: Serve static content (generated response) The following example shows how to use a Lambda function to serve static website content, which reduces the load on the origin server and reduces overall latency. Note You can generate HTTP responses for viewer request and origin request events. For more information, see Generate HTTP responses in request triggers . You can also replace or remove the body of the HTTP response in origin response events. For more information, see Update HTTP responses in origin response triggers . Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response Example: Generate an HTTP redirect (generated response) The following example shows how to generate an HTTP redirect. Note You can generate HTTP responses for viewer request and origin request events. For more information, see Generate HTTP responses in request triggers . Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response Query strings - examples The following examples show ways that you can use Lambda@Edge with query strings. Topics Example: Add a header based on a query string parameter Example: Normalize query string parameters to improve the cache hit ratio Example: Redirect unauthenticated users to a sign-in page Example: Add a header based on a query string parameter The following example shows how to get the key-value pair of a query string parameter, and then add a header based on those values. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request Example: Normalize query string parameters to improve the cache hit ratio The following example shows how to improve your cache hit ratio by making the following changes to query strings before CloudFront forwards requests to your origin: Alphabetize key-value pairs by the name of the parameter. Change the case of key-value pairs to lowercase. For more information, see Cache content based on query string parameters . Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request Example: Redirect unauthenticated users to a sign-in page The following example shows how to redirect users to a sign-in page if they haven't entered their credentials. Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response Personalize content by country or device type headers - examples The following examples show how you can use Lambda@Edge to customize behavior based on location or the type of device used by the viewer. Topics Example: Redirect viewer requests to a country-specific URL Example: Serve different versions of an object based on the device Example: Redirect viewer requests to a country-specific URL The following example shows how to generate an HTTP redirect response with a country-specific URL and return the response to the viewer. This is useful when you want to provide country-specific responses. For example: If you have country-specific subdomains, such as us.example.com and tw.example.com, you can generate a redirect response when a viewer requests example.com. If you're streaming video but you don't have rights to stream the content in a specific country, you can redirect users in that country to a page that explains why they can't view the video. Note the following: You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see Cache based on selected request headers . CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response Example: Serve different versions of an object based on the device The following example shows how to serve different versions of an object based on the type of device that the user is using, for example, a mobile device or a tablet. Note the following: You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see Cache based on selected request headers . CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request Content-based dynamic origin selection - examples The following examples show how you can use Lambda@Edge to route to different origins based on information in the request. Topics Example: Use an origin request trigger to change from a custom origin to an Amazon S3 origin Example: Use an origin-request trigger to change the Amazon S3 origin Region Example: Use an origin request trigger to change from an Amazon S3 origin to a custom origin Example: Use an origin request trigger to gradually transfer traffic from one Amazon S3 bucket to another Example: Use an origin request trigger to change the origin domain name based on the country header Example: Use an origin request trigger to change from a custom origin to an Amazon S3 origin This function demonstrates how an origin-request trigger can be used to change from a custom origin to an Amazon S3 origin from which the content is fetched, based on request properties. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request Example: Use an origin-request trigger to change the Amazon S3 origin Region This function demonstrates how an origin-request trigger can be used to change the Amazon S3 origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: It reduces latencies when the Region specified is nearer to the viewer's country. It provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. To use this example, you must do the following: Configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see Cache based on selected request headers . Create a trigger for this function in the origin request event. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event, so to use this example, you must make sure that the function executes for an origin request. Note The following example code uses the same origin access identity (OAI) for all S3 buckets that you're using for your origin. For more information, see Origin access identity . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Example: Use an origin request trigger to change from an Amazon S3 origin to a custom origin This function demonstrates how an origin-request trigger can be used to change the custom origin from which the content is fetched, based on request properties. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request Example: Use an origin request trigger to gradually transfer traffic from one Amazon S3 bucket to another This function demonstrates how you can gradually transfer traffic from one Amazon S3 bucket to another in a controlled way. Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Example: Use an origin request trigger to change the origin domain name based on the country header This function demonstrates how you can change the origin domain name based on the CloudFront-Viewer-Country header, so content is served from an origin closer to the viewer's country. Implementing this functionality for your distribution can have advantages such as the following: Reducing latencies when the Region specified is nearer to the viewer's country Providing data sovereignty by making sure that data is served from an origin that's in the same country that the request came from Note that to enable this functionality you must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see Cache based on selected request headers . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Update error statuses - examples The following examples provide guidance for how you can use Lambda@Edge to change the error status that is returned to users. Topics Example: Use an origin response trigger to update the error status code to 200 Example: Use an origin response trigger to update the error status code to 302 Example: Use an origin response trigger to update the error status code to 200 This function demonstrates how you can update the response status to 200 and generate static body content to return to the viewer in the following scenario: The function is triggered in an origin response. The response status from the origin server is an error status code (4xx or 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response Example: Use an origin response trigger to update the error status code to 302 This function demonstrates how you can update the HTTP status code to 302 to redirect to another path (cache behavior) that has a different origin configured. Note the following: The function is triggered in an origin response. The response status from the origin server is an error status code (4xx or 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response Access the request body - examples The following examples show how you can use Lambda@Edge to work with POST requests. Note To use these examples, you must enable the include body option in the distribution's Lambda function association. It is not enabled by default. To enable this setting in the CloudFront console, select the check box for Include Body in the Lambda Function Association . To enable this setting in the CloudFront API or with CloudFormation, set the IncludeBody field to true in LambdaFunctionAssociation . Topics Example: Use a request trigger to read an HTML form Example: Use a request trigger to modify an HTML form Example: Use a request trigger to read an HTML form This function demonstrates how you can process the body of a POST request generated by an HTML form (web form), such as a "contact us" form. For example, you might have an HTML form like the following: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> For the example function that follows, the function must be triggered in a CloudFront viewer request or origin request. Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request Example: Use a request trigger to modify an HTML form This function demonstrates how you can modify the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action to 'replace' 2) body.encoding to the encoding of the new data. Set to one of the following values: text - denotes that the generated body is in text format. Lambda@Edge will propagate this as is. base64 - denotes that the generated body is base64 encoded. Lambda@Edge will base64 decode the data before sending it to the origin. 3) body.data to the new body. ''' request['body']['action'] = 'replace' request['body']['encoding'] = 'text' request['body']['data'] = getUpdatedBody(request) return request def getUpdatedBody(request): # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} # For demonstration purposes, we're adding one more param # You can put your custom logic here. For example, you can truncate long # bodies from malicious requests params['new-param-name'] = 'new-param-value' return urlencode(params) 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 Work with requests and responses Restrictions on edge functions 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:35 |
https://vml.visma.ai/support | Interested in Autosuggest or Smartscan? About us Who are we? Learn more about Visma Machine Learning What we do Learn more about the products we offer What our customers say Read our customers' testimonials Products Autosuggest Automate your workflow Smartscan Extract data from your documents Resources Blog Product news and showcases Showcase of prototypes Prototypes, ideas and experiments Support Get started Find out more about onboarding to Visma Machine Learning FAQ We have answers to your frequently asked questions. Privacy policy Learn how we handle your data and protect your privacy Cookie policy Learn about how we use cookies to enhance your experience API Documentation Contact Us About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Showcase of prototypes Support Get started FAQ Privacy policy Cookie policy API Documentation Loading... Gærtorvet 1-5 1799 Copenhagen Denmark E-mail: worksmarter@visma.com About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Prototypes Documentation Support Get started FAQ Privacy policy Cookie policy Security Information Operating Status © 2026 Visma Group. All rights reserved Start your journey to intelligent automation now Come join us at the forefront of automation. If you're new to Machine Learning Assets, check out our API documentation for key guidelines on how to make the most of our products. View our FAQ section and onboarding steps below and let us know if you have any questions. Contact us See documentation How to onboard? If you work for Visma, and have access to Visma's Slack, we are available for questions or support regarding Autosuggest or Smartscan, on our support slack channel #smb-vml-support . If you have questions that our documentation does not have answers for, or if you run into what could be a bug in our systems, you can reach out to us at worksmarter@visma.com . Onboarding process differs for external and internal Visma customers: For Visma companies We offer self sign up with your visma e-mail, where you can set up a project from the Development Portal, staging and production : Get a project token from the portal Add team members who need access to the project Implement and call the API in your software For External (non-Visma) companies Self sign up and access to the portal requires a Visma e-mail. To get access to the API contact us on our support email . We can provide you with a token, which you can use to access our API. Frequently asked questions General What does it cost to get started? We provide free API access in staging to all Visma companies. To ensure the best onboarding and a strong partnership, contact us for more information. How are your solutions priced? Smartscan is competitively priced. For Visma companies, it's very competitively priced. contact us for more information. Feel free to test both Smartscan and Autosuggest and get a sense for what to expect. Do you provide any end-user products? Or is it purely developer/API-focused? Our solutions are strictly API-based. Build it into your software, so that you can offer your end-users a fluent experience. We offer guidance on UI and best practices, along with use cases from our other integrations. Get in touch with worksmarter@visma.com and we can help you out with this. On what platform do your APIs work? Can your solutions be implemented on-premise? Our APIs can be integrated into any software that you may be using and can be implemented into any web or mobile application of choice. The main source of communication is standardized JSON, so it is independent of specific programming languages. The APIs are made in a developer-friendly way, so that you can easily integrate our solutions into existing software - into any web or mobile application of choice. The API is well documented , so that your developers will have all the information they need to successfully implement the API. How long does it take to implement Smartscan/Autosuggest? How much workload is to be expected for the integrations? The implementation of our APIs and the direct integration can be done in a single day - integration into your application - data flow as well as user workflow is impossible for us to guess at. This will depend on the use case and your business, but in general it is expected that you can implement the actual integration of our Smartscan product in less than 1 day with our simple APIs. Do you have SDKs in your documentation? Yes, you can find our SDK solutions in our documentation to easily implement them in mobile and web applications. The SDK is being generated for various languages (C#, Go, Java, Python), each language has its own standalone SDK that performs the same function as the others. We support mainly four languages and have provided examples on how to use the SDKs for each of them. All data types are defined in the library so no JSON required Examples of current SDKs can be found in our API definitions Using the SDK means that your IDE of choice will help you create requests by utilising intelliSense which makes it much more convenient. Are the machine learning models customer-specific or global? Smartscan provides standard answers for common document types and is pre-trained to do so. Autosuggest is a platform for learning customer-specific behaviour and as such needs to be integrated with training data from customers to operate. Depending on your use case, the model can be trained per individual customer, but can also perform as one global prediction model across your customer base. Who develops and maintains the machine learning models? Smartscan is developed by the Visma ML Assets team. Autosuggest automatically updates ML models - the platform and built-in QA loop are developed by the Visma ML Assets team. Is the data hosted in the EU? Yes, Visma ML Assets is fully hosted in EU data centres on Google Cloud Platform. You can find more information on our privacy page and Visma's Trust Centre page . How about GDPR & Security? Are you GDPR compliant? All data is saved within the EU and our processes are GDPR compliant. For GDPR concerns: We enforce processing in the EU to support GDPR. Read more about where your data is saved on our privacy page . What kind of customer and technical support does your team offer? API documentation Technical support: We have a Slack community where you can ask your questions and chat with our team. We don't do the integration in your software, but we can offer support and guidance with implementation if needed. QA analysis + progress reports If you require a custom feature or have a specific use case that doesn't quite fit the current offering please get in touch with us at worksmarter@visma.com and we'll see what we can do to help! Smartscan How can I test the Smartscan API? Follow the instructions in the onboarding section above and our API documentation . To test our APIs, you can use our staging environment . You only have to sign in with your visma-email and set up a project on our Staging Portal. Then you'll be able to start using and calling the API - and receive the corresponding json output. We also have a demo page available in our Portal, so you can see it in action. Does Smartscan make use of OCR? Yes, we do! We apply text recognition with the highest recognition rate possible. Google's OCR technology converts any type of image (containing typed, handwritten, or printed text) into a machine-readable format (for example CSV, JSON, or XML). How quickly does the AI learn new data? We pre-train the model every couple of months, so Smartscan is updated approx. 2-6 times per year. How do you ensure high quality output? What quality can I expect? The quality of the scanned documents depends on your documents and cannot be guaranteed. Smartscan outputs up to 90% of the answers requested. Certain fields have the potential to reach an error rate as low as 1%. Confidence levels? Threshold values? Smartscan is tuned to provide an assessment on the likely correctness of all answers we provide. Consult our documentation for details. Are Smartscan's answers verified by humans? No. Man in loop or “human-in-the-loop” refers to systems that allow humans to directly interact with the AI systems to account for any uncertainty and offer 100% automation. Therefore, human-in-the-loop means integrating human employees into the machine learning pipeline, so that they can continuously validate e.g. documents and AI models. This can often result in longer processing times. What are the supported countries? We currently provide support for most European countries, and our software is already being used by end-users across all Europe, but most activity in the Nordics, Romania, Netherlands, and Belgium. Smartscan was trained with documents from over 50 countries, ensuring that you can extract data from your document and get instant results. Current supported countries are listed in our here: see API docs . We're continuously working together with our integrators to expand our document and language support. Please contact us if you would like us to look into new geographical areas. Which document formats are supported? Currently supported image types: PDF containing text PDF containing images (most often from scanners) JPG / JPEG PNG BMP HEIF WEBP GIF TIFF Which document types are supported? The following list gives you an idea of the type of documents we process. It works most seamlessly with receipts, invoices, and bank statements. In case you wonder if we support a certain document that is not on the list, feel free to contact us . Smartscan is currently set up to handle multiple document types, namely: Invoices Receipts Purchase Orders Credit Notes Debit notes What is the max request size can I send to Smartscan? Smartscan accepts only requests up to 10Mb in size, so the max request size is 10485760 Bytes (10Mb). Requests bigger than the max request size will result in a 413 response. Do you support local characters, as in Æ Ø Å Á Ö ? Yes, we generally support Unicode, i.e. local characters to the extent the OCR is able to output them. Does the OCR work on low-quality images? Smartscan processes all text the OCR is able to scan, and is trained to process documents from a large number of different layouts. This can include handwritten receipts on standard pads. Smartscan never rejects images, unless they are digitally damaged or above our size limit (or in an unsupported document format). Google's OCR is astoundingly good even in very bad conditions, bad light skews even handwritten documents, and documents with light and focus issues can work. What is the average API response time? The average processing time is around 1 second, and 95% of the requests are below 2.5 seconds. Our goal is to make sure you can get real-time results in your application. Autosuggest Which document types are supported? Autosuggest can ingest different types of input data, i.e. bank transactions, scanned invoices (i.e. document text), electronic invoice lines. What is the max request size can I send to Autosuggest? Autosuggest accepts only requests up to 10Mb in size, so the max request size is 10485760 Bytes (10Mb). Requests bigger than the max request size will result in a 413 response. How quickly does the AI learn new data? How many samples do you need in order to get results? Will the model be trained automatically with enough samples? Autosuggest models are retrained daily if new data is available. The model will try to train every time you add some data to your dataset, usually a few hours after the addition. With respect to how much data is required, the answer to this question varies a lot with data quality and the complexity of the task we're trying to learn. In optimal cases, Autosuggest starts providing useful answers with as few as 50-100 examples. We recommend having at least 20 samples. If the model does not have enough samples, it will end up with an unsuccessful training. Then you can add more samples and Autosuggest will try to train the model, ending up either in failure if it's not enough, or successfully when it's enough samples. What is a confidence score? All predictions from Autosuggest are accompanied by a quality score, namely the confidence score . Generally speaking, when the confidence is higher, the answer is more likely to be correct. To present your users with reliable predictions, you should filter out (i.e. simply ignore) answers below an acceptable confidence. Read more in our documentation . You might find the following explainer useful: Understanding ML Quality | 2026-01-13T09:30:35 |
https://young-programmers.blogspot.com/2009/12/invisible-player-escapes-maze.html | Young Programmers Podcast: Invisible Player Escapes Maze skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Friday, December 25, 2009 Invisible Player Escapes Maze Escape the maze. You are invisible, and so are all the obstacles unless they are close to you. Illustrates use of the ghost effect, and broadcast. http://scratch.mit.edu/projects/davebric/818925 at 1:37 PM Labels: scratch Newer Post Older Post Home About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ►  2015 (1) ►  February (1) ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ▼  2009 (37) ▼  December (4) Invisible Player Escapes Maze, Pygame Version 1 Invisible Player Escapes Maze Growing Player Escapes Maze Jython/Swing Game of Life Version 2 ►  November (1) ►  September (7) ►  August (11) ►  July (14)   | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/ko_kr/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Lambda@Edge 예제 함수 - Amazon CloudFront Lambda@Edge 예제 함수 - Amazon CloudFront 설명서 Amazon CloudFront 개발자 가이드 일반 예제 응답 생성 - 예시 쿼리 문자열 - 예시 국가 또는 디바이스 유형 헤더별 콘텐츠 개인화 - 예제 콘텐츠 기반 동적 원본 선택 - 예제 오류 상태 업데이트 - 예시 요청 본문 액세스 - 예시 Lambda@Edge 예제 함수 Amazon CloudFront에서 Lambda 함수를 사용하려면 다음 예시를 참조하세요. 참고 Lambda@Edge 함수에 대해 런타임 Node.js 18 이상을 선택하면 index.mjs 파일이 자동으로 생성됩니다. 다음 코드 예제를 사용하려면 index.mjs 파일의 이름을 index.js 로 바꿉니다. 주제 일반 예제 응답 생성 - 예시 쿼리 문자열 - 예시 국가 또는 디바이스 유형 헤더별 콘텐츠 개인화 - 예제 콘텐츠 기반 동적 원본 선택 - 예제 오류 상태 업데이트 - 예시 요청 본문 액세스 - 예시 일반 예제 다음 예시에서는 CloudFront에서 Lambda@Edge 를 사용하는 일반적인 방법을 보여줍니다. 주제 예: A/B 테스트 예시: 응답 헤더 재정의 예: A/B 테스트 다음 예제를 사용하여 리디렉션을 만들거나 URL을 변경하지 않고 두 가지 다른 버전의 이미지를 테스트할 수 있습니다. 이 예제는 최종 사용자 요청의 쿠키를 읽고 그에 따라 요청 URL을 수정합니다. 최종 사용자가 예상 값 중 하나와 함께 쿠키를 보내지 않는 경우, 이 예제에서는 최종 사용자를 URL 중 하나에 임의로 할당합니다. Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request 예시: 응답 헤더 재정의 다음 예제는 다른 헤더의 값을 기준으로 응답 헤더의 값을 변경하는 방법을 보여줍니다. Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response 응답 생성 - 예시 다음 예시에서는 Lambda@Edge를 사용하여 응답을 생성하는 방법을 보여줍니다. 주제 예시: 정적 콘텐츠 제공(생성된 응답) 예: HTTP 리디렉션 생성(생성된 응답) 예시: 정적 콘텐츠 제공(생성된 응답) 다음 예제는 Lambda 함수를 사용하여 정적 웹사이트 콘텐츠를 서비스하는 방법을 보여줍니다. 이는 오리진 서버에 대한 로드를 줄이고 전체 지연 시간을 단축합니다. 참고 최종 사용자 요청 및 오리진 요청 이벤트에 대해 HTTP 응답을 만들 수 있습니다. 자세한 내용은 요청 트리거에서 HTTP 응답 생성 섹션을 참조하세요. 원본 응답 이벤트에서 HTTP 응답의 본문을 바꾸거나 제거할 수도 있습니다. 자세한 내용은 오리진 응답 트리거에서 HTTP 응답 업데이트 섹션을 참조하세요. Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response 예: HTTP 리디렉션 생성(생성된 응답) 다음 예제는 HTTP 리디렉션을 만드는 방법을 보여줍니다. 참고 최종 사용자 요청 및 오리진 요청 이벤트에 대해 HTTP 응답을 만들 수 있습니다. 자세한 내용은 요청 트리거에서 HTTP 응답 생성 섹션을 참조하세요. Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response 쿼리 문자열 - 예시 다음 예시에서는 Lambda@Edge를 쿼리 문자열과 함께 사용할 수 있는 방법이 포함되어 있습니다. 주제 예시: 쿼리 문자열 파라미터를 기반으로 헤더 추가 예시: 쿼리 문자열 파라미터를 정규화하여 캐시 적중률 향상 예시: 인증되지 않은 사용자를 로그인 페이지로 리디렉션 예시: 쿼리 문자열 파라미터를 기반으로 헤더 추가 다음 예제에서는 쿼리 문자열 파라미터의 키-값 페어를 가져오고 그 값을 토대로 헤더를 추가하는 방법을 보여줍니다. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request 예시: 쿼리 문자열 파라미터를 정규화하여 캐시 적중률 향상 다음 예제에서는 CloudFront가 요청을 오리진에 전달하기 전에 쿼리 문자열을 다음과 같이 변경하여 캐시 적중률을 향상하는 방법을 보여 줍니다. 파라미터 이름을 기준으로 키-값 페어를 알파벳순으로 정렬 키-값 페어의 대/소문자를 소문자로 변경 자세한 내용은 쿼리 문자열 파라미터 기반의 콘텐츠 캐싱 섹션을 참조하세요. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request 예시: 인증되지 않은 사용자를 로그인 페이지로 리디렉션 다음 예제에서는 사용자가 자격 증명을 입력하지 않은 경우 사용자를 로그인 페이지로 리디렉션하는 방법을 보여 줍니다. Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response 국가 또는 디바이스 유형 헤더별 콘텐츠 개인화 - 예제 다음 예시에서는 Lambda@Edge를 사용하여 뷰어가 사용하는 위치나 장치 유형에 따라 동작을 사용자 정의하는 방법을 보여줍니다. 주제 예시: 최종 사용자 요청을 국가별 URL로 리디렉션 예시: 디바이스를 기반으로 객체의 다양한 버전 제공 예시: 최종 사용자 요청을 국가별 URL로 리디렉션 다음 예제에서는 국가별 URL이 포함된 HTTP 리디렉션 응답을 생성하고 해당 응답을 최종 사용자에게 반환하는 방법을 보여 줍니다. 이 작업은 국가별 응답을 제공하려는 경우에 유용합니다. 예: 국가별 하위 도메인이 있는 경우(예: us.example.com 및 tw.example.com) 최종 사용자가 example.com을 요청할 때 리디렉션 응답을 생성할 수 있습니다. 비디오를 스트리밍하지만 특정 국가에서 콘텐츠를 스트리밍할 권한이 없는 경우 비디오를 볼 수 없는 이유를 설명하는 페이지로 해당 국가의 사용자를 리디렉션할 수 있습니다. 다음을 참조하십시오. CloudFront-Viewer-Country 헤더 값을 기반으로 캐시하도록 배포를 구성해야 합니다. 자세한 내용은 선택한 요청 헤더 기반의 캐시 단원을 참조하세요. CloudFront는 최종 사용자 요청 이벤트 뒤에 CloudFront-Viewer-Country 헤더를 추가합니다. 이 예제를 사용하려면 오리진 요청 이벤트에 대한 트리거를 생성해야 합니다. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response 예시: 디바이스를 기반으로 객체의 다양한 버전 제공 다음 예제에서는 사용자가 사용 중인 디바이스 유형(예: 모바일 디바이스 또는 태블릿)을 기반으로 객체의 다양한 버전을 서비스하는 방법을 보여 줍니다. 다음을 참조하십시오. CloudFront-Is-*-Viewer 헤더 값을 기반으로 캐시하도록 배포를 구성해야 합니다. 자세한 내용은 선택한 요청 헤더 기반의 캐시 단원을 참조하세요. CloudFront는 최종 사용자 요청 이벤트 뒤에 CloudFront-Is-*-Viewer 헤더를 추가합니다. 이 예제를 사용하려면 오리진 요청 이벤트에 대한 트리거를 생성해야 합니다. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request 콘텐츠 기반 동적 원본 선택 - 예제 다음 예시에서는 Lambda@Edge를 사용하여 요청 정보를 기반으로 다른 오리진으로 라우팅하는 방법을 보여줍니다. 주제 예시: 오리진 요청 트리거를 사용하여 사용자 지정 오리진에서 Amazon S3 오리진으로 변경 예시: 오리진 요청 트리거를 사용하여 Amazon S3 오리진 리전 변경 예시: 오리진 요청 트리거를 사용하여 Amazon S3 오리진에서 사용자 지정 오리진으로 변경 예시: 오리진 요청 트리거를 사용하여 하나의 Amazon S3 버킷에서 다른 버킷으로 점진적으로 트래픽 전송 예시: 오리진 요청 트리거를 사용하여 국가 헤더를 기반으로 오리진 도메인 이름 변경 예시: 오리진 요청 트리거를 사용하여 사용자 지정 오리진에서 Amazon S3 오리진으로 변경 이 함수는 오리진 요청 트리거를 사용하여 사용자 지정 오리진에서 콘텐츠를 요청 속성을 기반으로 가져오는 Amazon S3 오리진으로 변경하는 방법을 보여줍니다. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request 예시: 오리진 요청 트리거를 사용하여 Amazon S3 오리진 리전 변경 이 함수는 오리진 요청 트리거를 사용하여 콘텐츠를 요청 속성을 기반으로 가져오는 Amazon S3 오리진을 변경하는 방법을 보여줍니다. 이 예제에서는 CloudFront-Viewer-Country 헤더 값을 사용하여 뷰어에게 더 가까운 리전의 버킷으로 S3 버킷 도메인 이름을 업데이트합니다. 이는 여러 방법에서 유용할 수 있습니다. 지정된 리전이 최종 사용자의 국가와 더욱 근접할 때 지연 시간을 감소합니다. 데이터가 요청이 온 곳과 동일한 국가에 있는 리전에서 서비스되는지 확인함으로써 데이터 주권을 제공합니다. 이 예제를 활용하려면 다음과 같이 해야 합니다. CloudFront-Viewer-Country 헤더를 기반으로 캐시하도록 배포를 구성합니다. 자세한 내용은 선택한 요청 헤더 기반의 캐시 섹션을 참조하세요. 오리진 요청 이벤트에서 이 함수에 대한 트리거를 생성합니다. CloudFront는 뷰어 요청 이벤트 뒤에 CloudFront-Viewer-Country 헤더를 추가하므로 이 예제를 사용하려면 함수가 원본 요청에 대해 실행되는지 확인해야 합니다. 참고 다음 예제 코드는 오리진에 사용 중인 모든 S3 버킷에 대해 동일한 오리진 액세스 ID(OAI)를 사용합니다. 자세한 내용은 오리진 액세스 ID 섹션을 참조하세요. Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 예시: 오리진 요청 트리거를 사용하여 Amazon S3 오리진에서 사용자 지정 오리진으로 변경 이 함수는 오리진 요청 트리거를 사용하여 콘텐츠를 요청 속성을 기반으로 가져오는 사용자 지정 오리진을 변경하는 방법을 보여줍니다. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request 예시: 오리진 요청 트리거를 사용하여 하나의 Amazon S3 버킷에서 다른 버킷으로 점진적으로 트래픽 전송 이 함수는 통제된 방법을 통해 하나의 Amazon S3 버킷에서 다른 버킷으로 점진적으로 트래픽을 전송하는 방법을 보여 줍니다. Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 예시: 오리진 요청 트리거를 사용하여 국가 헤더를 기반으로 오리진 도메인 이름 변경 이 함수는 CloudFront-Viewer-Country 헤더를 기반으로 원본 도메인 이름을 변경하여 뷰어의 국가에 더 가까운 원본에서 콘텐츠를 제공하는 방법을 보여줍니다. 배포에서 이 기능을 구현하면 다음과 같은 이점을 누릴 수 있습니다. 지정된 리전이 최종 사용자의 국가와 더욱 근접할 때 지연 시간이 감소 데이터가 요청이 온 곳과 동일한 국가에 있는 오리진에서 서비스되는지 확인함으로써 데이터 주권을 제공 이 함수를 사용하려면 CloudFront-Viewer-Country 헤더를 기반으로 캐시하도록 배포를 구성해야 합니다. 자세한 내용은 선택한 요청 헤더 기반의 캐시 섹션을 참조하세요. Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 오류 상태 업데이트 - 예시 다음 예시에서는 Lambda@Edge를 사용하여 사용자에게 반환되는 오류의 상태를 변경하는 방법에 대한 지침을 제공합니다. 주제 예시: 오리진 응답 트리거를 사용하여 오류 상태 코드를 200으로 업데이트 예시: 오리진 응답 트리거를 사용하여 오류 상태 코드를 302로 업데이트 예시: 오리진 응답 트리거를 사용하여 오류 상태 코드를 200으로 업데이트 이 함수는 응답 상태를 200으로 업데이트하고 정적 본문 콘텐츠를 생성하여 다음 시나리오에서 최종 사용자에게 반환하는 방법을 보여줍니다. 함수가 오리진 응답에서 트리거됩니다. 오리진 서버의 응답 상태는 오류 상태 코드(4xx 또는 5xx)입니다. Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response 예시: 오리진 응답 트리거를 사용하여 오류 상태 코드를 302로 업데이트 이 함수는 HTTP 상태 코드를 302로 업데이트하여 다른 오리진이 구성된 다른 경로(캐시 동작)로 리디렉션하는 방법을 보여줍니다. 다음을 참조하십시오. 함수가 오리진 응답에서 트리거됩니다. 오리진 서버의 응답 상태는 오류 상태 코드(4xx 또는 5xx)입니다. Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response 요청 본문 액세스 - 예시 다음 예시에서는 Lambda@Edge를 사용하여 POST 요청을 처리하는 방법을 보여줍니다. 참고 이러한 예제를 사용하려면 배포의 Lambda 함수 연결에서 본문 포함 옵션을 활성화해야 합니다. 기본적으로 활성화되어 있지 않습니다. CloudFront 콘솔에서 이 설정을 활성화하려면 Lambda 함수 연결(Lambda Function Association) 에서 본문 포함(Include Body) 확인란을 선택하세요. CloudFront API 또는 CloudFormation에서 이 설정을 활성화하려면 LambdaFunctionAssociation 에서 IncludeBody 필드를 true 로 설정합니다. 주제 예시: 요청 트리거를 사용하여 HTML 양식 읽기 예시: 요청 트리거를 사용하여 HTML 양식 수정 예시: 요청 트리거를 사용하여 HTML 양식 읽기 이 기능은 "문의처" 양식 등과 같은 HTML 양식(웹 양식)으로 인해 생성된 POST 요청의 본문을 처리할 수 있는 방법을 보여줍니다. 예를 들어, 다음과 같은 HTML 양식이 있을 수 있습니다. <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> 예를 들어, 다음 함수는 CloudFront 최종 사용자 요청 또는 오리진 요청 시 실행되어야 합니다. Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request 예시: 요청 트리거를 사용하여 HTML 양식 수정 이 기능은 "문의처" 양식 등과 같은 HTML 양식(웹 양식)으로 인해 생성된 POST 요청의 본문을 수정할 수 있는 방법을 보여줍니다. 이 함수는 CloudFront 최종 사용자 요청 또는 오리진 요청 시 실행됩니다. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action to 'replace' 2) body.encoding to the encoding of the new data. Set to one of the following values: text - denotes that the generated body is in text format. Lambda@Edge will propagate this as is. base64 - denotes that the generated body is base64 encoded. Lambda@Edge will base64 decode the data before sending it to the origin. 3) body.data to the new body. ''' request['body']['action'] = 'replace' request['body']['encoding'] = 'text' request['body']['data'] = getUpdatedBody(request) return request def getUpdatedBody(request): # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} # For demonstration purposes, we're adding one more param # You can put your custom logic here. For example, you can truncate long # bodies from malicious requests params['new-param-name'] = 'new-param-value' return urlencode(params) javascript가 브라우저에서 비활성화되거나 사용이 불가합니다. AWS 설명서를 사용하려면 Javascript가 활성화되어야 합니다. 지침을 보려면 브라우저의 도움말 페이지를 참조하십시오. 문서 규칙 요청 및 응답 작업 수행 엣지 함수에 대한 제한 사항 이 페이지의 내용이 도움이 되었습니까? | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/ja_jp/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Lambda@Edge 関数の例 - Amazon CloudFront Lambda@Edge 関数の例 - Amazon CloudFront ドキュメント Amazon CloudFront デベロッパーガイド 一般的な例 レスポンスを生成する - 例 クエリ文字列 - 例 国またはデバイスタイプヘッダー別のコンテンツのパーソナライズ - 例 コンテンツベースの動的オリジンの選択 - 例 エラーステータスを更新する - 例 リクエストボディにアクセスする - 例 Lambda@Edge 関数の例 Amazon CloudFront で Lambda 関数を使用するには、以下の例を参照してください。 注記 Lambda@Edge 関数にランタイム Node.js 18 以降を選択すると、 index.mjs ファイルが自動的に作成されます。次のコード例を使用するには、 index.mjs ファイルの名前を index.js に変更します。 トピック 一般的な例 レスポンスを生成する - 例 クエリ文字列 - 例 国またはデバイスタイプヘッダー別のコンテンツのパーソナライズ - 例 コンテンツベースの動的オリジンの選択 - 例 エラーステータスを更新する - 例 リクエストボディにアクセスする - 例 一般的な例 以下の例は、CloudFront で Lambda@Edge を使用する一般的な方法を示しています。 トピック 例: A/B テスト 例: レスポンスヘッダーをオーバーライドする 例: A/B テスト 次の例を使用すると、リダイレクトを作成したり URL を変更したりすることなく、2 つの異なるバージョンのイメージをテストできます。この例では、ビューワーリクエスト内の Cookie を読み取り、それに応じてリクエスト URL を変更します。ビューワーがいずれかの期待値を使用して Cookie を送信しない場合、例ではビューワーを URL のいずれかにランダムに割り当てます。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request 例: レスポンスヘッダーをオーバーライドする 以下の例は、レスポンスヘッダーの値を別のヘッダーの値に基づいて変更する方法を示しています。 Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response レスポンスを生成する - 例 以下の例は、Lambda@Edge を使用してレスポンスを生成する方法を示しています。 トピック 例: 静的コンテンツを提供する (生成されたレスポンス) 例: HTTP リダイレクトを生成する (生成されたレスポンス) 例: 静的コンテンツを提供する (生成されたレスポンス) 次の例は、Lambda 関数を使用して静的ウェブサイトコンテンツを提供する方法を示しています。これにより、オリジンサーバーの負荷と全体的なレイテンシーが軽減されます。 注記 HTTP レスポンスは、ビューワーリクエストおよびオリジンリクエストのイベントに対して生成できます。詳細については、「 リクエストトリガーでの HTTP レスポンスを生成する 」を参照してください。 オリジンレスポンスイベントで HTTP レスポンスのボディを置き換えたり、削除することもできます。詳細については、「 オリジンレスポンストリガーでの HTTP レスポンスを更新する 」を参照してください。 Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response 例: HTTP リダイレクトを生成する (生成されたレスポンス) 次の例は、HTTP リダイレクトを生成する方法を示しています。 注記 HTTP レスポンスは、ビューワーリクエストおよびオリジンリクエストのイベントに対して生成できます。詳細については、「 リクエストトリガーでの HTTP レスポンスを生成する 」を参照してください。 Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response クエリ文字列 - 例 以下の例は、クエリ文字列で Lambda@Edge を使用する方法を示しています。 トピック 例: クエリ文字列パラメータに基づくヘッダーを追加する 例: キャッシュヒット率を向上させるためにクエリ文字列パラメータを正規化する 例: 認証されていないユーザーをサインインページにリダイレクトする 例: クエリ文字列パラメータに基づくヘッダーを追加する 以下の例では、クエリ文字列パラメータのキーと値のペアを取得してから、それらの値に基づいてヘッダーを追加する方法を示します。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request 例: キャッシュヒット率を向上させるためにクエリ文字列パラメータを正規化する 次の例では、CloudFront がリクエストをオリジンに転送する前にクエリ文字列に以下の変更を行うことで、キャッシュヒット率を向上させる方法を示します。 パラメータの名前によりキーと値のペアをアルファベット順に並べ替える キーと値のペアを小文字に変更する 詳細については、「 クエリ文字列パラメータに基づいてコンテンツをキャッシュする 」を参照してください。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request 例: 認証されていないユーザーをサインインページにリダイレクトする 次の例では、ユーザーが認証情報を入力していない場合にサインインページにリダイレクトする方法を示します。 Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response 国またはデバイスタイプヘッダー別のコンテンツのパーソナライズ - 例 以下の例は、Lambda@Edge により、ビューワーが使用しているデバイスの場所やタイプに基づいて動作をカスタマイズする方法を示しています。 トピック 例: ビューワーリクエストを国に固有の URL にリダイレクトする 例: デバイスに基づいて異なるバージョンのオブジェクトを供給する 例: ビューワーリクエストを国に固有の URL にリダイレクトする 次の例では、HTTP リダイレクト応答を国に固有の URL で生成し、ビューワーにレスポンスを返す方法を示します。これは、国ごとに異なる応答を提供する場合に便利です。次に例を示します。 国別のサブドメイン (us.example.com および tw.example.com など) がある場合は、ビューワーが example.com をリクエストしたときにリダイレクト応答を生成できます。 動画をストリーミングしていて、そのコンテンツを特定の国でストリーミングする権限がない場合は、その国のユーザーを別のページにリダイレクトして動画を閲覧できない理由について説明できます。 次の点に注意してください。 CloudFront-Viewer-Country ヘッダーに基づいてキャッシュするようにディストリビューションを設定する必要があります。詳細については、「 選択されたリクエストヘッダーに基づいたキャッシュ 」を参照してください。 CloudFront は、ビューワーリクエストイベントの後に CloudFront-Viewer-Country ヘッダーを追加します。この例を使用するには、オリジンリクエストイベントのトリガーを作成する必要があります。 Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response 例: デバイスに基づいて異なるバージョンのオブジェクトを供給する 次の例では、ユーザーが使用しているモバイルデバイスまたはタブレットのようなデバイスのタイプに基づいてオブジェクトの異なるバージョンを提供する方法を示します。次の点に注意してください。 CloudFront-Is-*-Viewer ヘッダーに基づいてキャッシュするようにディストリビューションを設定する必要があります。詳細については、「 選択されたリクエストヘッダーに基づいたキャッシュ 」を参照してください。 CloudFront は、ビューワーリクエストイベントの後に CloudFront-Is-*-Viewer ヘッダーを追加します。この例を使用するには、オリジンリクエストイベントのトリガーを作成する必要があります。 Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request コンテンツベースの動的オリジンの選択 - 例 以下の例は、Lambda@Edge を使用し、リクエスト内の情報に基づいて複数の異なるオリジンにルーティングする方法を示しています。 トピック 例: オリジンリクエストトリガーを使用してカスタムオリジンを Amazon S3 オリジンに変更する 例: オリジンリクエストトリガーを使用して Amazon S3 オリジンのリージョンを変更する 例: オリジンリクエストトリガーを使用して Amazon S3 オリジンからカスタムオリジンに変更する 例: オリジンリクエストトリガーを使用して Amazon S3 バケットから別のバケットにトラフィックを徐々に転送する 例: オリジンリクエストトリガーを使用して Country ヘッダーに基づいてオリジンのドメイン名を変更する 例: オリジンリクエストトリガーを使用してカスタムオリジンを Amazon S3 オリジンに変更する この関数では、origin-request トリガーを使用して、リクエストのプロパティに基づいて、カスタムオリジンから、コンテンツがフェッチされる Amazon S3 オリジンに変更する方法を示しています。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request 例: オリジンリクエストトリガーを使用して Amazon S3 オリジンのリージョンを変更する この関数では、origin-request トリガーを使用して、リクエストのプロパティに基づいて、コンテンツがフェッチされる Amazon S3 オリジンを変更する方法を示しています。 この例では、 CloudFront-Viewer-Country ヘッダーの値を使用して、S3 バケットのドメイン名を、ビューワーに近いリージョンのバケットに更新します。これは、以下のように役立ちます。 指定したリージョンがビューワーの国に近いほど、レイテンシーが短縮されます。 リクエスト元と同じ国にあるオリジンからデータが提供されることになり、データ主権が確保されます。 この例を使用するには、以下を実行する必要があります。 CloudFront-Viewer-Country ヘッダーに基づいてキャッシュするようにディストリビューションを設定します。詳細については、「 選択されたリクエストヘッダーに基づいたキャッシュ 」を参照してください。 オリジンリクエストイベントでこの関数のトリガーを作成します。CloudFront はビューワーリクエストイベントの後に CloudFront-Viewer-Country ヘッダーを追加するため、この例を使用するには、オリジンリクエストに対して関数が実行されることを確認する必要があります。 注記 次のコード例では、オリジンに使用しているすべての S3 バケットに同じオリジンアクセスアイデンティティ (OAI) を使用します。詳細については、「 オリジンアクセスアイデンティティ 」を参照してください。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 例: オリジンリクエストトリガーを使用して Amazon S3 オリジンからカスタムオリジンに変更する この関数では、origin-request トリガーを使用して、リクエストのプロパティに基づいて、コンテンツがフェッチされるカスタムオリジンを変更する方法を示しています。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request 例: オリジンリクエストトリガーを使用して Amazon S3 バケットから別のバケットにトラフィックを徐々に転送する この関数では、Amazon S3 バケットから別のバケットにトラフィックを制御しながら徐々に転送する方法を示しています。 Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 例: オリジンリクエストトリガーを使用して Country ヘッダーに基づいてオリジンのドメイン名を変更する この関数では、 CloudFront-Viewer-Country ヘッダーに基づいてオリジンのドメイン名を変更する方法を示しています。これにより、コンテンツはビューワーの国に近いオリジンから配信されます。 ディストリビューションに対してこの機能を実装すると、次のような利点があります。 指定したリージョンがビューワーの国に近いほど、レイテンシーが短縮されます。 リクエスト元と同じ国にあるオリジンからデータが提供されることになり、データ主権が確保されます。 この機能を有効にするには、 CloudFront-Viewer-Country ヘッダーに基づいてキャッシュするようにディストリビューションを設定する必要があります。詳細については、「 選択されたリクエストヘッダーに基づいたキャッシュ 」を参照してください。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request エラーステータスを更新する - 例 以下の例は、Lambda@Edge を使用して、ユーザーに返すエラーステータスを変更する方法を示しています。 トピック 例: オリジンレスポンストリガーを使用してエラーステータスコードを 200 に更新する 例: オリジンレスポンストリガーを使用してエラーステータスコードを 302 に更新する 例: オリジンレスポンストリガーを使用してエラーステータスコードを 200 に更新する この関数では、レスポンスステータスを 200 に更新し、以下のシナリオでビューワーに返す静的な本文コンテンツを生成する方法を示しています。 関数がオリジンレスポンスでトリガーされる。 オリジンサーバーからのレスポンスステータスがエラーステータスコード (4xx または 5xx) である。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response 例: オリジンレスポンストリガーを使用してエラーステータスコードを 302 に更新する この関数では、HTTP ステータスコードを 302 に更新して、異なるオリジンを設定した別のパス (キャッシュ動作) にリダイレクトする方法を示しています。次の点に注意してください。 関数がオリジンレスポンスでトリガーされる。 オリジンサーバーからのレスポンスステータスがエラーステータスコード (4xx または 5xx) である。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response リクエストボディにアクセスする - 例 以下の例は、Lambda@Edge を使用して POST リクエストを操作する方法を示しています。 注記 これらの例を使用するには、ディストリビューションの Lambda 関数の関連付けで [Include body] (ボディを含める) オプションを有効にする必要があります。デフォルトでは、有効になっていません。 CloudFront コンソールでこの設定を有効にするには、[ Lambda 関数の関連付け ] の [ ボディを含める ] チェックボックスをオンにします。 CloudFront API または CloudFormation でこの設定を有効にするには、 LambdaFunctionAssociation の IncludeBody フィールドを true に設定します。 トピック 例: リクエストトリガーを使用して HTML フォームを読み込む 例: リクエストトリガーを使用して HTML フォームを変更する 例: リクエストトリガーを使用して HTML フォームを読み込む この関数では、「お問い合わせ」フォームなど HTML フォーム (ウェブフォーム) によって生成された POST リクエストボディを処理する方法を示しています。たとえば、次のような HTML フォームがあります。 <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> 次の関数の例では、関数は CloudFront ビューワーリクエストまたはオリジンリクエストでトリガーされる必要があります。 Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request 例: リクエストトリガーを使用して HTML フォームを変更する この関数では、HTML フォーム (ウェブフォーム) によって生成された POST リクエストボディを変更する方法を示しています。この関数は、CloudFront ビューワーリクエストまたはオリジンリクエストでトリガーされます。 Node.js 'use strict'; const querystring = require('querystring'); exports.han | 2026-01-13T09:30:35 |
https://www.iso.org/es/tienda | ISO - Tienda 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 Tienda ¿Ya está registrado como cliente ? Inicie una sesión en su cuenta . Busque en nuestro catálogo Explore by sector Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y riesgo Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Top standards ISO 9001 Sistemas de gestión de calidad — Requisitos Publicado en 2015 CHF 179 ISO 37001 Sistemas de gestión antisoborno — Requisitos con orientación para su uso Publicado en 2025 CHF 196 ISO/IEC 42001 Information technology — Artificial intelligence — Management system Publicado en 2023 CHF 225 ISO 14001 Sistemas de gestión ambiental — Requisitos con orientación para su uso Publicado en 2015 CHF 179 ISO/IEC 27001 Information security, cybersecurity and privacy protection — Information security management systems — Requirements Publicado en 2022 CHF 155 ISO 45001 Sistemas de gestión de la seguridad y salud en el trabajo — Requisitos con orientación para su uso Publicado en 2018 CHF 196 Starter packages Get started with essential standards for your business Publications Information security – the basics Strengthen your organization's information security with our ISO standards bundle, designed for cybersecurity and privacy protection. This bundle includes 2 products: ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection — Information security management systems … ISO/IEC 27001:2022 - … Publications AI and information security management package Enhance your organization's AI management and information security with our ISO 42001 and ISO 27001 standards package. This package includes two essential components: ISO/IEC 42001:2023 - Artificial intelligence — Management system ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection … Publications The complete ISO/IEC 27000 Information security bundle Empower your organization with robust information security management. This bundle includes four essential standards for a holistic approach to information security management: ISO/IEC 27000:2018 Information technology — Security techniques — Information security management systems — Overview and vocabulary … Publications AI data quality management bundle Ensure high-quality data for analytics and machine learning with our comprehensive ISO/IEC 5259 standards bundle. This bundle includes five essential components: ISO/IEC 5259-1:2024 - Artificial intelligence — Data quality for analytics and machine learning (ML) — Part 1: Overview, terminology, and examples … Publications Responsible AI governance and impact standards package Empower your organization with the essential standards for responsible artificial intelligence. This exclusive bundle brings together: ISO/IEC 42001: Artificial Intelligence Management Systems ISO/IEC 42005: AI System Impact Assessment Publications Industrial robot safety bundle Ensuring safe and efficient robotic operations with ISO 10218. This bundle includes two essential standards for a holistic approach to industrial robot safety: ISO 10218-1:2025 - Robotics — Safety requirements - Part 1: Industrial robots ISO 10218-2:2025 Robotics — Safety requirements - Part 2: Industrial … Publications Business continuity management systems – the basics Strengthen your organization's resilience with our ISO 22301 standards bundle, including ISO 22313 for comprehensive guidance on business continuity management. This bundle includes two essential standards: ISO 22301:2019 - Security and resilience — Business continuity management systems — Requirements … Publications Anti-bribery & Compliance bundle Strengthen integrity and compliance across your organization This bundle includes two essential components: ISO 37001:2025 - Anti-bribery management systems — Requirements with guidance for use ISO 37301:2021 - Compliance management systems — Requirements with guidance for use Publications Risk management – the basics Equip your organization with comprehensive risk management tools using our ISO 31000 standards bundle, including IEC 31010 and the ISO 31000 practical guide. This bundle includes three essential components: ISO 31000:2018 - Risk management — Guidelines IEC 31010:2019 - Risk management — Risk assessment … Publications Complete medical device compliance essentials package Your focused path to MDR/IVDR biological evaluation and risk management This streamlined bundle offers the newest ISO 10993-1:2025 biological evaluation standard, paired with ISO 14971:2019 and ISO/TR 24971:2020 for effective risk management implementation, covering the core regulatory essentials for … Publications ISO 26262 road vehicles functional safety Ensure comprehensive functional safety for road vehicles with our ISO 26262 standards bundle, covering all critical aspects from vocabulary to guidelines. This bundle includes 10 essential parts: ISO 26262-1:2018 - Road vehicles — Functional safety — Part 1: Vocabulary ISO 26262-2:2018 - Road vehicles … Publications Complete energy management & audit standards package Unlock your organization’s energy efficiency potential with our all-in-one standards bundle: ISO 50001:2018 – Energy Management Systems ISO 50002-1:2025 – General Requirements for Energy Audits ISO 50002-2:2025 – Energy Audits for Buildings ISO 50002-3:2025 – Energy Audits for Processes ISO 50004:2020 … Publications ISO 9001:2015 SME success package Unlock the full potential of ISO 9001:2015 with our SME success package. What's inside? - ISO 9001:2015 Quality management systems — Requirements: The full text of the ISO 9001:2015 standard, outlining the requirements for a quality management system. - ISO 9001:2015 for Small Enterprises - What to do: … Publications Medical devices - the basics Ensure quality management and risk mitigation for medical devices with our ISO standards bundle, tailored for compliance and practical implementation. This bundle includes 4 products: ISO 13485:2016 Requirements for regulatory purposes ISO 13485:2016 - Medical devices: A practical guide ISO 14971:2019 Application … Publications ISO 45001:2018 Occupational Health and Safety (OHSAS) success package Achieve Occupational Health and Safety (OHSAS) excellence with ISO 45001:2018 What's Included in the OHSAS Success Package? ISO 45001:2018 Occupational health and safety management systems — Requirements with guidance: The core requirements for establishing, implementing, maintaining, and improving an … Top publications Publications ISO 37001:2025 Anti-bribery management systems — A practical guide Empower your organization to fight bribery effectively. Bribery undermines trust, distorts markets, and damages reputations. ISO 37001 provides a globally recognized framework to prevent, detect, and respond to bribery. This official ISO handbook helps you implement the standard with confidence. Publications ISO 31000:2018 - Risk management — A practical guide This handbook, published jointly by ISO and UNIDO, provides valuable insights into the implementation of ISO 31000 Risk management – Guidelines. Publications ISO 13485:2016 - Medical devices - A practical guide Handbook intended to guide organizations in the development, implementation and maintenance of their quality management system in accordance with ISO 13485. Shopping at ISO Shopping FAQs My account Terms and conditions Privacy and copyright Licence agreement Buy from your national ISO member You can purchase ISO Standards and other ISO publications from the ISO member in your country. The ISO members page lists contact information for all ISO members, including links to their online stores where available. Consultar otras listas ICS (Clasificación internacional para las normas) Catálogo de los TC (comités técnicos) Manuales y folletos Tienda 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:35 |
https://vi-vn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT3lN7wpIGgWaTyXErk4SF1WCKEs9PDHJPdbiN3Yl_7Rba5JxYLIit5nb079Cw1WWMDlqJeHCsuW7di_wtBhIrbQwVsBpN2U3fkPKWMYiOrU-c_JuLCa8u7nUnpt80Nm-EprkKK9rPoa2_sw | Facebook Facebook Email hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T09:30:35 |
https://young-programmers.blogspot.com/2009/08/superhappydevhouse-34-interviews-part_23.html | Young Programmers Podcast: SuperHappyDevHouse 34 Interviews, Part Two skip to main | skip to sidebar Young Programmers Podcast A video podcast for computer programmers in grades 3 and up. We learn about Scratch, Tynker, Alice, Python, Pygame, and Scala, and interview interesting programmers. From professional software developer and teacher Dave Briccetti, and many special guests. Viewing the Videos or Subscribing to the Podcast Some of the entries have a picture, which you can click to access the video. Otherwise, to see the videos, use this icon to subscribe to or view the feed: Or, subscribe in iTunes Sunday, August 23, 2009 SuperHappyDevHouse 34 Interviews, Part Two Interviews with programmers and hardware hackers from SuperHappyDevHouse 34, part 2 of 2. Kevin Gadd talks about his dad bringing home computers for him to play with, and learning to program them, and his career making videogames. Drew Perttula ’s dad brought home computers but no games, so Drew had to write his own. He got interested in visual effects and computer graphics. He works at DreamWorks Animation. Mike Lundy works for Nasa in Mountain View. He started programming around age 10 on a PCjr running BASIC. He works in the Intelligent Robotics Group at NASA. He hopes the software he works on will eventually run on the Moon or Mars. at 3:14 PM Labels: hacker , interview , programmer , shdh , shdh34 Newer Post Older Post Home About Me Dave Briccetti View my complete profile Where to Get Software Kojo Python Alice Scratch Other Blogs Dave Briccetti’s Blog One of My Best Classes Ever 10 years ago Tags alice (3) Android (1) arduino (1) art (1) audacity (2) dictionary (2) Flickr (1) functions (2) gamedev (1) garageband (1) GIMP (2) Google (2) guest (4) hacker (1) higher-order functions (1) inkscape (1) interview (9) Java (2) JavaFX (2) Jython (3) Kojo (2) lift (1) music (2) physics (1) platform (1) programmer (4) pygame (6) python (31) PythonCard (1) random (6) Sande (2) Scala (5) scratch (10) shdh (2) shdh34 (2) sound (3) sprite (2) Swing (3) teaching (3) twitter (2) Tynker (1) Web Services (1) xturtle (1) Followers Blog Archive ►  2015 (1) ►  February (1) ►  2013 (4) ►  July (1) ►  June (3) ►  2012 (2) ►  February (1) ►  January (1) ►  2011 (8) ►  November (1) ►  July (3) ►  May (1) ►  February (2) ►  January (1) ►  2010 (6) ►  October (2) ►  June (2) ►  February (2) ▼  2009 (37) ►  December (4) ►  November (1) ►  September (7) ▼  August (11) SuperHappyDevHouse 34 Interviews, Part Two SuperHappyDevHouse 34 Interviews, Part One Jumping Man in Pygame Interviews with Professional Programmers, Part One Functions in Python Dave Briccetti Introduces the Podcast Using a Python Dictionary to Give Custom Greetings Mr. T Guess The Food Walkthrough Platform Example, Very Simple Cat Saves the Villager Scratch Project Walkthrough Bob Lee Videoconference With Dave Briccetti’s Coll... ►  July (14)   | 2026-01-13T09:30:35 |
https://vml.visma.ai/ | Visma Machine Learning - Automate your processes About us Who are we? Learn more about Visma Machine Learning What we do Learn more about the products we offer What our customers say Read our customers' testimonials Products Autosuggest Automate your workflow Smartscan Extract data from your documents Resources Blog Product news and showcases Showcase of prototypes Prototypes, ideas and experiments Support Get started Find out more about onboarding to Visma Machine Learning FAQ We have answers to your frequently asked questions. Privacy policy Learn how we handle your data and protect your privacy Cookie policy Learn about how we use cookies to enhance your experience API Documentation Contact Us About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Showcase of prototypes Support Get started FAQ Privacy policy Cookie policy API Documentation Loading... Gærtorvet 1-5 1799 Copenhagen Denmark E-mail: worksmarter@visma.com About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Prototypes Documentation Support Get started FAQ Privacy policy Cookie policy Security Information Operating Status © 2026 Visma Group. All rights reserved Transforming the way people work Visma Machine Learning dramatically reduces the time spent on routine tasks, and lets our customers focus on the important things. Our products save people many hours of data entry into accounting systems which directly translates into cost savings for companies and helps them to become paperless. Contact us Try out Smartscan Let our numbers speak for us 0 + thousand companies use our ML 0 + million documents scanned per month 0 + million API requests per day 30+ SaaS products powered by our machine learning APIs We simplify and automate accounting workflows Data entry is one of the big time sinks in business processes. With Smartscan we're eliminating most of this work for document handling. With AutoSuggest we're dramatically simplifying the decisions you need to make in the accounting workflow. Leading machine learning solutions Industry leading OCR and Data Capture API for scanning and extracting information from invoices and receipts. Learn more The process toolkit for your workflows and tasks. Simple-to-use prediction engine for scanned invoices and bank transactions. Learn more Minimise the time spent processing documents and doing manual work Easy setup We make machine learning as simple as possible - available through simple JSON APIs. Best in class AI We use state of the art techniques to offer the best coverage on the market. Blazingly fast Our speed is a point of pride. Document scans complete in 1-2 seconds. Faster than most document AI APIs. See what our customers have to say Great Service For any new Dinero customers the machine learning predictions will work right away, and it will be magical. Our customers love it! Alexander Jasper Lead AI Engineer, Dinero Intuitive Implementation The implementation was a breeze thanks to your documentation. Marco Hokke Software Developer, Visma Raet Efficient Performance If we want to increase our customers automation level, that is where ML Assets become extremely important. Oliver Storm-Pallesen Product Line Manager, e-conomic Questions? Are you using a Visma product but you are missing Autosuggest or Smartscan capabilities? Talk to your sales contact, if you have one, and ask for Autosuggest or Smartscan. Email us at worksmarter@visma.com to let us know which product you have and we'll get things rolling. Contact us | 2026-01-13T09:30:35 |
https://penneo.com/da/pricing/penneo-sign/ | Priser - Penneo Sign 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Å Penneo Sign Priser Denmark Denmark Sign Essential Fra 834 DKK pr. måned, faktureres årligt 500 underskrifter inkluderet Ekstra underskrifter: 14 DKK pr. underskrift, mængderabat gælder.Underskrifter er defineret som hver enkelt underskriftslinje i hvert dokument. Underskriftslinjer henviser til hver udpeget plads til underskrifter i dokumentet. Underskrift med nationale eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv, BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. SMS-verifikation SSO Dokumentarkiv BOOK ET MØDE Har du brug for hurtig hjælp? Vi ringer dig op inden for 20 minutter. Sign Plus Fra 1,250 DKK pr. måned, faktureres årligt 500 underskrifter inkluderet Ekstra underskrifter: 14 DKK pr. underskrift, mængderabat gælder.Underskrifter er defineret som hver enkelt underskriftslinje i hvert dokument. Underskriftslinjer henviser til hver udpeget plads til underskrifter i dokumentet. Underskrift med nationale eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv, BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. SMS-verifikation SSO Dokumentarkiv Branchespecifikke underskriftsflows Visse arbejdsopgaver (f.eks. årsrapporter) kræver underskrifter i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet af de rigtige personer i den rigtige rækkefølge. Penneo Sign indeholder et udvalg af typiske underskriftsflows. Integrationer (med undtagelse af Caseware, som kræver et særskilt gebyr) BOOK ET MØDE Har du brug for hurtig hjælp? Vi ringer dig op inden for 20 minutter. Sign Pro Fra 3,917 DKK pr. måned, faktureres årligt 500 underskrifter inkluderet Ekstra underskrifter: 14 DKK pr. underskrift, mængderabat gælder.Underskrifter er defineret som hver enkelt underskriftslinje i hvert dokument. Underskriftslinjer henviser til hver udpeget plads til underskrifter i dokumentet. Underskrift med nationale eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv, BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. SMS-verifikation SSO Dokumentarkiv Branchespecifikke underskriftsflows Visse arbejdsopgaver (f.eks. årsrapporter) kræver underskrifter i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet af de rigtige personer i den rigtige rækkefølge. Penneo Sign indeholder et udvalg af typiske underskriftsflows. Integrationer (med undtagelse af Caseware, som kræver et særskilt gebyr) Dedikeret supportline Står i med et akut problem? Kontakt vores supportlinje og tal direkte med en af vores produktspecialister. Personlig onboardingplan Vi skræddersyr jeres onboardingoplevelse, så den passer perfekt til jeres teams specifikke behov. Dedikeret sparringspartner Få en dedikeret partner, der er fokuseret på at hjælpe jer med at vokse. Med regelmæssige gennemgang af jeres konto vil vi identificere muligheder for forbedring og sikre, at jeres team udnytter Penneos fulde potentiale. Adgang til API Sandbox Giv jeres udviklere adgang til Penneos sandbox-miljø. Her kan I i trygge rammer simulere API-kald, teste forskellige scenarier og validere jeres kode. Det sikrer, at alt fungerer som forventet, inden I tager løsningen i brug. BOOK ET MØDE Har du brug for hurtig hjælp? Vi ringer dig op inden for 20 minutter. Populære funktioner Inkluderet Kundeservice 4,3 stjerner hos Trustpilot Inkluderet Automatic reminders to signers Inkluderet Dashboard overview Tilføjelse Internationale underskrifter med pas & itsme® Tilføjelse Formularer Tilføjelse Brugerdefineret underskriftsflow SE ALLE PENNEO FUNKTIONER Digital tillid mellem parterne Når forretningsinteraktioner bliver mere og mere digitale, er behovet for tillid større end nogensinde. Penneo sikrer tillid mellem virksomheder og deres klienter ved at tilbyde en platform, der møder de højeste sikkerhedsstandarder, og som er i overensstemmelse med EU og national lovgivning. Sammenlign planer Sign Essential Sign Plus Sign Pro Send flere dokumenter på én gang Tilføj flere filer i en forsendelse for at sende dem til underskrift på én gang. Underskriv flere dokumenter på én gang Underskriv alle dokumenter i forsendelsen på samme tid, og brug kun dit eID én gang. Underskrift med national eID De nationale eID, vi understøtter, er: MitID, MitID Erhverv,BankID NO, BankID SE, FTN, .beID. Vi understøtter også itsmeⓇ mod et tillæg. Mulighed for at tilføje flere underskrivere Nogle forsendelser kræver underskrifter fra mere end én person. I Penneo Sign kan du tilføje det nødvendige antal underskrivere til hver forsendelse. Mulighed for at tilføje modtagere Modtagere er personer, der skal modtage dokumenterne i din forsendelse, men som ikke behøver at underskrive. Automatiske påmindelser Penneo Sign sender automatiske påmindelsesmails til underskrivere for at minde dem om at underskrive de nødvendige dokumenter. Flere standardfunktioner Automatiske opdateringsmails Ejere af forsendelser modtager automatiske mails for at holde styr på opdateringerne i forsendelserne og underskrivernes handlinger. Anmodning om underskrift og bekræftelsesmail Underskriv ved at tegne en underskrift Underskriv ved at uploade et billede af din underskrift Visnings- og underskriftsbegrænsninger Beskyt dine dokumenter ved at kontrollere, hvem der har tilladelse til at se og underskrive dem. SMS verifikation En adgangsbegrænsningsmetode, der giver dig mulighed for at kontrollere, hvem der er autoriseret til at se og underskrive dokumenter. Hændelseslog Se alle afsluttede handlinger vedrørende forsendelsen i hændelsesloggen. Kontakter Dokumentarkiv Sikkert og organiseret arkiv af alle underskrevne dokumenter, som hjælper din virksomhed med at holde styr på forsendelser. Personligt arkiv Underskrivere kan vælge at have et personligt arkiv, som giver dem adgang til alle deres underskrevne dokumenter. E-mail-skabeloner og -signaturer Tilpas dine e-mails med anmodning om underskrift, herunder en brugerdefineret e-mailsignatur. Penneo Sign fås på 8 sprog Dansk, engelsk, tysk, svensk, norsk, finsk, hollandsk & fransk. Tilpassede funktioner Branchespecifikke underskriftsflows Visse arbejdsopgaver (f.eks. årsrapporter) kræver underskrifter i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet af de rigtige personer i den rigtige rækkefølge. Penneo Sign indeholder et udvalg af typiske underskriftsflows, der hjælper med at lette de manuelle processer, der er involveret i at indsamle underskrifter i den rigtige rækkefølge. Tilpas udseende Tilpas Penneo Sign interfacet, så det passer til din virksomheds brandidentitet. Analytics Penneo Sign Dashboard Penneo Sign-dashboardet indeholder et udvalg af standarddata og analyser, f.eks. antal forsendelser, aktuel status for forsendelser, nyligt afsluttede forsendelser og meget mere. Forbrugsoversigt Du får et klart overblik over, hvordan Penneo Sign bliver brugt i din organisation, herunder de vigtigste tal: Hvor mange dokumenter er blevet underskrevet? Hvor aktive er jeres brugere? Og hvordan ændrer jeres aktivitet sig fra måned til måned? Integrationer og API SSO Brugere kan oprette en bruger eller logge ind med deres virksomheds Google- og Microsoft-konti. Integrationer (med undtagelse af Caseware) Penneo Sign er integreret med: Silverfin, Adminpulse, Ratios, Instaclause, M-Files, Anlisa, Advisor, Unik Bolig, Unik Advosys, EG AdvoPro, EG Strato, EG Bolig, ByteLab, KTP, Legis 365, ELO, Documendo, 4human, Emply, Talentech, TimePlan. Caseware-integration Ifølge aftalen med Caseware Denmark skal Penneo pålægge et integrationsgebyr på minimum 10 kr. pr. CVR/årsrapport, som kunden har. Vores minimumsgebyr er 500 kr. om måneden (6.000 kr. årligt). DKK 10 pr. CVR/annual report 10 kr. pr. CVR/årsrapport 10 kr. pr. CVR/årsrapport API-adgang Sandbox-adgang Support og ydelser Kundeservice Kontakt kundesupport via vores sagsstyringssystem, og få adgang til en oversigt, så du kan holde styr på dine åbne og afsluttede sager. Hjælpecenter Onboarding Webinarer Dedikeret supportline Står i med et akut problem? Kontakt vores supportlinje og tal direkte med en af vores produktspecialister. Personlig onboardingplan Vi skræddersyr jeres onboardingoplevelse, så den passer perfekt til jeres teams specifikke behov. 10,000 DKK 10,000 DKK Dedikeret sparringspartner Få en dedikeret partner, der er fokuseret på at hjælpe jer med at vokse. Med regelmæssige gennemgang af jeres konto vil vi identificere muligheder for forbedring og sikre, at jeres team udnytter Penneos fulde potentiale. Adgang til API Sandbox Giv jeres udviklere adgang til Penneos sandbox-miljø. Her kan I i trygge rammer simulere API-kald, teste forskellige scenarier og validere jeres kode. Det sikrer, at alt fungerer som forventet, inden I tager løsningen i brug. Kontinuerlig onboarding (pris pr. time) Kontinuerlig mulighed for onboarding af nye kollegaer, eller ifm. introduktion af nye funktioner. 1,200 DKK 1,200 DKK 1,200 DKK Add-ons Underskrift med itsme® (pris pr. signatur) 12 DKK 12 DKK 12 DKK Underskrift med pas (pris pr. signatur) 12 DKK 12 DKK 12 DKK Tilpassede underskriftsflows (pris pr. tilpasset underskriftsflow) Visse arbejdsprocesser kræver, at underskrifter foretages i en bestemt rækkefølge. Underskriftsflows giver dig mulighed for at få dokumenter underskrevet i den rigtige rækkefølge. Vi tilbyder også skræddersyede underskrifsflows til din virksomheds specifikke behov. 20,000 DKK 20,000 DKK 20,000 DKK Formularer (ubegrænset adgang og oprettelse af formularer) 4,000 DKK 4,000 DKK 4,000 DKK Registreret brev (pris pr. brev) 10 DKK 10 DKK 10 DKK Vores kunder fortæller… “Det sidste skridt i vores digitaliseringsproces var at kunne sige, at vi tilbyder en 100% digital løsning. Det er, hvad Penneo har gjort muligt. Jo lettere vi kan gøre det for vores kunder at modtage, underskrive og returnere dokumenter, jo mere gnidningsløst bliver vores daglige arbejde.” – Julie van der Mast, revisor og direktør hos Finezz Accountants Ofte stillede spørgsmål Tilbyder Penneo produkttræning, onboarding og supporttjenester, og koster det noget? Penneo tilbyder online træning, tutorials og online onboarding-sessioner til alle nye kunder. Derudover tilbyder vi et omfattende hjælpecenter og support til alle kunder. Som kunde har du mulighed for at købe dedikeret onboarding, løbende onboarding af nye medarbejdere og adgang til premium-support, herunder telefon- og prioritetsservice. Hvor sikre er mine data med Penneo, og koster det noget at få ekstra sikkerhedsfunktioner? Penneo sørger for, at alle kundedata er beskyttet i henhold til de højeste standarder for informationssikkerhed. Penneo er certificeret i henhold til ISO 27001 og 27701. Disse certificeringer er gældende for vores arbejde med alle kunder, uden ekstra omkostninger. Er der volumenbaserede rabatter til store virksomheder? Vores pris pr. kunde (KYC) eller pris pr. underskrift (SIGN) varierer afhængigt af den mængde, du forpligter dig til. Hvis du forpligter dig til en større mængde, får du en billigere enhedspris. Du får altid den bedste samlede pris, hvis du forpligter dig til den mængde, du tror, du vil bruge. Hvad sker der, hvis mit forbrug overstiger mit abonnement? Hvis du bruger mere end den tildelte mængde i din pakke, vil du blive opkrævet det tilsvarende beløb (baseret på den aftalte enhedspris) ved udgangen af din abonnementsperiode eller ved fornyelse. Kan jeg foretage ændringer i mit abonnement baseret på forbrug? Hvis du forventer et højere forbrug, end du har forpligtet dig til, kan du til enhver tid opgradere dit abonnement til flere underskrifter/klienter, hvilket sandsynligvis vil føre til en bedre enhedspris. Det er kun muligt at nedgradere dit abonnement i slutningen af din abonnementsperiode. Hvornår/hvordan kan jeg opsige mit abonnement? Du kan opsige dit abonnement med mindst 3 måneders varsel, før dit abonnement fornyes. Hvad er betalingsbetingelserne, og hvilke betalingsformer accepteres? Penneos standardbetalingsfrist er 14 dage. Vi accepterer betalinger via bankoverførsel (standard) og kortbetaling (til de mindste kunder). Er der nogen ekstra omkostninger eller skjulte gebyrer? Alle priser vises tydeligt på vores hjemmeside. Men hvis du vælger at tilføje eller bruge tjenester ud over den pakke, du har købt, kan der påløbe ekstra gebyrer. Se hvad du kan opnå med Penneo FÅ ET TILBUD 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:35 |
https://wiki.php.net/vcs/gitworkflow?do=revisions | PHP: vcs:gitworkflow Login Register You are here: start › vcs › gitworkflow vcs:gitworkflow Permission Denied Sorry, you don't have enough rights to continue. Login You are currently not logged in! Enter your authentication credentials below to log in. You need to have cookies enabled to log in. Log In Username Password Remember me Log In You don't have an account yet? Just get one: Register Forgotten your password? Get a new one: Set new password vcs/gitworkflow.txt · Last modified: 2025/08/06 10:03 by derick Page Tools Show page Old revisions Backlinks Back to top Copyright © 2001-2026 The PHP Group Other PHP.net sites Privacy policy | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/zh_cn/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-add-triggers.html | 为 Lambda@Edge 函数添加触发器 - Amazon CloudFront 为 Lambda@Edge 函数添加触发器 - Amazon CloudFront 文档 Amazon CloudFront 开发人员指南 为 Lambda@Edge 函数添加触发器 Lambda@Edge 触发器是指 CloudFront 分配、缓存行为与使函数开始执行的事件的组合。例如，您可以创建一个触发器，在 CloudFront 收到来自为分配所设置的特定缓存行为查看器的请求时执行函数。您可以指定一个或多个 CloudFront 触发器。 提示 在创建 CloudFront 分配时，您可以指定一些设置来告诉 CloudFront 在收到不同的请求时如何响应。默认设置称为分配的 默认缓存行为 。您可以设置其他缓存行为来定义 CloudFront 在特定情况下（例如，在收到特定文件类型的请求时）如何响应。有关更多信息，请参阅 缓存行为设置 。 首次创建 Lambda 函数时，可以仅指定 一个 触发器。您可以通过使用 Lambda 控制台或在 CloudFront 控制台中编辑分配，在稍后向同一函数中添加更多触发器。 如果您要将更多触发器添加到同一 CloudFront 分配的函数中，那么使用 Lambda 控制台非常有效。 如果要为多个分配添加触发器，那么使用 CloudFront 控制台非常有效，因为这样更方便查找您要更新的分配。您同时还可以更新其他 CloudFront 设置。 主题 可以触发 Lambda@Edge 函数的 CloudFront 事件 选择要触发函数的事件 将触发器添加到 Lambda@Edge 函数中 Javascript 在您的浏览器中被禁用或不可用。 要使用 Amazon Web Services 文档，必须启用 Javascript。请参阅浏览器的帮助页面以了解相关说明。 文档惯例 编辑 Lambda 函数 将 CloudFront 事件作为触发器 此页面对您有帮助吗？- 是 感谢您对我们工作的肯定！ 如果不耽误您的时间，请告诉我们做得好的地方，让我们做得更好。 此页面对您有帮助吗？- 否 感谢您告诉我们本页内容还需要完善。很抱歉让您失望了。 如果不耽误您的时间，请告诉我们如何改进文档。 | 2026-01-13T09:30:35 |
https://vml.visma.ai/privacy | Privacy Policy | Visma Machine Learning About us Who are we? Learn more about Visma Machine Learning What we do Learn more about the products we offer What our customers say Read our customers' testimonials Products Autosuggest Automate your workflow Smartscan Extract data from your documents Resources Blog Product news and showcases Showcase of prototypes Prototypes, ideas and experiments Support Get started Find out more about onboarding to Visma Machine Learning FAQ We have answers to your frequently asked questions. Privacy policy Learn how we handle your data and protect your privacy Cookie policy Learn about how we use cookies to enhance your experience API Documentation Contact Us About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Showcase of prototypes Support Get started FAQ Privacy policy Cookie policy API Documentation Loading... Gærtorvet 1-5 1799 Copenhagen Denmark E-mail: worksmarter@visma.com About us Who are we? What we do What our customers say Products Autosuggest Smartscan Resources Blog Prototypes Documentation Support Get started FAQ Privacy policy Cookie policy Security Information Operating Status © 2026 Visma Group. All rights reserved Privacy and data security information Learn more about how we handle your data and protect your privacy. Security Information At Visma, safety is our priority. Our customers trust us with their data and it is critical that we implement the necessary level of security to protect that data. Information Security Visma Machine Learning (Visma ML Assets) complies with GDPR legislation and is ISO 27001 and 900 certified. Visma ML Assets uses certified infrastructure for hosting and data storage. Visma ML Assets's security is based on Visma Group's own security program ( Visma Security Program ), which is mandatory for all Visma products. ISO 27001 & 9001 Certified As an essential part of the operation and security of the service, we also adopt Visma's application delivery model process ( Visma Cloud Delivery Model , VCDM for short), which ensures high standardisation and efficient operation of the systems. VCDM is a framework to deliver cloud software to customer needs. The framework is based on a set of core principles and focuses on DevOps and Continuous Delivery. VCDM has the following audit assurance report and certifications: ISAE 3402 Type II ISO 27001 Visma ML Assets's certificate can be downloaded here . ISO 27001 ensures high-security standards when processing your data ISO 27001 is an internationally recognized standard for information security systems Visma Group Security and Compliance Standards Through Visma's programs that we are enrolled in, our work is structured to ensure stable and consistent delivery of service as well as secure and trustworthy management of customer data. From the following links, you can familiarise yourself with Visma's compliance work and how data security and data protection have been implemented in our services: Visma Cloud Delivery Model (VCDM) Visma Application Security Program (VASP) The Visma Security Program and the Visma Architecture and Technology Program are integrated in VCDM. Our Information Security Management System (ISMS) is certified according to ISO 27001 and it's audited annually by an independent IT auditor. Visma Trust Centre More information about Visma's security program and compliance work can be found at the Visma Trust Centre . More about these frameworks here: Visma Trust Centre Visma Trust Centre - ML Assets Visma Cloud Delivery Model (VCDM) Visma Application Security Program (VASP) Please contact our team for more details, if needed. Compliant with Privacy Regulations We at Visma ML Assets enforce processing in the EU to support GDPR. All data processed is saved within the EU and our processes are GDPR compliant. Our servers and privacy policy are GDPR compliant All data are processed under the Data Processing Agreement Our servers are safely located in Europe Visma ML Assets has carefully selected sub-processors who help us store your data and increase the level of security. Visma ML Assets is fully hosted in EU data centres on Google Cloud Platform. Visma Group's privacy statement can be found at https://www.visma.com/privacy-statement . The website contains information in accordance with the GDPR on how Visma processes personal data both as controller and processor of personal data, as well as information on the rights of data subjects. Availability Visma ML Assets makes every effort to make its APIs available on a continuous basis 24 hours a day, 7 days a week, so we can offer our customers predictability. Our ISO certifications require a minimum uptime of 99.8%, which Visma ML Assets satisfies. The Visma status page reports the incidents for our APIs, below Common Services > Machine Learning Assets . On the status page you will find an up-to-date overview of the statuses of our system. You can subscribe to updates, where you get email notifications whenever Visma Cloud Services creates, updates or resolves an incident. Whistleblower channel Visma has its own whistleblower channel , where employees, former employees, customers, suppliers and others can report objectionable conditions in Visma and any breaches of Visma's obligations to respect human rights and decent working conditions. The Visma Whistleblowing Channel is a tool that enables the anonymous submission of (suspected) violations of local and/or EU/EEA regulations both within Visma and outside, as well as violations of Visma's own guidelines. The channel ensures confidential communication between the whistleblower and the person who processes the complaint internally. Visma ML Assets is connected to this channel. Report any concern you might have through the Visma Whistleblowing website . | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-add-triggers.html | Ajout de déclencheurs pour une fonction Lambda@Edge - Amazon CloudFront Ajout de déclencheurs pour une fonction Lambda@Edge - 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. Ajout de déclencheurs pour une fonction Lambda@Edge Un déclencheur Lambda @Edge est une combinaison d'une CloudFront distribution, d'un comportement de cache et d'un événement qui entraîne l'exécution d'une fonction. Par exemple, vous pouvez créer un déclencheur qui entraîne l'exécution de la fonction lorsqu'un utilisateur CloudFront reçoit une demande concernant un comportement de cache spécifique que vous avez configuré pour votre distribution. Vous pouvez spécifier un ou plusieurs CloudFront déclencheurs. Astuce Lorsque vous créez une CloudFront distribution, vous spécifiez des paramètres qui indiquent CloudFront comment répondre lorsqu'elle reçoit différentes demandes. Les paramètres par défaut correspondent au comportement de cache par défaut pour la distribution. Vous pouvez configurer des comportements de cache supplémentaires qui définissent la manière dont il CloudFront répond dans des circonstances spécifiques, par exemple lorsqu'il reçoit une demande pour un type de fichier spécifique. Pour de plus amples informations, veuillez consulter Paramètres de comportement du cache . Lorsque vous créez pour la première fois une fonction Lambda, vous ne pouvez spécifier qu’ un seul déclencheur. Vous pouvez ajouter d'autres déclencheurs à la même fonction ultérieurement en utilisant la console Lambda ou en modifiant la distribution dans la CloudFront console. La console Lambda fonctionne bien si vous souhaitez ajouter d'autres déclencheurs à une fonction pour la même CloudFront distribution. La CloudFront console peut être meilleure si vous souhaitez ajouter des déclencheurs pour plusieurs distributions, car il est plus facile de trouver la distribution que vous souhaitez mettre à jour. Vous pouvez également mettre à jour d'autres CloudFront paramètres en même temps. Rubriques CloudFront événements pouvant déclencher une fonction Lambda @Edge Choix de l’événement qui déclenche la fonction Ajout de déclencheurs à une fonction Lambda@Edge 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 Modification d’une fonction Lambda CloudFront événements en tant que déclencheurs 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:35 |
https://docs.aws.amazon.com/lambda/latest/dg/intro-permission-model.html#lambda-intro-execution-role | Managing permissions in AWS Lambda - AWS Lambda Managing permissions in AWS Lambda - AWS Lambda Documentation AWS Lambda Developer Guide Managing permissions in AWS Lambda You can use AWS Identity and Access Management (IAM) to manage permissions in AWS Lambda. There are two main categories of permissions that you need to consider when working with Lambda functions: Permissions that your Lambda functions need to perform API actions and access other AWS resources Permissions that other AWS users and entities need to access your Lambda functions Lambda functions often need to access other AWS resources, and perform various API operations on those resources. For example, you might have a Lambda function that responds to an event by updating entries in an Amazon DynamoDB database. In this case, your function needs permissions to access the database, as well as permissions to put or update items in that database. You define the permissions that your Lambda function needs in a special IAM role called an execution role . In this role, you can attach a policy that defines every permission your function needs to access other AWS resources, and read from event sources. Every Lambda function must have an execution role. At a minimum, your execution role must have access to Amazon CloudWatch because Lambda functions log to CloudWatch Logs by default. You can attach the AWSLambdaBasicExecutionRole managed policy to your execution role to satisfy this requirement. To give other AWS accounts, organizations, and services permissions to access your Lambda resources, you have a few options: You can use identity-based policies to grant other users access to your Lambda resources. Identity-based policies can apply to users directly, or to groups and roles that are associated with a user. You can use resource-based policies to give other accounts and AWS services permissions to access your Lambda resources. When a user tries to access a Lambda resource, Lambda considers both the user's identity-based policies and the resource's resource-based policy. When an AWS service such as Amazon Simple Storage Service (Amazon S3) calls your Lambda function, Lambda considers only the resource-based policy. You can use an attribute-based access control (ABAC) model to control access to your Lambda functions. With ABAC, you can attach tags to a Lambda function, pass them in certain API requests, or attach them to the IAM principal making the request. Specify the same tags in the condition element of an IAM policy to control function access. In AWS, it's a best practice to grant only the permissions required to perform a task ( least-privilege permissions ). To implement this in Lambda, we recommend starting with an AWS managed policy . You can use these managed policies as-is, or as a starting point for writing your own more restrictive policies. To help you fine-tune your permissions for least-privilege access, Lambda provides some additional conditions you can include in your policies. For more information, see Fine-tuning the Resources and Conditions sections of policies . For more information about IAM, see the IAM User Guide . 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 Execution role (permissions for functions to access other resources) 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:35 |
https://hackmd.io/blog | The HackMD Blog: Home Blog Product Company Changelog Education Sign in Sign in Get HackMD free # en # company 2025 in Review: New Features, Big Wins, and What Lies Ahead Dec 31, 2025 By Chaseton Collins Read more Recent posts # en # use-case Build Better AI Workflows: Creating and Organizing Claude Skills in HackMD A practical guide to understanding Claude Skills and learning how to build, structure, and organize them inside HackMD using templates, folders, and reusable markdown systems. Dec 10, 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 # 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 # use-case From Wallet to Workspace: Decentralize using Sign-in with ETH Reintroducing Sign in with Wallet on HackMD. Use your Ethereum wallet to access docs with ownership, privacy, and speed. Step-by-step guide to connect included. Nov 5, 2025 By Chaseton Collins # 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 # 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 1 2 3 20 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 Changelog View Changelog Improved Tag Management Manage Tags in Bulk from the Sidebar Sep 23, 2025 Profile Overhaul: Pin Notes, Categories & Connections Your new profile: The business card for your expertise. Sep 4, 2025 Cite Paragraphs, Stay Connected Quickly add quotes with automatic footnotes and discover how your ideas inspire others. Aug 5, 2025 Use Guided Comments to Spark Better Feedback Guided Comments gently prompt visitors, making feedback easier and more meaningful. Jul 8, 2025 Get started for free Play around with it first. Pay and add your team later. Get started for free 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:35 |
https://docs.aws.amazon.com/ko_kr/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-add-triggers.html | Lambda@Edge 함수에 대한 트리거 추가 - Amazon CloudFront Lambda@Edge 함수에 대한 트리거 추가 - Amazon CloudFront 설명서 Amazon CloudFront 개발자 가이드 Lambda@Edge 함수에 대한 트리거 추가 Lambda@Edge 트리거는 CloudFront 배포, 캐시 동작, 그리고 함수 실행을 유도하는 이벤트를 하나로 조합한 것입니다. 예를 들어, 최종 사용자가 해당 배포에 설정된 특정 캐시 동작을 CloudFront에 요청하면 함수가 실행되도록 하는 트리거를 생성할 수 있습니다. 하나 이상의 CloudFront 트리거를 지정할 수 있습니다. 작은 정보 CloudFront 배포를 생성할 때 다른 요청을 수신할 때 응답하는 방법을 CloudFront에게 알려주는 설정을 지정합니다. 기본 설정을 배포에 대한 기본 캐시 동작 이라고 합니다. CloudFront가 특정한 상황(예를 들어, 특정 파일 유형에 대한 요청을 수신할 때)에서 응답하는 방법을 정의하는 추가 캐시 동작을 설정할 수 있습니다. 자세한 내용은 캐시 동작 설정 섹션을 참조하세요. Lambda 함수를 처음 생성할 때는 트리거를 하나 만 지정할 수 있습니다. 나중에 Lambda 콘솔을 사용하거나 CloudFront 콘솔에서 배포를 편집하여 동일한 함수에 더 많은 트리거를 추가할 수 있습니다. Lambda 콘솔을 사용하는 방법은 동일한 CloudFront 배포에 대한 함수에 트리거를 더 추가하려는 경우에 적합합니다. CloudFront 콘솔을 사용하는 방법은 업데이트하려는 배포를 쉽게 찾을 수 있기 때문에 여러 배포에 대한 트리거를 추가하려는 경우에 더 적합할 수 있습니다. 또한 동시에 다른 CloudFront 설정을 업데이트할 수 있습니다. 주제 Lambda@Edge 함수를 트리거할 수 있는 CloudFront 이벤트 함수를 트리거할 이벤트를 선택합니다. Lambda@Edge 함수에 트리거 추가 javascript가 브라우저에서 비활성화되거나 사용이 불가합니다. AWS 설명서를 사용하려면 Javascript가 활성화되어야 합니다. 지침을 보려면 브라우저의 도움말 페이지를 참조하십시오. 문서 규칙 Lambda 함수 편집 트리거로서의 CloudFront 이벤트 이 페이지의 내용이 도움이 되었습니까? - 예 칭찬해 주셔서 감사합니다! 잠깐 시간을 내어 좋았던 부분을 알려 주시면 더 열심히 만들어 보겠습니다. 이 페이지의 내용이 도움이 되었습니까? - 아니요 이 페이지에 작업이 필요하다는 점을 알려 주셔서 감사합니다. 실망시켜 드려 죄송합니다. 잠깐 시간을 내어 설명서를 향상시킬 수 있는 방법에 대해 말씀해 주십시오. | 2026-01-13T09:30:35 |
https://www.iso.org/es/home/about-iso/what-we-do.html | ISO - Qué es lo que hacemos 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 Sobre nosotros Qué es lo que hacemos Elaboración de las normas Investigación Desarrollo de capacidades Somos una red global de los normalizadores mejor cualificados del mundo. A través de nuestros miembros (organismos nacionales de normalización de 175 países) reunimos a expertos de todo el mundo para elaborar las Normas Internacionales. Consulte más información sobre nuestros miembros y el proceso de elaboración de normas . Además de gestionar miles de documentos a través de su redacción, revisión, votación y publicación, también proporcionamos una gran variedad de servicios que cumplen con nuestros objetivos estratégicos. Entre ellos, trabajamos para ayudar a concienciar al público sobre la importancia de las normas y la normalización. Trabajamos con otras organizaciones como la IEC y la UIT para crear anualmente el Día Mundial de la Normalización . Organizaciones de normalización de todo el mundo celebran este día, en el que se analiza cómo las normas abordan los retos a los que se enfrenta la sociedad actual . La ISO también permite la participación del público general a través de su comité de consumidores para el desarrollo de las normas ( COPOLCO ). Promovemos la enseñanza de la normalización participando directamente en un programa de máster conjunto, ayudando a nuestros miembros a crear programas similares y manteniendo una base de datos de materiales relacionados con las normas en la enseñanza a todos los niveles. Además de concienciar a nuestros miembros, también los ayudamos a través de la formación y actuamos como un recurso para la investigación en materia de normas . Para más información sobre la estrategia de ISO, consulte nuestro plan estratégico y nuestro informe anual . Aun así, todo se reduce a un único objetivo: concienciar a nuestros miembros para que utilicen las normas en todos los ámbitos. ¿Cuáles son los diferentes tipos de suscripción a la ISO? Los miembros plenos (u organismos miembros) influyen en el desarrollo de las normas y la estrategia de ISO, participando y votando en las reuniones técnicas y políticas de ISO. Los miembros plenos venden y adoptan las Normas Internacionales ISO a escala nacional. Los miembros correspondientes observan el desarrollo de las normas y la estrategia de ISO asistiendo como observadores a las reuniones técnicas y políticas de ISO. Los miembros correspondientes son entidades nacionales que venden y adoptan las Normas Internacionales ISO a escala nacional. Los miembros correspondientes en los territorios que no son entidades nacionales se encargan de vender las Normas Internacionales ISO dentro de su territorio. Los miembros suscriptores se mantienen al día del trabajo realizado por ISO, pero no pueden participar en él. No venden ni adoptan Normas Internacionales ISO a escala nacional. Para obtener más información sobre la afiliación a ISO y sus ventajas, consulte el Manual de suscripción a ISO . A continuación, podrá descubrir cómo apoya ISO a sus miembros para que avancen en su labor de normalización a través de la formación, la investigación y los premios de normalización. Investigación Discover the ISO Research Grant, our Research & Innovation Network, the ISO Research Library or learn about global trends and how they relate to standardization. Developing standards Find out how the ISO process bring together global experts to create standards that are chosen the world over. ISO awards ISO has a number of awards that help promote different aspects of international standardization. Educación sobre las normas Materials that support teaching the technological, economic and societal benefits of International Standards. ISO Strategy 2030 The ISO Strategy 2030 outlines our vision and our mission for the next 10 years and a set of goals and priorities to help us get there. The three goals are stepping stones to our vision. We will focus on six priorities to achieve our goals and maximize our impact. ISO Membership Manual Learn how to get the most out of ISO membership Our latest Announcements 11 diciembre 2025 International Standards at the heart of development: ISO joins the World Bank in launching the World Development Report 2025 ISO today joins the World Bank to mark the official launch of the World Development Report 2025: Standards for Development. For the first time in its 45-year history, the World Bank’s flagship report is … 8 diciembre 2025 Good data, better decisions: ISO showcases new environmental standards dashboard at UNEA-7 As the 7th United Nations Environment Assembly (UNEA-7) convenes in Nairobi this week, ISO, in collaboration with Standards Australia, is showcasing a new interactive dashboard designed to help policymakers, … 2 diciembre 2025 International Organizations align at International AI Standards Summit Seoul Statement enshrines commitment to advance the wellbeing of humanity through standards in the AI revolution. All Announcements PRESS CONTACT Sobre nosotros Qué es lo que hacemos 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:35 |
https://docs.aws.amazon.com/zh_tw/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 會攔截在 CloudFront 節點的請求和回應。您可以在發生下列 CloudFront 事件時執行 Lambda 函數： 當 CloudFront 接收到來自檢視器的請求 (檢視器請求) 時 在 CloudFront 轉寄請求至來源 (原始請求) 之前 當 CloudFront 接收到來自來源的回應 (原始回應) 時 在 CloudFront 傳回回應給檢視器 (檢視器回應) 之前 如果您使用的是 AWS WAF，則會在套用任何 AWS WAF 規則後執行 Lambda@Edge 檢視器請求。 如需詳細資訊，請參閱 使用請求和回應 及 Lambda@Edge 事件結構說明頁面 。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 使用 Lambda@Edge 進行自訂 使用 Lambda@Edge 的方式 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:30:35 |
https://vi-vn.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 hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/it_it/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Esempi di funzioni Lambda@Edge - Amazon CloudFront Esempi di funzioni Lambda@Edge - Amazon CloudFront Documentazione Amazon CloudFront Guida per gli sviluppatori Esempi generali Generazione di risposte: esempi Stringhe di query: esempi Esempi di personalizzazione del contenuto in base alle intestazioni del paese o del tipo di dispositivo Esempi di selezione dinamica dell'origine in funzione del contenuto Aggiornamento degli stati di errore: esempi Accesso al corpo della richiesta: esempi 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à. Esempi di funzioni Lambda@Edge Guarda i seguenti esempi per utilizzare le funzioni Lambda con Amazon. CloudFront Nota Se scegli Node.js 18 o versioni successive come runtime per la funzione Lambda@Edge, viene creato automaticamente un file index.mjs . Per utilizzare i seguenti esempi di codice, rinomina invece il file index.mjs in index.js . Argomenti Esempi generali Generazione di risposte: esempi Stringhe di query: esempi Esempi di personalizzazione del contenuto in base alle intestazioni del paese o del tipo di dispositivo Esempi di selezione dinamica dell'origine in funzione del contenuto Aggiornamento degli stati di errore: esempi Accesso al corpo della richiesta: esempi Esempi generali Gli esempi seguenti mostrano i modi più comuni di usare Lambda @Edge in. CloudFront Argomenti Esempio: test A/B Esempio: sostituzione di un’intestazione di risposta Esempio: test A/B È possibile utilizzare l'esempio seguente per testare due diverse versioni di un'immagine senza creare reindirizzamenti o modificare l'URL. Questo esempio legge i cookie nella richiesta del visualizzatore e modifica l'URL della richiesta di conseguenza. Se il visualizzatore non invia un cookie con uno dei valori previsti, l'esempio assegna casualmente il visualizzatore a uno dei. URLs Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request Esempio: sostituzione di un’intestazione di risposta L'esempio seguente mostra come modificare il valore di un'intestazione di risposta in base al valore di un'altra intestazione. Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response Generazione di risposte: esempi Gli esempi seguenti illustrano come è possibile usare Lambda@Edge per generare risposte. Argomenti Esempio: distribuzione di contenuto statico (risposta generata) Esempio: generazione di un reindirizzamento HTTP (risposta generata) Esempio: distribuzione di contenuto statico (risposta generata) L'esempio seguente mostra come utilizzare una funzione Lambda per distribuire contenuto Web statico e quindi ridurre il carico sul server di origine e la latenza complessiva. Nota È possibile generare risposte HTTP solo per eventi di richiesta origine e visualizzatore. Per ulteriori informazioni, consulta Generazione di risposte HTTP in trigger di richiesta . È inoltre possibile sostituire o rimuovere il corpo della risposta HTTP negli eventi di richiesta origine. Per ulteriori informazioni, consulta Aggiornamento delle risposte HTTP nei trigger di risposta origine . Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response Esempio: generazione di un reindirizzamento HTTP (risposta generata) L'esempio seguente mostra come generare un reindirizzamento HTTP. Nota È possibile generare risposte HTTP solo per eventi di richiesta origine e visualizzatore. Per ulteriori informazioni, consulta Generazione di risposte HTTP in trigger di richiesta . Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response Stringhe di query: esempi Gli esempi seguenti illustrano i modi in cui è possibile usare Lambda@Edge con le stringhe di query. Argomenti Esempio: aggiunta di un’intestazione in base a un parametro di stringa di query Esempio: normalizzazione dei parametri di stringa di query per migliorare il numero di riscontri nella cache Esempio: reindirizzamento di utenti non autenticati a un pagina di accesso Esempio: aggiunta di un’intestazione in base a un parametro di stringa di query L'esempio seguente mostra come ottenere la coppia chiave-valore di un parametro di stringa di query e aggiungere quindi un'intestazione in base a tali valori. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request Esempio: normalizzazione dei parametri di stringa di query per migliorare il numero di riscontri nella cache L'esempio seguente mostra come migliorare il rapporto di accesso alla cache apportando le seguenti modifiche alle stringhe di query prima di CloudFront inoltrare le richieste all'origine: Ordina alfabeticamente le coppie chiave-valore in base al nome del parametro Cambia le coppie chiave-valore da maiuscolo in minuscolo Per ulteriori informazioni, consulta Memorizzazione nella cache di contenuti basati su parametri delle stringhe di query . Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request Esempio: reindirizzamento di utenti non autenticati a un pagina di accesso L'esempio seguente mostra come reindirizzare gli utenti a una pagina di accesso se non hanno immesso le loro credenziali. Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response Esempi di personalizzazione del contenuto in base alle intestazioni del paese o del tipo di dispositivo Gli esempi seguenti illustrano come utilizzare Lambda@Edge per personalizzare il comportamento in base alla posizione o al tipo di dispositivo usato dal visualizzatore. Argomenti Esempio: reindirizzamento di richieste visualizzatore a un URL specifico di un paese Esempio: distribuzione di versioni differenti di un oggetto in base al dispositivo Esempio: reindirizzamento di richieste visualizzatore a un URL specifico di un paese L'esempio seguente mostra come generare una risposta di reindirizzamento HTTP con un URL specifico di un paese e restituire la risposta al visualizzatore. Ciò è utile quando intendi fornire risposte relative a un paese. Ad esempio: Se hai sottodomini specifici di un paese, ad esempio us.example.com e tw.example.com, puoi generare una risposta di reindirizzamento quando un visualizzatore richiede example.com. Se stai eseguendo lo streaming di video, ma non disponi dei diritti per lo streaming di contenuto in un determinato paese, puoi reindirizzare gli utenti in quel paese a una pagina che spiega perché non sono in grado di riprodurre il video. Tieni presente quanto segue: Devi configurare la tua distribuzione in modo tale che la memorizzazione nella cache venga eseguita in base all'intestazione CloudFront-Viewer-Country . Per ulteriori informazioni, consulta Cache Based on Selected Request Headers (Cache in base a intestazioni di richiesta selezionate) . CloudFront aggiunge l' CloudFront-Viewer-Country intestazione dopo l'evento di richiesta del visualizzatore. Per utilizzare questo esempio, devi creare un trigger per l'evento di richiesta origine. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response Esempio: distribuzione di versioni differenti di un oggetto in base al dispositivo L'esempio seguente mostra come servire diverse versioni di un oggetto in base al tipo di dispositivo che l'utente sta utilizzando, ad esempio, un dispositivo mobile o un tablet. Tieni presente quanto segue: Devi configurare la tua distribuzione in modo tale che la memorizzazione nella cache venga eseguita in base all'intestazione CloudFront-Is-*-Viewer . Per ulteriori informazioni, consulta Cache Based on Selected Request Headers (Cache in base a intestazioni di richiesta selezionate) . CloudFront aggiunge le CloudFront-Is-*-Viewer intestazioni dopo l'evento di richiesta del visualizzatore. Per utilizzare questo esempio, devi creare un trigger per l'evento di richiesta origine. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request Esempi di selezione dinamica dell'origine in funzione del contenuto Gli esempi seguenti mostrano in che modo è possibile usare Lambda@Edge per l’instradamento a diverse origini in base alle informazioni nella richiesta. Argomenti Esempio: utilizzo di un trigger di richiesta origine per passare da un’origine personalizzata a un’origine Amazon S3 Esempio: utilizzo di un trigger di richiesta origine per modificare la regione dell’origine Amazon S3 Esempio: utilizzo di un trigger di richiesta origine per passare da un’origine Amazon S3 a un’origine personalizzata Esempio: utilizzo di un trigger di richiesta origine per trasferire progressivamente il traffico da un bucket Amazon S3 a un altro Esempio: utilizzo di un trigger di richiesta origine per modificare il nome di dominio dell’origine in base all’intestazione del paese Esempio: utilizzo di un trigger di richiesta origine per passare da un’origine personalizzata a un’origine Amazon S3 Questa funzione mostra come utilizzare un trigger di richiesta origine per passare da un'origine personalizzata a un'origine Amazon S3 da cui il contenuto viene recuperato, in base alle proprietà della richiesta. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request Esempio: utilizzo di un trigger di richiesta origine per modificare la regione dell’origine Amazon S3 Questa funzione mostra come utilizzare un trigger di richiesta origine per modificare l'origine Amazon S3 da cui viene recuperato il contenuto, in base alle proprietà della richiesta. In questo esempio viene utilizzato il valore dell'intestazione CloudFront-Viewer-Country per aggiornare il nome di dominio del bucket S3 in un bucket in una regione più vicina al visualizzatore. Questa modifica può essere utile per vari motivi: Riduce le latenze quando la regione specificata è più vicina al paese del visualizzatore. Consente il controllo dei dati verificando che siano serviti da un'origine nello stesso paese in cui è stata effettuata la richiesta. Per utilizzare questo esempio, è necessario eseguire le operazioni indicate di seguito: Configurare la tua distribuzione in modo tale che la memorizzazione nella cache venga eseguita in base all'intestazione CloudFront-Viewer-Country . Per ulteriori informazioni, consulta Cache Based on Selected Request Headers (Cache in base a intestazioni di richiesta selezionate) . Crea un trigger per questa funzione nell'evento di richiesta di origine. CloudFrontaggiunge l' CloudFront-Viewer-Country intestazione dopo l'evento viewer request, quindi per usare questo esempio, devi assicurarti che la funzione venga eseguita per una richiesta di origine. Nota Il codice di esempio seguente utilizza la stessa identità di accesso origine (OAI) per tutti i bucket S3 utilizzati per l’origine. Per ulteriori informazioni, consulta Identità di accesso origine . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Esempio: utilizzo di un trigger di richiesta origine per passare da un’origine Amazon S3 a un’origine personalizzata Questa funzione mostra come utilizzare un trigger di richiesta origine per passare all'origine personalizzata da cui viene recuperato il contenuto in base alle proprietà della richiesta. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request Esempio: utilizzo di un trigger di richiesta origine per trasferire progressivamente il traffico da un bucket Amazon S3 a un altro Questa funzione mostra come è possibile trasferire progressivamente il traffico da un bucket Amazon S3 a un altro in modo controllato. Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Esempio: utilizzo di un trigger di richiesta origine per modificare il nome di dominio dell’origine in base all’intestazione del paese Questa funzione mostra come è possibile modificare il nome di dominio dell'origine in base all'intestazione CloudFront-Viewer-Country , affinché il contenuto venga distribuito da un'origine più vicina al paese del visualizzatore. L'implementazione di questa funzionalità per la distribuzione può offrire i seguenti vantaggi: Riduzione delle latenze quando la regione specificata è più vicina al paese del visualizzatore. Possibilità di controllare i dati verificando che siano distribuiti da un'origine nello stesso paese in cui è stata effettuata la richiesta. Per attivare questa funzionalità, è necessario configurare la distribuzione in modo che la memorizzazione nella cache venga eseguita in base all'intestazione CloudFront-Viewer-Country . Per ulteriori informazioni, consulta Cache Based on Selected Request Headers (Cache in base a intestazioni di richiesta selezionate) . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Aggiornamento degli stati di errore: esempi Gli esempi seguenti forniscono indicazioni su come è possibile usare Lambda@Edge per modificare lo stato di errore che viene restituito agli utenti. Argomenti Esempio: utilizzo di un trigger di risposta origine per aggiornare il codice di stato di errore a 200 Esempio: utilizzo di un trigger di risposta origine per aggiornare il codice di stato di errore a 302 Esempio: utilizzo di un trigger di risposta origine per aggiornare il codice di stato di errore a 200 Questa funzione mostra come puoi aggiornare lo stato della risposta a 200 e generare contenuto di corpo statico da restituire al visualizzatore nel seguente scenario: La funzione viene attivata in una risposta di origine Lo stato delle risposta dal server di origine è codice di stato di errore (4xx e 5xx) Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response Esempio: utilizzo di un trigger di risposta origine per aggiornare il codice di stato di errore a 302 Questa funzione mostra come puoi aggiornare il codice di stato HTTP a 302 per eseguire il reindirizzamento a un altro percorso (comportamento cache) che ha un'origine configurata differente. Tieni presente quanto segue: La funzione viene attivata in una risposta di origine Lo stato delle risposta dal server di origine è codice di stato di errore (4xx e 5xx) Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response Accesso al corpo della richiesta: esempi Gli esempi seguenti illustrano come utilizzare Lambda@Edge con le richieste POST. Nota Per utilizzare questi esempi, è necessario abilitare l'opzione include body (Includi corpo) nell'associazione della funzione Lambda della distribuzione. Non è abilitato per impostazione predefinita. Per abilitare questa impostazione nella CloudFront console, seleziona la casella di controllo Include Body in the Lambda Function Association. Per abilitare questa impostazione nell' CloudFront API o con CloudFormation, imposta il IncludeBody campo su true in LambdaFunctionAssociation . Argomenti Esempio: utilizzo di un trigger di richiesta per leggere un modulo HTML Esempio: utilizzo di un trigger di richiesta per modificare un modulo HTML Esempio: utilizzo di un trigger di richiesta per leggere un modulo HTML Questa funzione dimostra come è possibile elaborare il corpo di una richiesta POST generato da un modulo HTML (modulo Web), ad esempio "Contattaci". Ad esempio, potresti avere un modulo HTML come il seguente: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> Per la funzione di esempio che segue, la funzione deve essere attivata in una richiesta di un visualizzatore CloudFront o di richiesta origine. Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request Esempio: utilizzo di un trigger di richiesta per modificare un modulo HTML Questa funzione dimostra come è possibile modificare il corpo di una richiesta POST generato da un modulo HTML (modulo Web). La funzione viene attivata in una richiesta del CloudFront visualizzatore o in una richiesta di origine. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action to 'replace' 2) body.encoding to the encoding of the new data. Set to one of the following values: text - denotes that the generated body is in text format. Lambda@Edge will propagate this as is. base64 - denotes that the generated body is base64 encoded. Lambda@Edge will base64 decode the data before sending it to the origin. 3) body.data to the new body. ''' request['body']['action'] = ' | 2026-01-13T09:30:35 |
https://wiki.php.net/vcs/gitworkflow?do= | PHP: vcs:gitworkflow Login Register You are here: start › vcs › gitworkflow vcs:gitworkflow Git Workflow Also read gitfaq and CONTRIBUTING.md which have other workflows and PHP git tips. Git does not enforce a certain workflow. For php-src we will use a workflow that is described below. We will use release branches for the php-src.git repository. We will have branches for actively maintained versions. For example: 7.4 , 8.0 , 8.1 and master . A patch will be applied to the oldest possible branch. If the Release Manager of 7.4 accepts the change, commit it to the 7.4 branch. We will use regular merging between the release branches. Bigger features can use feature branches, but developers are encouraged to fork php on github and start implementing the feature there on the respective branch. Bugfix Workflow for Core Developers Core developers that have access to the php-src.git repository apply changes to the lower possible branch and then merge the change upwards. The repository is prepared in a way, that only new changes will be merged upwards. E.g. Git will not attempt to synchronize the whole 5.6 and 7.0 branch. Only your commit will be merged . Here is a visualization of a standard Patch Workflow Let's go through the process of setting it up and doing the merges. Initial Setup $ git clone git@github.com:php/php-src.git $ cd php-src $ git config merge.NEWS.name "Keep the NEWS file" $ git config merge.NEWS.driver 'touch %A' $ git config merge.log true Please refer to Git FAQ for alternative cloning methods via HTTP or the Git Protocol. Patching a release branch Patching the PHP 7.4 branch: $ git checkout PHP-7.4 ... hack hack ... $ git commit <changed files> ... USE A GOOD COMMIT MESSAGE ... ... run tests ... $ git checkout PHP-8.0 $ git merge PHP-7.4 ... run tests ... $ git checkout PHP-8.1 $ git merge PHP-8.0 ... run tests ... $ git checkout PHP-8.2 $ git merge PHP-8.1 ... run tests ... $ git checkout master $ git merge PHP-8.2 ... run tests ... $ gitk master ... review the merges ... $ git push --atomic origin PHP-7.4 PHP-8.0 PHP-8.1 PHP-8.2 master ... push to the official repository ... When you use 'git push --all origin', make sure there are not any unwanted branches in local repository or set branch.<name>.remote properly via git-config. Use the '--atomic' flag to ensure that no refs are updated if the update of any of them fails. Reviewing and closing pull requests Johannes has created a tool to easily close pull requests. It requires a valid PHP account. You can also include Closes GH-NNNN. in the commit message to automatically close a pull request. Merge a pull request Preferably, pull requests should not be merged, but rebased onto the target branch. Because it is common that PRs need to be applied to a different branch than the one it was originally created for, the easiest way to do this is using git am . Patches for use by git am can be obtained by appending .patch to the GitHub URL . For example, to apply pull request #1234 onto branch PHP-7.4: $ git checkout PHP-7.4 $ wget https://github.com/php/php-src/pull/1234.patch $ git am -3 1234.patch $ git commit --am # Adjust commit message to add "Closes GH-1234." ... REVIEW IT ... $ make test .. you better not forget that ... $ git checkout PHP-8.0 $ git merge PHP-7.4 $ make test $ git checkout PHP-8.1 $ git merge PHP-8.0 $ make test $ git checkout master $ git merge PHP-8.1 $ make test $ git push --atomic origin PHP-7.4 PHP-8.0 PHP-8.1 master Additionally, the history of pull requests often requires cleanup. For most pull requests, all commits can be squashed into one. Note about moving patches from a newer branch In case you have to merge a commit from a higher branch. E.g from PHP-8.1 into PHP-7.4 make sure you still merge upwards as described above afterward: $ git checkout PHP-7.4 $ git cherry-pick <SHA1-OF-PATCH-TO-MOVE> $ git checkout PHP-8.0 $ git merge PHP-7.4 $ git checkout PHP-8.1 $ git merge PHP-8.0 $ git checkout master $ git merge PHP-8.1 $ git push TL;DR : Always try to merge PHP-7.4 into PHP-8.0, then PHP-8.1, and then into master. Merge patches received per mail If patches are created with “git format-patch”, you can easily apply them with git's am command: $ git am 000* Normal diff-patches can be applied with git apply: $ git apply <patchfile> Updating NEWS If a patch is related to a bug ticket or is worth it a mention otherwise, the NEWS file needs to be updated to reflect the change done. More info is available in CONTRIBUTING.md . When merging upwards, you can either commit the NEWS entry separately, or as part of the merge commit. To do that, merge using git merge PHP-8.2 --no-commit , add the NEWS entry, add it to the staging area, and git merge --continue . Feature Workflow for Core Developers Feature development can take a lot of time. You might not know to which branch the feature will be committed or you want to combine commits before pushing the final bits. Therefore it is advised to use a separate branch while you develop your feature. This approach is called a feature branch: The workflows aim for a feature to be included into the master branch. So we branch of the master branch first: $ git checkout -b feature/featurename master .. hack hack hack ... $ git commit Update your branch regularly so it's up to date: $ git checkout feature/featurename $ git rebase master Once the feature is accepted, make sure your branch is up to date (see above) and then fast-forward merge it into master: $ git checkout master $ git merge --ff-only feature/featurename Workflow for external contributors The standard workflow for external contributors: Fork the php-src to your own github account. Setup your issue branch on your development system: $ git clone git@github.com:<account>/php-src.git php $ cd php $ git remote add upstream https://github.com/php/php-src.git $ git fetch upstream $ git branch --track issue-<issuenr> origin/PHP-7.4 (or use origin/master) $ git checkout issue-<issuenr> Do your stuff and add/commit your work accordingly. Optionally, you can rebase your work: $ git pull --rebase upstream PHP-7.4 (or use upstream master) Push your branch to your github repository: $ git push origin issue-<issuenr> Before you send in your pull request: Make sure you have proper (and passing) tests for the change. Make sure the pull request message contains a good and precise description what was changed and why. We accept patches in several ways. We prefer getting pull requests from github: Go to your own github PHP repository, select your branch and click the “pull request” button. Now you can create a pull request on your github account to the upstream branch (the same version as you branched). Add a descriptive pull request message. All pull request notifications are sent to the git-pulls@lists.php.net mailinglist. Wait for comments. If you prefer mail use git format-patch and send the created patch using mail: $ git format-patch origin/PHP-7.4 0001-bug-fix.patch ... 0005-another-commit.patch These patches can be attached to a bug or emailed, e.g. to internals@lists.php.net If you don't have an issue-number, just make the branch name self-descriptive (ie: “json_encoding_fix” instead of “branch-001”). As stated before, branch from the lowest version possible. When you want to create a patch that needs to be incorporated into several branches, like a security fix for something in PHP-7.4, PHP-8.0, PHP-8.1, and the master, make sure you checkout a branch from PHP-7.4. You don't need to create separate pull requests for PHP-7.4, PHP-8.0, PHP-8.1, and master. New Commit Message Format We propose the following commit message format for PHP: <max 79 characters short description>\n \n <long description, 79 chars per line> \n An Example from the git project (commit 2b34e486bc): pack-objects: Fix compilation with NO_PTHREDS It looks like commit 99fb6e04 (pack-objects: convert to use parse_options(), 2012-02-01) moved the #ifdef NO_PTHREDS around but hasn't noticed that the 'arg' variable no longer is available. Git commands like log, shortlog, etc support this format and make use of the short description. Please stick to the format. vcs/gitworkflow.txt · Last modified: 2025/08/06 10:03 by derick Page Tools Show pagesource Old revisions Backlinks Back to top Table of Contents Git Workflow Bugfix Workflow for Core Developers Initial Setup Patching a release branch Reviewing and closing pull requests Merge a pull request Merge patches received per mail Updating NEWS Feature Workflow for Core Developers Workflow for external contributors New Commit Message Format Copyright © 2001-2026 The PHP Group Other PHP.net sites Privacy policy | 2026-01-13T09:30:35 |
http://www.videolan.org/vlc/releases/3.0.12-update.html | VLC 3.0.12 and 3.0.13 auto updater issues - VideoLAN * { behavior: url("/style/box-sizing.htc"); } Toggle navigation VideoLAN Team & Organization Consulting Services & Partners Events Legal Press center Contact us VLC Download Features Customize Get Goodies Projects DVBlast x264 x262 x265 multicat dav1d VLC Skin Editor VLC media player libVLC libdvdcss libdvdnav libdvdread libbluray libdvbpsi libaacs libdvbcsa biTStream vlc-unity All Projects Contribute Getting started Donate Report a bug Support donate donate Donate donate donate VideoLAN, a project and a non-profit organization. ENGLISH | DEUTSCH | FRANÇAIS | हिंदी | ITALIANO | 日本語 | PORTUGUÊS | РУССКИЙ VLC 3.0.12 and 3.0.13 automatic updater issue A bug in the auto updater will prevent Windows users to automatically update This is only relevant to Windows users Short version: - versions 3.0.12 to 3.0.13 are not able to update automatically anymore, and will require user action - versions 3.0.11 and earlier should update automatically to 3.0.14 Description: This notice applies to VLC 3.0.13 and VLC 3.0.12 users. Due to a mistake introduced in the automatic updater code, updates will be downloaded, verified for integrity, but will not be installed. This is bad and we would like to apologize for this. Instructions: In order to update to 3.0.14, you will need to go to https://www.videolan.org/vlc to download and install VLC manually. You can find details instructions on how to do so here If you already ran the updater and it downloaded the installer, you can run it manually by opening a file explorer (Windows key + E, or just click the explorer icon) and enter %TEMP% as the location. You'll see the installer there. It will be named «vlc-3.0.14-win32.exe» or «vlc-3.0.14-win64.exe» respectively depending on whether you're using a 32bit or 64bit version of Windows. Post mortem explanation: On May 10 th 2021, the VideoLAN organization released VLC 3.0.13, and enabled auto updates. This usually would be fairly straightforward, a prompt would appear informing you that an update is available, you click download and install, and that would be the end of it. However and unfortunately, for this particular update, a few additional tedious (if not painful) steps will be necessary. The issue was introduced in 3.0.12, but it didn't become obvious until we started rolling out 3.0.13. While the issue was fixed for 3.0.14, we can't rely on that fix for people who've installed 3.0.12 already. The commit that introduced the bug The commit that fixed the bug for future releases Download Updated VLC VLC for Windows Version 3.0.16 Related links Changelog Contact For any questions related to this release, please contact us . VLC media player VLC VLC for Windows VLC for Mac OS X VLC for Ubuntu VLC for Android VLC for iOS Skins Extensions Features Screenshots VLC Skin Editor All Projects VideoLan Movie Creator DVBlast x264 x262 x265 multicat dav1d VLMa libVLC libdvdcss libdvdnav libdvdread libbluray libdvbpsi libaacs libdvbcsa biTStream vlc-unity Community Wiki Forums Mailing-Lists FAQ Donate money Donate time Get Goodies VideoLAN Project and Organization Team Legal Contact us Partners Mirrors Press center Events Security center Get Involved News Legal | Report Trademark Abuse VideoLAN, VLC, VLC media player and x264 are trademarks internationally registered by the VideoLAN non-profit organization. VideoLAN software is licensed under various open-source licenses: use and distribution are defined by each software license. Design by Made By Argon . Some icons are licensed under the CC BY-SA 3.0+ . The VLC cone icon was designed by Richard Øiestad. Icons for VLMC, DVBlast and x264 designed by Roman Khramov . | 2026-01-13T09:30:35 |
https://aws.amazon.com/th/waf/ | ไฟร์วอลสำหรับแอปพลิเคชันบนเว็บ - การป้องกันเว็บ API - AWS WAF - AWS ข้ามไปที่เนื้อหาหลัก Filter: ทั้งหมด English ติดต่อเรา AWS Marketplace การสนับสนุน บัญชีของฉัน การค้นหา Filter: ทั้งหมด ลงชื่อเข้าใช้คอนโซล สร้างบัญชี AWS Web Application Firewall ภาพรวม ฟีเจอร์ ราคา เริ่มต้นใช้งาน ทรัพยากร เพิ่มเติม ผลิตภัณฑ์ › ความปลอดภัย ข้อมูลระบุตัวตน และการปฏิบัติตามข้อกำหนด › AWS WAF รับคำขอควบคุมบอททั่วไป 10 ล้านรายการต่อเดือนด้วย AWS Free Tier → AWS WAF ปกป้องเว็บแอปพลิเคชันของคุณจากการโจมตีที่พบบ่อย เริ่มต้นใช้งาน AWS WAF ประโยชน์ของ AWS WAF ประหยัดเวลาด้วยกฎที่มีการจัดการ ประหยัดเวลาด้วยการใช้กฎที่มีการจัดการ คุณจึงสามารถใช้เวลาในการสร้างแอปพลิเคชันได้มากขึ้น ติดตาม บล็อก หรือจำกัดอัตราของบอต ตรวจสอบ บล็อก หรือจำกัดอัตราของบอตแบบทั่วไปและมีความแพร่หลาย ลดขั้นตอนการกำหนดค่าความปลอดภัย เร่งการกำหนดค่าความปลอดภัยที่ซับซ้อนด้วยอินเทอร์เฟซแบบรวมซึ่งช่วยลดความซับซ้อนและขั้นตอนการปรับใช้การรักษาความปลอดภัยได้ถึง 80% การมองเห็นแบบรวมศูนย์และดำเนินการได้ อินเทอร์เฟซเดียวที่ครอบคลุมรวมฟังก์ชันการรักษาความปลอดภัยหลักเข้ากับการป้องกันพันธมิตรเฉพาะเพื่อเพิ่มการมองเห็นและการควบคุมด้านความปลอดภัย แนวทางแบบครบวงจรนี้จะเปลี่ยนข้อมูลด้านความปลอดภัยให้กลายเป็นข้อมูลเชิงลึกที่สามารถดำเนินการได้ ขจัดแรงเสียดทานในการปฏิบัติงานและเร่งการตอบสนอง เสริมสร้างสภาวะความปลอดภัย ชุดป้องกันที่กำหนดค่าไว้ล่วงหน้าใช้ประโยชน์จากความเชี่ยวชาญด้านความปลอดภัยของ AWS เพื่อส่งมอบเทมเพลตการป้องกันทันทีสำหรับอุตสาหกรรมและประเภทงานเฉพาะ เช่น API แอปพลิเคชัน PHP และบริการเว็บ เทมเพลตเหล่านี้ได้รับการปรับให้เหมาะสมอย่างต่อเนื่องเพื่อให้มั่นใจถึงความปลอดภัยที่ทันสมัยโดยไม่ต้องใช้ความเชี่ยวชาญในการปรับใช้ที่ลึกซึ้ง รับคำแนะนำด้านความปลอดภัยอย่างต่อเนื่องเพื่อเสริมสร้างท่าทางความปลอดภัยโดยรวม ทำไมต้องใช้ AWS WAF AWS WAF มอบการควบคุมจำนวนการเข้าใช้แอปพลิเคชันของคุณโดยให้คุณสร้างกฎการรักษาความปลอดภัยที่ควบคุมการเข้าใช้งานโดยบอตและบล็อกรูปแบบการโจมตีทั่วไป เช่น การ SQL Injection หรือ Cross-Site Scriping (XSS) เล่น กรณีการใช้งาน กรองการใช้งานเว็บ สร้างกฏเพื่อสำหรับกรองคำขอบนเว็บอิงตามเงื่อนไข เช่น ที่อยู่ IP ส่วนหัวและส่วนเนื้อหา HTTP, หรือ URI ที่ปรับแต่ง เรียนรู้เพิ่มเติมเกี่ยวกับการสร้างกฎ ป้องกันการฉ้อโกงขโมยบัญชี ตรวจสอบหน้าจอล็อกอินของแอปพลิเคชันของคุณเพื่อหาการเข้าถึงบัญชีผู้ใช้ที่ไม่ได้รับอนุญาตโดยใช้ข้อมูลประจำตัวที่โดนโจมตี เรียนรู้เพิ่มเติมเกี่ยวกับการป้องกันการฉ้อโกง การป้องกัน DDoS เลเยอร์ 7 อัตโนมัติ ออกแบบมาเพื่อตรวจสอบอย่างต่อเนื่องและลดเหตุการณ์การปฏิเสธการให้บริการแบบกระจาย (DDoS) ของเลเยอร์แอปพลิเคชัน (เลเยอร์ 7) โดยอัตโนมัติภายในไม่กี่วินาที การดำเนินการรักษาความปลอดภัยอย่างรวดเร็ว เปิดตัวแอพพลิเคชั่นใหม่ด้วยความมั่นใจโดยใช้การตั้งค่าการเชื่อมต่อแบบมีแนวทางที่คล่องตัวพร้อมอินเทอร์เฟซหน้าเดียวเพื่อเปิดใช้งานค่าเริ่มต้นด้านความปลอดภัยที่กำหนดไว้ล่วงหน้าซึ่งปรับให้เหมาะกับความต้องการของคุณ เสริมสร้างสภาวะความปลอดภัย ด้วยชุดกฎที่คัดสรรโดยผู้เชี่ยวชาญ การมองเห็นแบบรวม และคำแนะนำอย่างต่อเนื่อง คุณจะได้รับการปกป้องทันทีเพื่อเพิ่มประสิทธิภาพท่าทางด้านความปลอดภัยของคุณ เริ่มต้นใช้งาน AWS WAF เริ่มต้นใช้งาน AWS WAF สำรวจ AWS WAF ติดต่อผู้เชี่ยวชาญ ติดต่อเรา สร้างบัญชี AWS เรียนรู้ AWS คืออะไร การประมวลผลบนคลาวด์คืออะไร Agentic AI คืออะไร ฮับแนวคิดการประมวลผลบนคลาวด์ AWS Cloud Security มีอะไรใหม่ บล็อก ข่าวประชาสัมพันธ์ ทรัพยากร เริ่มต้นใช้งาน การฝึกอบรม AWS Trust Center ไลบราลีโซลูชันของ AWS Architecture Center คำถามที่พบบ่อยเกี่ยวกับผลิตภัณฑ์และเทคนิค รายงานการวิเคราะห์ พาร์ทเนอร์ AWS นักพัฒนา Builder Center SDK และเครื่องมือ .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. หรือบริษัทในเครือ สงวนลิขสิทธิ์ | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudFront/latest/DeveloperGuide/kvs-with-functions-kvp.html | Utilisation de données clé-valeur - Amazon CloudFront Utilisation de données clé-valeur - Amazon CloudFront Documentation Amazon CloudFront Guide du développeur Utilisation de paires clé-valeur (console) À propos de CloudFront KeyValueStore Utilisation des paires clé-valeur (AWS CLI) Utilisation des paires clé-valeur (API) 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. Utilisation de données clé-valeur Cette rubrique décrit comment ajouter des paires clé-valeur à un magasin de clés-valeurs existant. Pour inclure des paires clé-valeur lorsque vous créez initialement le magasin de clés-valeurs, consultez Création d’un magasin de clés-valeurs . Rubriques Utilisation de paires clé-valeur (console) À propos de CloudFront KeyValueStore Utilisation des paires clé-valeur (AWS CLI) Utilisation des paires clé-valeur (API) Utilisation de paires clé-valeur (console) Vous pouvez utiliser la console CloudFront pour gérer vos paires clé-valeur. Pour utiliser les paires clé-valeur Connectez-vous à la AWS Management Console et ouvrez la page Fonctions dans la console CloudFront à l’adresse https://console.aws.amazon.com/cloudfront/v4/home#/functions . Choisissez l’onglet Magasins de clés-valeurs . Sélectionnez le magasin de clés-valeurs que vous souhaitez modifier. Dans la section Paires clé-valeur , choisissez Modifier . Vous pouvez ajouter une paire clé-valeur, supprimer une paire clé-valeur ou modifier la valeur d’une paire clé-valeur existante. Lorsque vous avez terminé, sélectionnez Enregistrer les modifications . À propos de CloudFront KeyValueStore Astuce L’API CloudFront KeyValueStore est un service mondial qui utilise Signature Version 4A (SigV4A) pour l’authentification. L’utilisation d’informations d’identification temporaires avec SigV4A nécessite des jetons de session de version 2. Pour plus d’informations, consultez Utilisation des informations d’identification temporaires avec l’API CloudFront KeyValueStore . Si vous utilisez l’AWS Command Line Interface (AWS CLI) ou votre propre code pour appeler l’API CloudFront KeyValueStore, consultez les sections suivantes. Lorsque vous utilisez un magasin de clés-valeurs et ses paires clé-valeur, le service que vous appelez dépend de votre cas d’utilisation : Pour utiliser des paires clé-valeur par programmation dans un magasin de clés-valeurs existant , utilisez le service CloudFront KeyValueStore. Pour inclure certaines paires clé-valeur dans le magasin de clés-valeurs lorsque vous créez initialement le magasin de clés-valeurs, utilisez le service CloudFront. L’API CloudFront et l’API CloudFront KeyValueStore disposent toutes deux d’une opération DescribeKeyValueStore . Vous les appelez pour différentes raisons. Pour comprendre les différences, consultez le tableau suivant. API CloudFront DescribeKeyValueStore API CloudFront KeyValueStore DescribeKeyValueStore Données relatives au magasin de clés-valeurs Renvoie des données, telles que l’état et la date à laquelle le magasin de clés-valeurs lui-même a été modifié pour la dernière fois. Renvoie les données relatives au contenu de la ressource de stockage : les paires clé-valeur figurant dans le magasin et la taille du contenu. Données qui identifient le magasin de clés-valeurs Renvoie un ETag , l’UUID et l’ARN du magasin de clés-valeurs. Renvoie un ETag et l’ARN du magasin de clés-valeurs. Remarques Chaque opération DescribeKeyValueStore renvoie un ETag différent . Les ETags ne sont pas interchangeables. Lorsque vous appelez une opération d’API pour effectuer une action, vous devez spécifier l’ ETag provenant de l’API appropriée. Par exemple, dans l’opération de suppression CloudFront KeyValueStore DeleteKey , indiquez l’ ETag que vous avez obtenu dans l’opération CloudFront KeyValueStore DescribeKeyValueStore . Lorsque vous invoquez vos fonctions CloudFront à l’aide de CloudFront KeyValueStore, les valeurs du magasin de clés-valeurs ne sont ni mises à jour ni modifiées lors de l’invocation de la fonction. Les mises à jour sont traitées entre deux invocations d’une fonction. Utilisation des paires clé-valeur (AWS CLI) Vous pouvez exécuter les commandes de l’AWS Command Line Interface suivantes pour CloudFront KeyValueStore. Table des matières Liste des paires clé-valeur Obtention des paires clé-valeur Description d’un magasin de clés-valeurs Création d’une paire clé-valeur Suppression d’une paire clé-valeur Mise à jour d’une paire clé-valeur Liste des paires clé-valeur Pour répertorier les paires clé-valeur dans votre magasin de clés-valeurs, exécutez la commande suivante. aws cloudfront-keyvaluestore list-keys \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Réponse { "Items": [ { "Key": "key1", "Value": "value1" } ] } Obtention des paires clé-valeur Pour obtenir les paires clé-valeur dans votre magasin de clés-valeurs, exécutez la commande suivante. aws cloudfront-keyvaluestore get-key \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Réponse { "Key": "key1", "Value": "value1", "ItemCount": 1, "TotalSizeInBytes": 11 } Description d’un magasin de clés-valeurs Pour décrire un magasin de clés-valeurs, exécutez la commande suivante. aws cloudfront-keyvaluestore describe-key-value-store \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Réponse { "ETag": "KV1F83G8C2ARO7P", "ItemCount": 1, "TotalSizeInBytes": 11, "KvsARN": "arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example", "Created": "2024-05-08T07:48:45.381000-07:00", "LastModified": "2024-08-05T13:50:58.843000-07:00", "Status": "READY" } Création d’une paire clé-valeur Pour créer une paire clé-valeur dans votre magasin de clés-valeurs, exécutez la commande suivante. aws cloudfront-keyvaluestore put-key \ --if-match=KV1PA6795UKMFR9 \ --key=key2 \ --value=value2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Réponse { "ETag": "KV13V1IB3VIYZZH", "ItemCount": 3, "TotalSizeInBytes": 31 } Suppression d’une paire clé-valeur Pour supprimer une paire clé-valeur, exécutez la commande suivante. aws cloudfront-keyvaluestore delete-key \ --if-match=KV13V1IB3VIYZZH \ --key=key1 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example Sortie { "ETag": "KV1VC38T7YXB528", "ItemCount": 2, "TotalSizeInBytes": 22 } Mise à jour d’une paire clé-valeur Vous pouvez utiliser la commande update-keys pour mettre à jour plusieurs paires clé-valeur. Par exemple, pour supprimer une paire clé-valeur existante et en créer une autre, exécutez la commande suivante. aws cloudfront-keyvaluestore update-keys \ --if-match=KV2EUQ1WTGCTBG2 \ --kvs-arn=arn:aws:cloudfront::123456789012:key-value-store/37435e19-c205-4271-9e5c-example \ --deletes '[ { "Key":"key2"}]' \ --puts '[ { "Key":"key3","Value":"value3"}]' Réponse { "ETag": "KV3AEGXETSR30VB", "ItemCount": 3, "TotalSizeInBytes": 28 } Utilisation des paires clé-valeur (API) Suivez cette section pour utiliser vos paires clé-valeur par programmation. Table des matières Obtention d’une référence à un magasin de clés-valeurs Modification de paires clé-valeur dans un magasin de clés-valeurs Exemple de code pour CloudFront KeyValueStore Obtention d’une référence à un magasin de clés-valeurs Lorsque vous utilisez l’API CloudFront KeyValueStore pour appeler une opération d’écriture, vous devez spécifier l’ARN et l’ ETag du magasin de clés-valeurs. Pour obtenir ces données, procédez comme suit : Pour obtenir une référence à un magasin de clés-valeurs Utilisez l’opération d’API CloudFront ListKeyValueStores pour obtenir une liste de magasins de clés-valeurs. Recherchez le magasin de clés-valeurs que vous souhaitez modifier. Utilisez l’ opération d’API CloudFrontKeyValueStore DescribeKeyValueStore et indiquez le magasin de clés-valeurs identifié à l’étape précédente. La réponse inclut l’ARN et l’ ETag du magasin de clés-valeurs. L’ARN inclut le numéro de Compte AWS, la constante key-value-store et l’UUID, comme dans l’exemple suivant : arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 Un ETag ressemble à l’exemple suivant : ETVABCEXAMPLE2 Modification de paires clé-valeur dans un magasin de clés-valeurs Vous pouvez spécifier le magasin de clés-valeurs qui contient la paire clé-valeur que vous souhaitez mettre à jour. Consultez les opérations d’API CloudFront KeyValueStore suivantes : CloudFrontKeyValueStore DeleteKey : supprime une paire clé-valeur CloudFrontKeyValueStore GetKey : renvoie une paire clé-valeur CloudFrontKeyValueStore ListKeys : renvoie une liste de paire clé-valeur CloudFrontKeyValueStore PutKey : vous pouvez effectuer les tâches suivantes : Créer une paire clé-valeur dans un magasin de clés-valeurs en indiquant un nouveau nom de clé et une valeur. Définir une valeur différente dans une paire clé-valeur existante en spécifiant un nom de clé existant et une nouvelle valeur. CloudFrontKeyValueStore UpdateKeys : vous pouvez effectuer une ou plusieurs des actions suivantes en une seule opération « tout ou rien » : Supprimer une ou plusieurs paires clé-valeur Créer une ou plusieurs nouvelles paires clé-valeur Définir une valeur différente dans une ou plusieurs paires clé-valeur existantes Exemple de code pour CloudFront KeyValueStore Le code suivant vous montre comment appeler l’opération d’API DescribeKeyValueStore pour un magasin de clés-valeurs. const { CloudFrontKeyValueStoreClient, DescribeKeyValueStoreCommand, } = require("@aws-sdk/client-cloudfront-keyvaluestore"); require("@aws-sdk/signature-v4-crt"); (async () => { try { const client = new CloudFrontKeyValueStoreClient( { region: "us-east-1" }); const input = { KvsARN: "arn:aws:cloudfront::123456789012:key-value-store/a1b2c3d4-5678-90ab-cdef-EXAMPLE11111", }; const command = new DescribeKeyValueStoreCommand(input); const response = await client.send(command); } catch (e) { console.log(e); } })(); 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 Format de fichier pour les paires clé-valeur Personnalisez avec les fonctions CloudFront de connexion 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:35 |
https://wiki.php.net/vcs/gitworkflow?do=resendpwd | PHP: Set new password Login Register You are here: start › vcs › gitworkflow vcs:gitworkflow Set new password Please enter a new password for your account in this wiki. You can only do this for wiki accounts. If you have a php.net VSC account, then you need to reset your password on main.php.net . Set new password Username Set new password vcs/gitworkflow.txt · Last modified: 2025/08/06 10:03 by derick Page Tools Show page Old revisions Backlinks Back to top Copyright © 2001-2026 The PHP Group Other PHP.net sites Privacy policy | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/zh_tw/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Lambda@Edge 範例函數 - Amazon CloudFront Lambda@Edge 範例函數 - Amazon CloudFront 文件 Amazon CloudFront 開發人員指南 一般範例 產生回應：範例 查詢字串：範例 根據國家/地區或裝置類型標頭個人化 - 範例 以內容為基礎的動態原始伺服器選擇 - 範例 更新錯誤狀態：範例 存取請求本文：範例 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 Lambda@Edge 範例函數 請參閱下列透過 Amazon CloudFront 使用 Lambda 函數的範例。 注意 如果您為 Lambda@Edge 函數選擇執行時期 Node.js 18 或更新版本，系統會自動為您建立 index.mjs 檔案。若要使用下列程式碼範例，請將 index.mjs 檔案重新命名為 index.js 。 主題 一般範例 產生回應：範例 查詢字串：範例 根據國家/地區或裝置類型標頭個人化 - 範例 以內容為基礎的動態原始伺服器選擇 - 範例 更新錯誤狀態：範例 存取請求本文：範例 一般範例 下列範例顯示在 CloudFront 中使用 Lambda@Edge 的常見方法。 主題 範例：A/B 測試 範例：覆寫回應標頭 範例：A/B 測試 您可以使用下列範例測試兩種不同版本的影像，而不需要建立重新導向或變更 URL。此範例會讀取檢視器請求中的 Cookie，並據此修改請求 URL。如果檢視器未傳送具有其中一個預期值的 Cookie，此範例會將檢視器隨機指派給其中一個 URL。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request 範例：覆寫回應標頭 以下範例說明如何根據另一個標頭的值變更回應標頭的值。 Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response 產生回應：範例 以下範例示範如何使用 Lambda@Edge 來產生回應。 主題 範例：提供靜態內容 (產生回應) 範例：產生 HTTP 重新導向 (產生回應) 範例：提供靜態內容 (產生回應) 以下範例說明如何使用 Lambda 函數提供靜態網站內容，其可減少原始伺服器的負載，並降低整體延遲。 注意 您可以針對檢視器要求及原始伺服器請求事件產生 HTTP 回應。如需詳細資訊，請參閱 在請求觸發條件中產生 HTTP 回應 。 您也可以在原始伺服器回應請求事件中取代或移除 HTTP 回應的主體。如需詳細資訊，請參閱 在原始伺服器回應觸發條件中更新 HTTP 回應 。 Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response 範例：產生 HTTP 重新導向 (產生回應) 以下範例說明如何產生 HTTP 重新導向。 注意 您可以針對檢視器要求及原始伺服器請求事件產生 HTTP 回應。如需詳細資訊，請參閱 在請求觸發條件中產生 HTTP 回應 。 Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response 查詢字串：範例 以下範例示範以查詢字串使用 Lambda@Edge 的方式。 主題 範例：根據查詢字串參數新增標頭 範例：標準化查詢字串參數，以提升快取點擊率 範例：重新導向未驗證使用者到登入頁面 範例：根據查詢字串參數新增標頭 以下範例說明如何取得查詢字串參數的鍵值對，然後根據這些值新增標頭。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request 範例：標準化查詢字串參數，以提升快取點擊率 以下範例說明如何在 CloudFront 轉送請求至您的原始伺服器之前，做以下變更至查詢字串以提高您的快取點擊率： 依字母排序鍵值組的參數名稱。 將鍵值組變更為小寫。 如需詳細資訊，請參閱 根據查詢字串參數快取內容 。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request 範例：重新導向未驗證使用者到登入頁面 以下範例說明，如果尚未輸入他們的登入資料，如何將使用者重新導向至登入頁面。 Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response 根據國家/地區或裝置類型標頭個人化 - 範例 以下範例說明如何使用 Lambda@Edge 來根據位置或檢視器使用的裝置類型自訂行為。 主題 範例：將檢視器請求重新導向到國家/地區特定的 URL 範例：根據裝置提供不同的物件版本 範例：將檢視器請求重新導向到國家/地區特定的 URL 以下範例說明如何產生含國家/地區特定 URL 的 HTTP 重新導向回應，並將回應傳回至檢視器。當您希望提供特定國家的回應時，此方法很有用。例如： 如果您有國家/地區特定的子網域 (例如 us.example.com 和 tw.example.com)，當檢視器請求 example.com 時，您可以產生一個重新導向回應。 如果您在串流視訊，但沒有在特定國家/地區串流此內容的權利，您可以在該國家/地區將使用者重新導向到說明他們為何無法檢視影片的頁面。 注意下列事項： 您必須根據 CloudFront-Viewer-Country 標頭設定您的分佈為快取。如需詳細資訊，請參閱 根據選取請求標頭的快取 。 在檢視器請求事件後，CloudFront 新增 CloudFront-Viewer-Country 標頭。要使用此範例，您必須建立原始伺服器請求事件的觸發。 Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response 範例：根據裝置提供不同的物件版本 以下範例說明如何根據使用者使用的裝置類型，提供不同的物件版本，例如行動裝置或平板電腦。注意下列事項： 您必須根據 CloudFront-Is-*-Viewer 標頭設定您的分佈為快取。如需詳細資訊，請參閱 根據選取請求標頭的快取 。 在檢視器請求事件後，CloudFront 新增 CloudFront-Is-*-Viewer 標頭。要使用此範例，您必須建立原始伺服器請求事件的觸發。 Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request 以內容為基礎的動態原始伺服器選擇 - 範例 以下範例示範如何使用 Lambda@Edge 來根據請求中的資訊路由到不同的原始伺服器。 主題 範例：使用原始伺服器請求觸發條件，以從自訂原始伺服器變更到 Amazon S3 原始伺服器 範例：使用原始伺服器請求觸發條件，以變更 Amazon S3 原始伺服器區域 範例：使用原始伺服器請求觸發條件，變更 Amazon S3 原始伺服器為自訂原始伺服器 範例：使用原始伺服器請求觸發條件，將流量自一個 Amazon S3 儲存貯體逐漸傳輸到另一個。 範例：使用原始伺服器請求觸發，根據國家/地區標頭變更原始網域名稱 範例：使用原始伺服器請求觸發條件，以從自訂原始伺服器變更到 Amazon S3 原始伺服器 此函數示範如何使用 origin-request 觸發條件，根據請求屬性從自訂原始伺服器變更至內容被擷取的 Amazon S3 原始伺服器。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request 範例：使用原始伺服器請求觸發條件，以變更 Amazon S3 原始伺服器區域 此函數示範如何根據請求屬性，使用 origin-request 觸發條件來變更內容被擷取的 Amazon S3 原始伺服器。 在這個範例中，我們使用 CloudFront-Viewer-Country 標頭的值來將 S3 儲存貯體的網域名稱更新為較靠近檢視器的區域內的儲存貯體。這在數種方式中非常受用： 當指定的區域更靠近檢視器的國家/地區時，能減少延遲。 藉由確保該資料與請求來自位於相同國家/地區的原始伺服器，提供資料主權服務。 要使用此範例，須執行下列項目： 您必須根據 CloudFront-Viewer-Country 標頭設定您的分佈為快取。如需詳細資訊，請參閱 根據選取請求標頭的快取 。 在原始伺服器請求事件中建立此函數的觸發。CloudFront 將在檢視者請求事件後新增 CloudFront-Viewer-Country 標頭，所以若要使用此範例，必須確認函數會執行原始請求。 注意 下列範例程式碼針對您用於原始伺服器的所有 S3 儲存貯體使用相同的原始存取身分 (OAI)。如需更多詳細資訊，請參閱 原始存取身分 。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 範例：使用原始伺服器請求觸發條件，變更 Amazon S3 原始伺服器為自訂原始伺服器 此函數示範如何根據請求屬性，使用原始伺服器請求觸發來變更內容被擷取的自訂原始伺服器。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request 範例：使用原始伺服器請求觸發條件，將流量自一個 Amazon S3 儲存貯體逐漸傳輸到另一個。 此函數示範如何以可控的方式，從一個 Amazon S3 儲存貯體逐步傳輸流量到另一個儲存貯體。 Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 範例：使用原始伺服器請求觸發，根據國家/地區標頭變更原始網域名稱 此函數示範如何根據 CloudFront-Viewer-Country 標頭來變更原始伺服器的網域名稱，使內容能從靠近檢視者國家/地區的原始伺服器提供。 為您的分佈實施此功能可以擁有如下所述的優勢： 當指定的區域更靠近檢視器的國家/地區時，可減少延遲 藉由確保該資料與請求來自位於相同國家/地區的原始伺服器來提供資料主權服務 請注意，要啟用此功能，您必須根據 CloudFront-Viewer-Country 標頭設定您的分佈為快取。如需詳細資訊，請參閱 根據選取請求標頭的快取 。 Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request 更新錯誤狀態：範例 以下範例提供指導，說明如何使用 Lambda@Edge 來變更傳回給使用者的錯誤狀態。 主題 範例：使用原始伺服器請求觸發以更新錯誤狀態碼為 200 範例：使用原始伺服器請求觸發以更新錯誤狀態碼為 302 範例：使用原始伺服器請求觸發以更新錯誤狀態碼為 200 此函數示範如何更新回應狀態為 200 並產生靜態本文內容，以在以下案例傳回給檢視器： 函數在原始伺服器回應中觸發。 原始伺服器的回應狀態為錯誤狀態碼 (4xx 和 5xx) Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response 範例：使用原始伺服器請求觸發以更新錯誤狀態碼為 302 此函數示範如何更新 HTTP 狀態碼為 302，以重新導向到另一個由不同原始伺服器設定的路徑 (快取行為)。注意下列事項： 函數在原始伺服器回應中觸發。 原始伺服器的回應狀態為錯誤狀態碼 (4xx 和 5xx) Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response 存取請求本文：範例 以下範例說明如何使用 Lambda@Edge 來處理 POST 請求。 注意 若要使用這些範例，您必須在分佈的 Lambda 函數關聯中啟用 包含內文 選項。依預設不會啟用此功能。 若要在 CloudFront 主控台中啟用此設定，請選取 Lambda 函數關聯 中 包含內文 的核取方塊。 若要在 CloudFront API 中或使用 啟用此設定 CloudFormation，請在 true 中將 IncludeBody 欄位設定為 LambdaFunctionAssociation 。 主題 範例：使用請求觸發條件來讀取 HTML 表單 範例：使用請求觸發條件來修改 HTML 表單 範例：使用請求觸發條件來讀取 HTML 表單 此函數示範如何處理 HTML 表單 (Web 表單) 所產生 POST 請求的主體，例如「聯絡我們」表單。例如，您可能會有如下的 HTML 表單： <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> 至於後面的範例函數，該函數必須在 CloudFront 檢視器請求或原始伺服器請求中觸發。 Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request 範例：使用請求觸發條件來修改 HTML 表單 此函數示範如何修改 HTML 表單 (Web 表單) 所產生 POST 請求的主體。此函數會在 CloudFront 檢視器請求或原始伺服器請求中觸發。 Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action to 'replace' 2) body.encoding to the encoding of the new data. Set to one of the following values: text - denotes that the generated body is in text format. Lambda@Edge will propagate this as is. base64 - denotes that the generated body is base64 encoded. Lambda@Edge will base64 decode the data before sending it to the origin. 3) body.data to the new body. ''' request['body']['action'] = 'replace' request['body']['encoding'] = 'text' request['body']['data'] = getUpdatedBody(request) return request def getUpdatedBody(request): # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} # For demonstration purposes, we're adding one more param # You can put your custom logic here. For example, you can truncate long # bodies from malicious requests params['new-param-name'] = 'new-param-value' return urlencode(params) 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 使用請求和回應 對邊緣函數的限制 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:30:35 |
https://penneo.com/da/blog/ | Vidensunivers - 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Å VIDENSUNIVERS Alt, hvad du har brug for at vide om digital tillid Her får du guides, knivskarp juridisk viden og perspektiver fra vores eksperter. Du kan også se hvordan andre virksomheder bruger Penneo Sign til at gøre hverdagen lettere mens juraen overholdes. Nyt fra Penneo Hemmeligheden bag en stærk revision: Skab værdi, undgå manuelt besvær Læs mere Produktopdateringer fra Q4 2025: Hurtigere afsendelse, global QES & API-opdateringer Læs mere Penneo QES: Højeste juridiske gyldighed og dokumenteret sikkerhed Læs mere Filtrér efter indholdstype ↓ Blogindlæg Guides og e-bøger Referencer Produktopdateringer Alle Digital transformation Digitale tillidstjenester Signaturer og juridisk gyldighed Sikkerhed og overholdelse Vækst og forretning Send dokumenter til underskrift på få sekunder med Penneo Sign Læs mere Penneo i opråb – Med svindleres brug af AI har vi akut brug for bedre beskyttelse Læs mere Hvad er nyt i Penneo Sign? Produktopdateringer fra Q2 2025 Læs mere Vi introducerer Penneos nye analysepanel: Forbrugsoversigt Læs mere Hvad hvis din kunde siger ‘Det er ikke min underskrift’? Læs mere Sådan gør du din revisionsproces fuldt integreret med Penneo og Caseware Læs mere Q1 2025 Penneo Sign Opdateringer Læs mere Har du brug for at indsamle underskrifter fra internationale interessenter? Penneo Sign gør det nu nemmere Læs mere Hvad er nyt i Penneo Sign? Produktopdateringer fra H2 2024 Læs mere SE FLERE ARTIKLER 4.700 i erhvervslivet læser allerede vores nyhedsbrev - hvad med dig? Når du tilmelder dig vores e-mail nyhedsbrev holder vi dig opdateret på alt det nyeste inden for digitale underskrifter. Du får også et klart overblik over, hvad nye regler betyder i praksis for dig og din virksomhed. Vi sender dig nøje udvalgt indhold, så du nemt kan holde dig et skridt foran. Email Dette felt er til validering og bør ikke ændres. E-mail * * Jeg giver samtykke til at modtage nyheder og opdateringer fra Penneo via e-mail. Indsigter fra vores eksperter Fredrik Lernevall Information Security Manager hos Penneo Læs mere Ksenia Bezukladnikova Product Manager hos Penneo Læs mere Kasper Behrens Strategisk forretningsudvikler Læs mere Nina Vesalainen Seniorjurist hos Penneo Læs mere Tag en snak med os Vil du se, hvordan Penneo Sign fungerer i praksis? Book en kort demo, og så viser vi dig platformen trin for trin, og besvarer dine spørgsmål. Helt uden pres. BOOK ET MØDE Start din gratis prøveperiode i dag Underskriv dine første dokumenter med Penneo Sign på få minutter, og se, hvor nemt det er at komme i gang med digital signering. Vi beder ikke om dine kortoplysninger. GRATIS PRØVEPERIODE 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:35 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Beispielfunktionen für Lambda@Edge - Amazon CloudFront Beispielfunktionen für Lambda@Edge - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch Allgemeine Beispiele Generieren von Antworten – Beispiele Abfragezeichenfolgen – Beispiele Personalisieren von Inhalten nach Land oder Gerätetyp-Header – Beispiele Inhaltsbasierte dynamische Ursprungsauswahl –Beispiele Aktualisieren von Fehlerstatusangaben – Beispiele Zugriff auf den Anforderungstext – Beispiele 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. Beispielfunktionen für Lambda@Edge Sehen Sie sich die folgenden Beispiele für die Verwendung von Lambda-Funktionen mit Amazon CloudFront an. Anmerkung Wenn Sie die Laufzeitumgebung Node.js 18 oder höher für Ihre Lambda@Edge-Funktion auswählen, wird automatisch eine index.mjs -Datei für Sie erstellt. Um die folgenden Codebeispiele zu verwenden, benennen Sie die index.mjs -Datei in index.js um. Themen Allgemeine Beispiele Generieren von Antworten – Beispiele Abfragezeichenfolgen – Beispiele Personalisieren von Inhalten nach Land oder Gerätetyp-Header – Beispiele Inhaltsbasierte dynamische Ursprungsauswahl –Beispiele Aktualisieren von Fehlerstatusangaben – Beispiele Zugriff auf den Anforderungstext – Beispiele Allgemeine Beispiele Die folgenden Beispiele zeigen gängige Verwendungsmöglichkeiten von Lambda @Edge in CloudFront. Themen Beispiel: Testen A/B Beispiel: Überschreiben eines Antwortheaders Beispiel: Testen A/B Sie können das folgende Beispiel verwenden, um zwei verschiedene Versionen eines Images zu testen, ohne Weiterleitungen zu erstellen oder die URL zu ändern. In diesem Beispiel werden die Cookies in der Viewer-Anfrage gelesen und die Anforderungs-URL wird entsprechend geändert. Wenn der Betrachter kein Cookie mit einem der erwarteten Werte sendet, weist das Beispiel den Betrachter nach dem Zufallsprinzip einem der URLs folgenden zu. Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request Beispiel: Überschreiben eines Antwortheaders Das folgende Beispiel zeigt, wie Sie den Wert eines Antwortheaders basierend auf dem Wert eines anderen Headers modifizieren: Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response Generieren von Antworten – Beispiele Die folgenden Beispiele zeigen, wie Sie Lambda@Edge zum Generieren von Antworten verwenden können. Themen Beispiel: Bereitstellen von statischen Inhalten (generierte Antwort) Beispiel: Generieren einer HTTP-Umleitung (generierte Antwort) Beispiel: Bereitstellen von statischen Inhalten (generierte Antwort) Das folgende Beispiel zeigt, wie Sie mit einer Lambda-Funktion Inhalte von statischen Websites bereitstellen können, wodurch sich die Verarbeitungslast auf dem Ursprungs-Server und die Latenz insgesamt verringert. Anmerkung Sie können HTTP-Antworten für Viewer-Anfrage- und Ursprungsanfrageereignisse generieren. Weitere Informationen finden Sie unter Generieren von HTTP-Antworten in Anforderungsauslösern . Sie können auch den Text der HTTP-Antwort in Ursprungsantwortereignissen ersetzen oder entfernen. Weitere Informationen finden Sie unter Aktualisieren von HTTP-Antworten in Ursprungsantwortauslösern . Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response Beispiel: Generieren einer HTTP-Umleitung (generierte Antwort) Das folgende Beispiel zeigt, wie Sie eine HTTP-Umleitung generieren. Anmerkung Sie können HTTP-Antworten für Viewer-Anfrage- und Ursprungsanfrageereignisse generieren. Weitere Informationen finden Sie unter Generieren von HTTP-Antworten in Anforderungsauslösern . Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response Abfragezeichenfolgen – Beispiele Die folgenden Beispiele zeigen Möglichkeiten zur Verwendung von Lambda@Edge mit Abfragezeichenfolgen. Themen Beispiel: Hinzufügen eines Headers auf Grundlage eines Abfragezeichenfolgeparameters Beispiel: Normalisieren von Abfragezeichenfolgeparametern zum Verbessern der Cache-Trefferrate Beispiel: Umleiten von nicht authentifizierten Benutzern auf eine Anmeldeseite Beispiel: Hinzufügen eines Headers auf Grundlage eines Abfragezeichenfolgeparameters Im folgenden Beispiel wird gezeigt, wie Sie das Schlüssel-Wert-Paar eines Abfragezeichenfolgeparameter abrufen und auf Grundlage dieser Werte einen Header hinzufügen können. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request Beispiel: Normalisieren von Abfragezeichenfolgeparametern zum Verbessern der Cache-Trefferrate Das folgende Beispiel zeigt, wie Sie Ihre Cache-Trefferquote verbessern können, indem Sie die folgenden Änderungen an Abfragezeichenfolgen vornehmen, bevor CloudFront Anfragen an Ihren Ursprung weitergeleitet werden: Alphabetisches Anordnen von Schlüssel-Wert-Paaren nach dem Parametername. Ändern der Schreibung von Schlüssel-Wert-Paaren in Kleinschreibung. Weitere Informationen finden Sie unter Zwischenspeichern von Inhalten auf der Grundlage von Abfragezeichenfolgeparametern . Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request Beispiel: Umleiten von nicht authentifizierten Benutzern auf eine Anmeldeseite Im folgenden Beispiel wird gezeigt, wie Benutzer zu einer Anmeldeseite umgeleitet werden, wenn sie ihre Anmeldeinformationen nicht eingegeben haben. Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response Personalisieren von Inhalten nach Land oder Gerätetyp-Header – Beispiele Die folgenden Beispiele zeigen, wie Sie mit Lambda@Edge das Verhalten basierend auf dem Standort oder dem Typ des Geräts anpassen können, das vom jeweiligen Viewer verwendet wird. Themen Beispiel: Umleiten von Viewer-Anforderungen an eine länderspezifische URL Beispiel: Bereitstellen verschiedener Versionen eines Objekts auf Grundlage des Geräts Beispiel: Umleiten von Viewer-Anforderungen an eine länderspezifische URL Im folgenden Beispiel wird gezeigt, wie eine HTTP-Umleitungsantwort mit einer länderspezifischen URL erzeugt und die Antwort an den Viewer zurückgegeben wird. Dies ist nützlich, wenn Sie länderspezifische Antworten bereitstellen möchten. Beispiel: Wenn Sie über länderspezifischen Subdomänen verfügen, z. B. us.example.com und tw.example.com, können Sie eine Umleitungsantwort erzeugen, wenn ein Viewer example.com anfordert. Wenn Sie Videos streamen, aber keine Rechte für das Streamen von Inhalten in einem bestimmten Land besitzen, können Sie Benutzer in diesem Land auf eine Seite umleiten, auf der erklärt wird, warum sie das Video nicht ansehen können. Beachten Sie Folgendes: Sie müssen Ihre Verteilung so konfigurieren, dass die Zwischenspeicherung auf Grundlage des CloudFront-Viewer-Country -Headers erfolgt. Weitere Informationen finden Sie unter Basierend auf den ausgewählten Anforderungsheadern . CloudFront fügt den CloudFront-Viewer-Country Header nach dem Viewer-Anforderungsereignis hinzu. Wenn Sie dieses Beispiel verwenden möchten, müssen Sie einen Auslöser für das ursprüngliche Anfrageereignis erstellen. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response Beispiel: Bereitstellen verschiedener Versionen eines Objekts auf Grundlage des Geräts Das folgende Beispiel zeigt, wie Sie für verschiedene Versionen eines Objekts auf Grundlage des Gerätetyps, den der Benutzer verwendet (z. B. ein mobiles Gerät oder ein Tablet), bereitstellen. Beachten Sie Folgendes: Sie müssen Ihre Verteilung so konfigurieren, dass die Zwischenspeicherung auf Grundlage der CloudFront-Is-*-Viewer -Header erfolgt. Weitere Informationen finden Sie unter Basierend auf den ausgewählten Anforderungsheadern . CloudFront fügt die CloudFront-Is-*-Viewer Header nach dem Viewer-Anforderungsereignis hinzu. Wenn Sie dieses Beispiel verwenden möchten, müssen Sie einen Auslöser für das ursprüngliche Anfrageereignis erstellen. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request Inhaltsbasierte dynamische Ursprungsauswahl –Beispiele Die folgenden Beispiele zeigen, wie Sie Lambda@Edge zur Weiterleitung an verschiedene Ursprünge basierend auf Informationen in der Anforderung verwenden können. Themen Beispiel: Mithilfe eines Ursprungsanforderungsauslösers von einem benutzerdefinierten Ursprung zu einem Amazon-S3-Ursprung wechseln Beispiel: Ändern der Amazon-S3-Ursprungsregion mithilfe eines Ursprungsanforderungsauslösers Beispiel: Mithilfe eines Ursprungsanforderungsauslösers von einem Amazon-S3-Ursprung zu einem benutzerdefinierten Ursprung wechseln Beispiel: Verwenden eines Ursprungsanforderungsauslösers zur schrittweisen Übertragung von Netzwerkverkehr von einem Amazon-S3-Bucket zu einem anderen Beispiel: Verwenden eines Ursprungsanforderungsauslösers zum Ändern des Ursprungsdomainnamens anhand des Landes-Headers Beispiel: Mithilfe eines Ursprungsanforderungsauslösers von einem benutzerdefinierten Ursprung zu einem Amazon-S3-Ursprung wechseln Diese Funktion demonstriert, wie mit Hilfe eines Ursprungsanforderungsauslösers von einem benutzerdefinierten Ursprung zu einem Amazon S3-Ursprung gewechselt werden kann, von dem der Inhalt auf Basis der Anforderungseigenschaften abgerufen wird. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request Beispiel: Ändern der Amazon-S3-Ursprungsregion mithilfe eines Ursprungsanforderungsauslösers Diese Funktion demonstriert, wie mit Hilfe eines Ursprungsanforderungsauslösers von einem Amazon S3-Ursprung gewechselt werden kann, von dem der Inhalt auf Basis der Anforderungseigenschaften abgerufen wird. In diesem Beispiel verwenden wir den Wert des CloudFront-Viewer-Country -Headers zum Aktualisieren des S3-Bucket-Domänennamens auf einen Bucket in einer Region, die sich näher am Viewer befindet. Dies kann auf verschiedene Weise nützlich sein: Es werden Latenzen reduziert, wenn die angegebene Region näher am Land des Viewers liegt. Es sorgt für Datenhoheit, indem es sicherstellt, dass die Daten aus einem Ursprung stammen, der in dem Land liegt, aus dem die Anfrage stammt. In diesem Beispiel gehen Sie wie folgt vor: Konfigurieren Sie Ihre Verteilung so, dass die Zwischenspeicherung auf Grundlage des CloudFront-Viewer-Country -Headers erfolgt. Weitere Informationen finden Sie unter Basierend auf den ausgewählten Anforderungsheadern . Erstellen Sie einen Trigger für diese Funktion im ursprünglichen Anforderungsereignis. CloudFrontfügt den CloudFront-Viewer-Country Header nach dem Viewer-Anforderungsereignis hinzu. Um dieses Beispiel zu verwenden, müssen Sie also sicherstellen, dass die Funktion für eine ursprüngliche Anfrage ausgeführt wird. Anmerkung Der folgende Beispielcode verwendet dieselbe Ursprungszugriffsidentität (OAI) für alle S3-Buckets, die Sie für Ihren Ursprung verwenden. Weitere Informationen finden Sie unter Ursprungszugriffsidentitäten . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Beispiel: Mithilfe eines Ursprungsanforderungsauslösers von einem Amazon-S3-Ursprung zu einem benutzerdefinierten Ursprung wechseln Diese Funktion demonstriert, wie mit Hilfe eines Ursprungsanforderungsauslösers von einem benutzerdefinierten Ursprung gewechselt werden kann, von dem der Inhalt auf Basis der Anforderungseigenschaften abgerufen wird. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request Beispiel: Verwenden eines Ursprungsanforderungsauslösers zur schrittweisen Übertragung von Netzwerkverkehr von einem Amazon-S3-Bucket zu einem anderen Diese Funktion demonstriert, wie Sie schrittweise und kontrolliert den Datenverkehr von einem Amazon-S3-Bucket zu einem anderen übertragen können. Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Beispiel: Verwenden eines Ursprungsanforderungsauslösers zum Ändern des Ursprungsdomainnamens anhand des Landes-Headers Diese Funktion demonstriert, wie Sie den Ursprungsdomänennamen, basierend auf dem CloudFront-Viewer-Country -Header, ändern können, sodass der Inhalt von einem Ursprungsland aus bereitgestellt wird, das näher am Land des Viewers liegt. Die Implementierung dieser Funktionalität für Ihre Verteilung bietet u. a. ggf. folgende Vorteile: Es werden Latenzen reduziert, wenn die angegebene Region näher am Land des Viewers liegt. Es wird für Datenhoheit gesorgt, indem sichergestellt wird, dass die Daten aus einem Ursprung stammen, der in dem Land liegt, aus dem die Anfrage stammt Beachten Sie, dass Sie Ihre Verteilung für die Zwischenspeicherung auf Basis des CloudFront-Viewer-Country -Headers konfigurieren müssen, um diese Funktionalität zu aktivieren. Weitere Informationen finden Sie unter Basierend auf den ausgewählten Anforderungsheadern . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Aktualisieren von Fehlerstatusangaben – Beispiele Die folgenden Beispiele leiten Sie bei der Verwendung von Lambda@Edge zum Ändern des an Benutzer zurückgegebenen Fehlerstatus an. Themen Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 200 aktualisieren Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 302 aktualisieren Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 200 aktualisieren Diese Funktion demonstriert, wie Sie den Antwortstatus auf 200 aktualisieren und statischen Body-Content für die Rückgabe an den Viewer generieren können: Die Funktion wird in einer Ursprungsantwort ausgelöst. Der Antwortstatus vom Ursprungs-Server ist ein Fehlerstatuscode (4xx oder 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response Beispiel: Mithilfe eines Ursprungsantwortauslösers den Fehlerstatuscode auf 302 aktualisieren Diese Funktion demonstriert, wie Sie den HTTP-Statuscode auf 302 aktualisieren können, um ihn auf einen anderen Pfad (Cache-Verhalten) umzuleiten, der einen anderen Ursprung hat. Beachten Sie Folgendes: Die Funktion wird in einer Ursprungsantwort ausgelöst. Der Antwortstatus vom Ursprungs-Server ist ein Fehlerstatuscode (4xx oder 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response Zugriff auf den Anforderungstext – Beispiele Die folgenden Beispiele veranschaulichen, wie Sie Lambda@Edge für die Arbeit mit POST-Anforderungen verwenden können. Anmerkung Um diese Beispiele zu verwenden, müssen Sie die Option Textkörper einschließen in der Lambda-Funktionszuordnung der Verteilung aktivieren. Sie ist standardmäßig nicht aktiviert. Um diese Einstellung in der CloudFront Konsole zu aktivieren, aktivieren Sie das Kontrollkästchen Body in the Lambda Function Association einbeziehen . Um diese Einstellung in der CloudFront API oder mit zu aktivieren CloudFormation, setzen Sie das IncludeBody Feld auf true in LambdaFunctionAssociation . Themen Beispiel: Verwenden eines Anforderungsauslösers zum Lesen eines HTML-Formulars Beispiel: Verwenden eines Anforderungsauslösers zum Bearbeiten eines HTML-Formulars Beispiel: Verwenden eines Anforderungsauslösers zum Lesen eines HTML-Formulars Diese Funktion zeigt, wie Sie den Body einer POST-Anforderung verarbeiten können, die durch ein HTML-Formular (Webformular) erzeugt wird (z. B. ein "Kontaktformular"). Beispielsweise könnten Sie ein HTML-Formular wie das Folgende nutzen: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> Für die folgende Beispielfunktion muss die Funktion in einer CloudFront -Betrachteranforderung oder -Ursprungsanforderung ausgelöst werden. Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request Beispiel: Verwenden eines Anforderungsauslösers zum Bearbeiten eines HTML-Formulars Diese Funktion zeigt, wie Sie den Body einer POST-Anforderung bearbeiten können, die durch ein HTML-Formular (Webformular) erzeugt wird. Die Funktion wird in einer CloudFront Viewer-Anfrage oder einer Origin-Anfrage ausgelöst. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action | 2026-01-13T09:30:35 |
https://docs.vml.visma.ai/smartscan/getting-started/ | Getting Started - Visma ML Assets Skip to content Visma ML Assets Getting Started Initializing search Visma ML Assets Home Quick Start Guide Endpoints Limitations & Rate Limit Authentication Smartscan Smartscan Getting Started Getting Started Table of contents Free Demo Quicklinks Getting started Access to the API Example request Authorization - Bearer Token Body - raw (json) Example response Body - raw (json) Model Versions Speed or performance Document Data Sources Example request POST v1/document:annotate Authorization - Bearer Token Body - raw (json) Confidence Levels VERIFIED Bounding Boxes How to Implement Bounding Boxes Page references Supported countries Supported file types Feature List Questions for Smartscan Feedback Loop Data Deletion API Reference Smartscan Async Smartscan Async Getting Started Feature List Autosuggest v2 Autosuggest v2 Getting Started Model Training Data Deletion API Reference Autosuggest v1 (deprecated) Autosuggest v1 (deprecated) Getting Started Dataset Type Structure Model Training Retention Policy API Reference SDKs API Status Support Table of contents Free Demo Quicklinks Getting started Access to the API Example request Authorization - Bearer Token Body - raw (json) Example response Body - raw (json) Model Versions Speed or performance Document Data Sources Example request POST v1/document:annotate Authorization - Bearer Token Body - raw (json) Confidence Levels VERIFIED Bounding Boxes How to Implement Bounding Boxes Page references Supported countries Supported file types Document annotator for intelligent ERP systems ¶ Smartscan is an is a cutting-edge data extraction tool (using OCR technology) for unstructured documents, such as invoices and receipts. The Smartscan API extracts, enriches and categorizes information details within seconds, and the output consists of a JSON document. Explore the use cases on our website . Free Demo ¶ Try our demo for free! Experience the power of the Smartscan API firsthand. Upload your document and get the scan results within seconds using our demo application . Quicklinks ¶ Smartscan's feature list . You can also find all available output fields in our GitHub repository . Comments in the protobuf will contain information on fields that have unique traits. All supported countries . All supported file types . How to start providing feedback data . Data Deletion Policy . Getting started ¶ Access to the API ¶ Demo Access Token For development purposes, you can use the demo access token demo , like in the example below, for access to staging. Use the staging endpoints indicated in the endpoints section . Please note that this token is rate-limited and should only be used for testing. Staging Access Token (Recommended) For more extensive testing and integration purposes, we recommend generating a staging access token through our Staging portal . Follow the steps in the Quick Start Guide for generating a staging or production access tokens. Refer to the Authentication for more information on the server-to-server token method. Example request ¶ POST v1/document:annotate https://api.stag.ssn.visma.ai/v1/document:annotate Authorization - Bearer Token ¶ Token: demo Body - raw (json) ¶ Body { "document" : { "source" : { "httpUri" : "http://storage.googleapis.com/vml-test-data/distributable/pdf5/10.pdf" } }, "features" : [ { "type" : "DEFAULT" } ], "tier" : "PREMIUM" } The response includes: Feedback ID : A unique identifier for each document. Read more in our feedback loop section . Page reference : Serves to backtrack what information was extracted and which page it was from. Read more here . Answers : The features that were requested and its corresponding answer. Note that the answer might not be there, if Smartscan determines that the information is not present on the document. This is shown in the example below. Bounding boxes : Represent the coordinates of the rectangular border that encloses a suggested field on the image of the document. Read more here . Confidence Level : Smartscan provides predictions accompanied by a confidence level, indicating the model's output quality. Read more here . Example response ¶ Body - raw (json) ¶ Body { "feedbackId" : "df7d8a8e-3332-40c1-bb97-aa981bcd0c4f" , "answers" : [ { "orderDate" :[{ "value" : "2015-07-09" , "text" : "09-07-2015" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 1730 , "y" : 732 },{ "x" : 1878 , "y" : 732 },{ "x" : 1878 , "y" : 762 },{ "x" : 1730 , "y" : 762 }], "normalizedVertices" :[{ "x" : 0.711348712 , "y" : 0.22276324 },{ "x" : 0.772203922 , "y" : 0.22276324 },{ "x" : 0.772203922 , "y" : 0.231892884 },{ "x" : 0.711348712 , "y" : 0.231892884 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "paymentDueDate" :[{ "value" : "2015-07-17" , "text" : "17-07-2015" , "confidence" :{ "level" : "HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 812 , "y" : 2900 },{ "x" : 996 , "y" : 2900 },{ "x" : 996 , "y" : 2952 },{ "x" : 812 , "y" : 2952 }], "normalizedVertices" :[{ "x" : 0.333881587 , "y" : 0.882531941 },{ "x" : 0.409539461 , "y" : 0.882531941 },{ "x" : 0.409539461 , "y" : 0.898356676 },{ "x" : 0.333881587 , "y" : 0.898356676 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "currency" :[{ "value" : "DKK" , "confidence" :{ "level" : "VERY_HIGH" }, "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "totalVat" :[{ "value" : "585.45" , "text" : "585,45" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 2092 , "y" : 2650 },{ "x" : 2214 , "y" : 2650 },{ "x" : 2214 , "y" : 2686 },{ "x" : 2092 , "y" : 2686 }], "normalizedVertices" :[{ "x" : 0.860197365 , "y" : 0.806451619 },{ "x" : 0.910361826 , "y" : 0.806451619 },{ "x" : 0.910361826 , "y" : 0.817407191 },{ "x" : 0.860197365 , "y" : 0.817407191 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "totalInclVat" :[{ "value" : "2927.24" , "text" : "2.927,24" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 2066 , "y" : 2734 },{ "x" : 2222 , "y" : 2734 },{ "x" : 2222 , "y" : 2770 },{ "x" : 2066 , "y" : 2770 }], "normalizedVertices" :[{ "x" : 0.849506557 , "y" : 0.83201462 },{ "x" : 0.913651288 , "y" : 0.83201462 },{ "x" : 0.913651288 , "y" : 0.842970192 },{ "x" : 0.849506557 , "y" : 0.842970192 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "totalExclVat" :[{ "value" : "2341.79" , "text" : "2.341,79)" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 804 , "y" : 2578 },{ "x" : 952 , "y" : 2578 },{ "x" : 952 , "y" : 2618 },{ "x" : 804 , "y" : 2618 }], "normalizedVertices" :[{ "x" : 0.330592096 , "y" : 0.784540474 },{ "x" : 0.391447365 , "y" : 0.784540474 },{ "x" : 0.391447365 , "y" : 0.796713352 },{ "x" : 0.330592096 , "y" : 0.796713352 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "supplierCorporateId" :[{ "value" : "30901347" , "text" : "30 90 13 47" , "confidence" :{ "level" : "HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 1762 , "y" : 490 },{ "x" : 1962 , "y" : 490 },{ "x" : 1962 , "y" : 526 },{ "x" : 1762 , "y" : 526 }], "normalizedVertices" :[{ "x" : 0.724506557 , "y" : 0.14911747 },{ "x" : 0.806743443 , "y" : 0.14911747 },{ "x" : 0.806743443 , "y" : 0.160073042 },{ "x" : 0.724506557 , "y" : 0.160073042 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "supplierCountryCode" :[{ "value" : "DK" , "confidence" :{ "level" : "VERY_HIGH" }, "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "documentType" :[{ "value" : "Invoice" , "confidence" :{ "level" : "VERY_HIGH" }, "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "paymentMethod" :[{ "value" : "BankTransfer" , "confidence" :{ "level" : "VERY_HIGH" }, "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "invoiceNumber" :[{ "value" : "1925" , "text" : "1925" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 1732 , "y" : 694 },{ "x" : 1796 , "y" : 694 },{ "x" : 1796 , "y" : 720 },{ "x" : 1732 , "y" : 720 }], "normalizedVertices" :[{ "x" : 0.712171078 , "y" : 0.21119903 },{ "x" : 0.738486826 , "y" : 0.21119903 },{ "x" : 0.738486826 , "y" : 0.219111383 },{ "x" : 0.712171078 , "y" : 0.219111383 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "feedbackId" : "cff4fb8e-6d3b-404e-8df6-cf440562f266" , "documentNumber" :[{ "value" : "1925" , "text" : "1925" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 1732 , "y" : 694 },{ "x" : 1796 , "y" : 694 },{ "x" : 1796 , "y" : 720 },{ "x" : 1732 , "y" : 720 }], "normalizedVertices" :[{ "x" : 0.712171078 , "y" : 0.21119903 },{ "x" : 0.738486826 , "y" : 0.21119903 },{ "x" : 0.738486826 , "y" : 0.219111383 },{ "x" : 0.712171078 , "y" : 0.219111383 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}], "documentDate" :[{ "value" : "2015-07-09" , "text" : "09-07-2015" , "confidence" :{ "level" : "VERY_HIGH" }, "boundingBox" :{ "vertices" :[{ "x" : 1730 , "y" : 732 },{ "x" : 1878 , "y" : 732 },{ "x" : 1878 , "y" : 762 },{ "x" : 1730 , "y" : 762 }], "normalizedVertices" :[{ "x" : 0.711348712 , "y" : 0.22276324 },{ "x" : 0.772203922 , "y" : 0.22276324 },{ "x" : 0.772203922 , "y" : 0.231892884 },{ "x" : 0.711348712 , "y" : 0.231892884 }]}, "pageRef" : 1 , "modelMetadata" :{ "modelName" : "layoutlm-r3" , "modelVer" : "1" }}]} } Model Versions ¶ Smartscan is available in two flavors: PREMIUM is our main model - replacing older versions of Smartscan with enhanced capabilities that was first launched in 2021. ULTRA is our top of the line model which employs both our proprietary AI as well as premium LLMs to deliver the best results in the business Speed or performance ¶ PREMIUM uses our own lightning fast proprietary AI and is ideal for interactive situations where response time is almost as important as AI quality. PREMIUM is available in two API flawors - synchronous and asynchronous . ULTRA combines our proprietary AI with assistance from top flight reasoning LLMs to deliver results that are significantly better than the sum of the parts. This introduces additional processing time, so the ULTRA tier is only available using our asynchronous API. Document Data Sources ¶ The caller can choose either to send the document data as part of the request or as shown in the example request through URI. Key field content is the document data base64 encoded. Example request ¶ POST v1/document:annotate ¶ https://api.stag.ssn.visma.ai/v1/document:annotate Authorization - Bearer Token ¶ Token: demo Body - raw (json) ¶ Body { "document" : { "content" : "Vl00oANHjF3gxaYT4fQ0PSDJwwZIuMLl0GdNlgyKhF4KYOtcH3r... -- this is unfinished base64 enconding --" }, "features" : [ { "type" : "DEFAULT" } ], "tier" : "PREMIUM" } Confidence Levels ¶ Smartscan provides predictions accompanied by a confidence level, indicating the model's output quality. The allowed confidence level values are as follows: VERY_HIGH, HIGH, MID, LOW, VERY_LOW Higher confidence levels suggest more accurate predictions. By default, we display suggestions with the highest confidence. We filter results based on confidence thresholds ( HIGH or VERY HIGH ) to enhance accuracy. You can customize confidence levels in your Smartscan requests, filtering results according to your desired confidence threshold, such as VERY HIGH . However, raising confidence levels may yield fewer suggestions. Results are sorted by confidence level, from most to least confident. VERIFIED ¶ With Smartscan's Verified functionality we introduce an additional value for the confidence level VERIFIED . Results that have been verified are cross checked with other results for greater precision. This is enabled by requesting the VERIFIED feature . Bounding Boxes ¶ In the Smartscan API, bounding boxes play a crucial role in extracting meaningful information from documents. A bounding box represents the coordinates of the rectangular border that encloses a suggested field on the image of the document, as shown in the image below. Utilising bounding boxes empowers you to precisely pinpoint and extract specific data, enhancing the accuracy and efficiency of your document processing. How to Implement Bounding Boxes ¶ When making API requests, include bounding box coordinates to define the region of interest within the document. Here's a basic example: { "bounding_box" : { "top_left" : { "x" : 100 , "y" : 150 }, "bottom_right" : { "x" : 300 , "y" : 250 } }, // Other request parameters... } Page references ¶ Pageref references to the number of the suggested field's page. When you send a document that is only one page long, Smartscan returns pageref of 1. When you send a document that is two or more pages long, Smartscan only reads the first and last page. As an example, if the document is four pages long, the pageref will return pageref of 1 and 4. The bounding box and pagerefs is present on majority of the fields. Supported countries ¶ Smartscan currently supports 51 countries , and we're continuously working to expand this list. Below is the complete list of supported countries: "AL", "AT", "AU", "BA", "BE", "BG", "BY", "CA", "CH", "CN", "CY", "CZ","DE", "DK", "EE", "EL", "ES", "FI", "FO", "FR", "GB", "GL", "HR", "HU", "IE", "IS", "IT", "LI", "LT", "LU", "LV", "MC", "MD", "ME", "MK", "MT", "NL", "NO", "NZ", "PL", "PT", "RO", "RS", "RU", "SE", "SI", "SK", "TR", "UA", "US", "XK" If you're unsure whether your country is supported, or if you require improved support for a specific country, please get in touch with us . Supported file types ¶ Below is the complete list of supported image types: PDF containing text (Recommended) PDF containing images (most often from scanners) JPG / JPEG (Recommended) PNG BMP webp tif gif bmp heif/heic In addition, Smartscan processes all text the OCR is able to scan. This can include handwritten receipts on standard pads. Copyright © 2023 Visma | 2026-01-13T09:30:35 |
http://www.videolan.org/vlc/releases/3.0.16.html | VLC 3.0.16 Vetinari - VideoLAN * { behavior: url("/style/box-sizing.htc"); } Toggle navigation VideoLAN Team & Organization Consulting Services & Partners Events Legal Press center Contact us VLC Download Features Customize Get Goodies Projects DVBlast x264 x262 x265 multicat dav1d VLC Skin Editor VLC media player libVLC libdvdcss libdvdnav libdvdread libbluray libdvbpsi libaacs libdvbcsa biTStream vlc-unity All Projects Contribute Getting started Donate Report a bug Support donate donate Donate donate donate VideoLAN, a project and a non-profit organization. VLC 3.0.16 Vetinari VLC 3.0.16 is the seventeenth version of the "Vetinari" branch of our popular media player. Hardware accelerated decoding for HD and UHD Supports HDR and HDR tone-mapping 360° video navigation Chromecast streaming Optimized for iPhone X Faster version for UWP and XBox One Get VLC now! Version 3.0 3.0.16 Fixes VLC 3.0.16 is the seventeenth update of "Vetinari": Fixes delays when seeking with D3D11 Fixes opening DVD folders with non-ASCII characters Fixes ASF regressions with broadcast streams Fixes dropping audio on seek with specific MP4 content Read the documentation when upgrading from VLC 3.0.12. Adds TouchBar support on macOS Fixes seek & volume sliders overlapping with subtitles Improves freetype fonts outlining Fixes HTTPS support on Windows XP Fixes OPUS and ALAC playback in WAV Read the Changelog . 3.0 Highlights VLC 3.0 "Vetinari" is a new major update of VLC VLC 3.0 activates hardware decoding by default, to get 4K and 8K playback! It supports 10bits and HDR VLC supports 360 video and 3D audio , up to Ambisonics 3rd order Allows audio passthrough for HD audio codecs Can stream to Chromecast devices, even in formats not supported natively Can play Blu-Ray Java menus : BD-J VLC supports browsing of local network drives and NAS Read the Changelog . VLC 3.0 playing 8K 48fps 360 video on Android Galaxy S8 from VideoLAN on Vimeo . VLC 3.0 playing 8k60 on Windows 10 using i7 GPU from VideoLAN on Vimeo . 3.0 Features Core Network browsing for distant filesystems (SMB, FTP, SFTP, NFS...) HDMI passthrough for Audio HD codecs, like E-AC3, TrueHD or DTS-HD 12bits codec and extended colorspaces (HDR) Stream to distant renderers, like Chromecast 360 video and 3D audio playback with viewpoint change Support for Ambisonics audio and more than 8 audio channels Subtitles size modification during playback Secure passwords storage Acceleration Hardware decoding and display on all platforms HEVC hardware decoding on Windows, using DxVA2 and D3D11 HEVC hardware decoding using OMX and MediaCodec (Android) MPEG-2, VC1/WMV3 hardware decoding on Android Important improvements for the MMAL decoder and output for rPI and rPI2 HEVC and H.264 hardware decoding for macOS and and iOS based on VideoToolbox New VA-API decoder and rendering for Linux Codecs BD-Java menus and overlay in Blu-Ray Experimental AV1 video and Daala video decoders OggSpots video decoder New MPEG-1 & 2 audio layer I, II, III + MPEG 2.5 decoder based on libmpg123 New BPG decoder based on libbpg TDSC, Canopus HQX, Cineform, SpeedHQ, Pixlet, QDMC and FMVC decoders TTML subtitles support, including EBU-TT variant Rewrite of webVTT subtitles support, including CSS style support BluRay text subtitles (HDMV) deocoder Support for ARIB-B24, CEA-708 New decoder for MIDI on macOS, iOS and Windows Containers Rework of the MP4 demuxer: including 608/708, Flip4Mac, XiphQT, VP8, TTML mappings Rework of the TS demuxer: including Opus, SCTE-18, ARIB mappings HD-DVD .evo support Rework of the PS demuxer, supporting HEVC, improving compatibility of broken files Improvements on MKV, including support for DVD-menus and FFv1, and faster seeking Support for Chained-Ogg, raw-HEVC and improvements for Flac Support for Creative ADPCM in AVI and VOC files Improved metadata formats in most file formats Protocols and devices Full support for Bluray Menus (BD-J) and Bluray ISO Rewrite of Adaptive Streaming protocols support Support for HLSv4 to HLSv7, including MP4 and ID3 cases Rewrite of DASH support, including MPEG2TS and ISOBMFF Support SAT>IP devices, for DVB-S via IP networks Support for HTTP 2.0 Support NFS, SMB and SFTP shares, with browsing Support for SRT streaming protocol Stream output and encoding Support for streaming to Chromecast devices Support for VP8 and VP9 encoding through libvpx Support for streaming Opus inside TS Support for mp4 fragmented muxing Improvements for x265 encoding Video outputs and filters OpenGL as Linux/BSD default video output Improvements in OpenGL output: direct displaying and HDR tonemapping Rework of the Android video outputs New Direct3D11 video output supporting both Windows desktop and WinRT modes HDR10 support in Direct3D11 with Windows 10 Fall Creator Update Hardware deinterlacing on the rPI, using MMAL Video filter to convert between fps rates Hardware accelerated deinterlacing/adjust/sharpen/chroma with VA-API Hardware accelerated adjust/invert/posterize/sepia/sharpen with CoreImage Hardware accelerated deinterlacing/adjust/chroma with D3D9 and D3D11 Audio outputs and filters Complete rewrite of the AudioTrack Android output New Tizen audio output HDMI/SPDIF pass-through support for WASAPI (AC3/DTS/DTSHD/EAC3/TRUEHD) Support EAC3 and TRUEHD pass-through for PulseAudio Rework of the AudioUnit modules to share more code between iOS and macOS SoX Resampler library audio filter module (converter and resampler) Ambisonics audio renderer, supporting up to 3rd order Binauralizer audio filter, working with Ambisonics or 5.1/7.1 streams Pitch shifting module OS Versions Windows XP ➔ 10 RS3 macOS 10.7 ➔ 10.13 iOS 7 ➔ 11 Android 2.3 ➔ 8.1 Android TV, Chromebooks with Play Store Windows RT 8.1, Windows Phone 8.1 Windows 10 Mobile, Xbox 1, Windows Store GNU/Linux, Ubuntu, *BSD Android specific Chromecast support from your phone HEVC hardware decoding using MediaCodec Android Auto with voice actions Available on all Android TV, Chromebooks & DeX Support for Picture-in-Picture Playlist files detection VLC SDK - libVLC New bindings for C++ and C++/CX New input-from-memory to implement custom protocols or DRM Support for ChromeCast and Renderer targets Improve API for servers discovery New API for dialogs, notably for HTTPS warnings New API to manage slaves inputs, including subtitles over the network Improve codec, format descriptions and associated metadata Improve EPG events API Better support for Android applications, native and Java ones Download VLC Windows VLC for Windows Version 3.0.16 Android macOS VLC for macOS Version 3.0.16 - 64bits iOS Windows Store and UWP Windows Phone Sources Get the source! Linux Ask your favorite packager for VLC 3.0! Related links Changelog Contact For any questions related to this release, please contact us . VLC media player VLC VLC for Windows VLC for Mac OS X VLC for Ubuntu VLC for Android VLC for iOS Skins Extensions Features Screenshots VLC Skin Editor All Projects VideoLan Movie Creator DVBlast x264 x262 x265 multicat dav1d VLMa libVLC libdvdcss libdvdnav libdvdread libbluray libdvbpsi libaacs libdvbcsa biTStream vlc-unity Community Wiki Forums Mailing-Lists FAQ Donate money Donate time Get Goodies VideoLAN Project and Organization Team Legal Contact us Partners Mirrors Press center Events Security center Get Involved News Legal | Report Trademark Abuse VideoLAN, VLC, VLC media player and x264 are trademarks internationally registered by the VideoLAN non-profit organization. VideoLAN software is licensed under various open-source licenses: use and distribution are defined by each software license. Design by Made By Argon . Some icons are licensed under the CC BY-SA 3.0+ . The VLC cone icon was designed by Richard Øiestad. Icons for VLMC, DVBlast and x264 designed by Roman Khramov . | 2026-01-13T09:30:35 |
https://support.microsoft.com/pt-br/windows/gerencie-cookies-no-microsoft-edge-exibir-permitir-bloquear-excluir-e-usar-168dab11-0753-043d-7c16-ede5947fc64d | Gerencie cookies no Microsoft Edge: exibir, permitir, bloquear, excluir e usar. - Suporte da Microsoft Tópicos relacionados × Segurança, segurança e privacidade do Windows Visão Geral Visão geral de segurança, segurança e privacidade Segurança do Windows Obter ajuda com a segurança do Windows Mantenha-se protegido com a segurança do Windows Antes de reciclar, vender ou presentear o seu Xbox ou computador Windows Remova o malware do seu computador Windows Segurança do Windows Obter ajuda com a segurança do Windows Exibir e excluir o histórico do navegador no Microsoft Edge Excluir e gerenciar cookies Remova com segurança seu conteúdo valioso ao reinstalar o Windows Localizar e bloquear um dispositivo Windows perdido Privacidade do Windows Obter ajuda com a privacidade do Windows Configurações de privacidade do Windows que os aplicativos usam Ver seus dados no painel de privacidade Pular para o conteúdo principal Microsoft Suporte Suporte Suporte Início Microsoft 365 Office Produtos Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mais ... Dispositivos Surface Acessórios de computador Xbox Jogos de Computador HoloLens Surface Hub Garantias de hardware Conta & cobrança Conta Microsoft Store & cobrança Recursos Novidades Fóruns da Comunidade Administração Microsoft 365 Portal de Pequenas Empresas Desenvolvedor Educação Relatar um golpe de suporte Segurança do produto Mais Comprar o Microsoft 365 Toda a Microsoft Global Microsoft 365 Teams Copilot Windows Xbox Suporte Software Software Aplicações Windows IA OneDrive Outlook Como migrar do Skype para o Teams OneNote Microsoft Teams PCs e dispositivos PCs e dispositivos Compre o Xbox Acessórios para PC Entretenimento Entretenimento Xbox Game Pass Ultimate Xbox e jogos Jogos para PC Negócios Negócios Segurança da Microsoft Azure Dynamics 365 Microsoft 365 para empresas Microsoft Industry Microsoft Power Platform Windows 365 Desenvolvedor & it Desenvolvedor & it Desenvolvedor Microsoft Microsoft Learn Suporte para aplicativos de marketplace de IA Comunidade Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards Outros Outros Microsoft Rewards Segurança e downloads gratuitos Educação Cartões-presente Licenciamento Ver mapa do site Pesquisar Procurar ajuda Nenhum resultado Cancelar Entrar Entrar com a conta da Microsoft Entrar ou criar uma conta. Olá, Selecionar uma conta diferente. Você tem várias contas Escolha a conta com a qual você deseja entrar. Tópicos relacionados Segurança, segurança e privacidade do Windows Visão Geral Visão geral de segurança, segurança e privacidade Segurança do Windows Obter ajuda com a segurança do Windows Mantenha-se protegido com a segurança do Windows Antes de reciclar, vender ou presentear o seu Xbox ou computador Windows Remova o malware do seu computador Windows Segurança do Windows Obter ajuda com a segurança do Windows Exibir e excluir o histórico do navegador no Microsoft Edge Excluir e gerenciar cookies Remova com segurança seu conteúdo valioso ao reinstalar o Windows Localizar e bloquear um dispositivo Windows perdido Privacidade do Windows Obter ajuda com a privacidade do Windows Configurações de privacidade do Windows que os aplicativos usam Ver seus dados no painel de privacidade Gerencie cookies no Microsoft Edge: exibir, permitir, bloquear, excluir e usar. 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 resolve 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 Excluir todos os cookies Excluir cookies de um site específico Excluir cookies sempre que fechar o navegador 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 isso pode impedir que algumas páginas sejam exibidas corretamente. Também pode aparecer uma mensagem em um site avisando que é preciso permitir os cookies para poder visualizá-lo. 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 isso pode impedir que algumas páginas sejam exibidas corretamente. Também pode aparecer uma mensagem em um site avisando que é preciso permitir os cookies para poder visualizá-lo. 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. Excluir todos os cookies Abra o browser Edge, selecione Definições e muito mais no canto superior direito da janela do browser. Selecione Configuraçõ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 , escolha um intervalo de tempo da lista. Selecione Cookies e outros dados do site e então selecione Limpar agora . Observação: 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 agora serão excluídos para o intervalo de tempo selecionado. Isso faz com que você saia da maioria dos sites. Excluir 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 você deseja excluir e selecione Excluir . Os cookies do site que selecionou são agora eliminados. Repita esta etapa para qualquer site cujos cookies você deseja excluir. Excluir cookies sempre que fechar o navegador 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 opção Cookies e outros dados do site . Assim que esta funcionalidade estiver ativada, sempre que fechar o browser Edge, todos os cookies e outros dados do site são eliminados. Isso faz com que você saia da 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 Configuraçõ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. ASSINAR RSS FEEDS Precisa de mais ajuda? Quer mais opções Descobrir Comunidade Entre em contato conosco Explore os benefícios da assinatura, procure cursos de treinamento, saiba como proteger seu dispositivo e muito mais. Benefícios da assinatura do Microsoft 365 Treinamento do Microsoft 365 Segurança da Microsoft Centro de acessibilidade As comunidades ajudam você a fazer e responder perguntas, fazer comentários e ouvir especialistas com conhecimento avançado. Perguntar à comunidade da Microsoft Microsoft Tech Community Windows Insiders Insiders do Microsoft 365 Encontre soluções para problemas comuns ou obtenha ajuda de um agente de suporte. Suporte online Essas informações foram úteis? Sim Não Obrigado! Mais algum comentário para a Microsoft? Poderia nos ajudar a melhorar? (Envie comentários à Microsoft para que possamos ajudar.) Qual é o seu grau de satisfação com a qualidade do idioma? O que afetou sua experiência? Resolveu meu problema Instruções claras Fácil de seguir Sem jargão As imagens foram úteis Qualidade da tradução Incompatível com a minha tela Instruções incorretas Muito técnico Não há informações suficientes Não há imagens suficientes Qualidade da tradução Algum comentário adicional? (opcional) Enviar comentários Ao pressionar enviar, seus comentários serão usados para aprimorar os produtos e serviços da Microsoft. Seu administrador de TI poderá coletar esses dados. Política de Privacidade. Agradecemos seus comentários! × Novidades Copilot para organizações Copilot para uso pessoal Microsoft 365 Explorar os produtos da Microsoft Aplicativos do Windows 11 Microsoft Store Perfil da conta Centro de Download Suporte da Microsoft Store Devoluções Acompanhamento de pedidos Educação Microsoft Education Dispositivos para educação Microsoft Teams para Educação Microsoft 365 Education Office Education Treinamento e desenvolvimento de educadores Ofertas para estudantes e pais Azure para estudantes Negócios Segurança da Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Desenvolvedor e TI Desenvolvedor Microsoft Microsoft Learn Suporte para aplicativos de marketplace de IA Comunidade Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Empresa Carreiras Sobre a Microsoft Notícias da empresa Privacidade na Microsoft Investidores Diversidade e inclusão Acessibilidade Sustentabilidade Português (Brasil) Ícone de recusa de opções de privacidade Suas opções de privacidade Ícone de recusa de opções de privacidade Suas opções de privacidade Privacidade dos Dados de Saúde do Consumidor Entre em contato com a Microsoft Privacidade Gerenciar cookies Ética e Compliance Nota Legal Marcas Sobre os nossos anúncios © Microsoft 2026 Microsoft do Brasil Importação e Comércio de Software e Vídeo Games Ltda., com sede na cidade de São Paulo, Estado de São Paulo, na Avenida Presidente Juscelino Kubitschek, nº 1.909, conjunto 181, localizado no 18º andar da Torre Sul SP Corporate Towers, Vila Nova Conceição, CEP 04543-907, inscrita no CNPJ sob o nº 04.712.500/0001-07. | 2026-01-13T09:30:35 |
https://docs.aws.amazon.com/pt_br/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html | Funções de exemplo do Lambda@Edge - Amazon CloudFront Funções de exemplo do Lambda@Edge - Amazon CloudFront Documentação Amazon CloudFront Guia do Desenvolvedor Exemplos gerais Gerar respostas: exemplos Strings de consulta: exemplos Personalizar o conteúdo por cabeçalhos de país ou tipo de dispositivo: exemplos Seleção de origem dinâmica baseada em conteúdo: exemplos Atualização do status de erro: exemplos Acesso ao corpo da solicitação: exemplos Funções de exemplo do Lambda@Edge Veja os exemplos a seguir de como usar as funções do Lambda com o Amazon CloudFront. nota Se você escolher o runtime Node.js 18 ou posterior para a função Lambda@Edge, um arquivo index.mjs será criado automaticamente para você. Para usar os exemplos de código a seguir, renomeie o arquivo index.mjs para index.js . Tópicos Exemplos gerais Gerar respostas: exemplos Strings de consulta: exemplos Personalizar o conteúdo por cabeçalhos de país ou tipo de dispositivo: exemplos Seleção de origem dinâmica baseada em conteúdo: exemplos Atualização do status de erro: exemplos Acesso ao corpo da solicitação: exemplos Exemplos gerais Os exemplos a seguir mostram as maneiras comuns de usar o Lambda@Edge no CloudFront. Tópicos Exemplo: testes A/B Exemplo: substituir um cabeçalho de resposta Exemplo: testes A/B Você pode usar o exemplo a seguir para testar duas versões diferentes de uma imagem sem criar redirecionamentos nem alterar a URL. Este exemplo lê os cookies na solicitação do visualizador e modifica a URL da solicitação adequadamente. Se o visualizador não enviar um cookie com um dos valores esperados, o exemplo atribuirá aleatoriamente o visualizador a um dos URLs. Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; if (request.uri !== '/experiment-pixel.jpg') { // do not process if this is not an A-B test request callback(null, request); return; } const cookieExperimentA = 'X-Experiment-Name=A'; const cookieExperimentB = 'X-Experiment-Name=B'; const pathExperimentA = '/experiment-group/control-pixel.jpg'; const pathExperimentB = '/experiment-group/treatment-pixel.jpg'; /* * Lambda at the Edge headers are array objects. * * Client may send multiple Cookie headers, i.e.: * > GET /viewerRes/test HTTP/1.1 * > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 * > Cookie: First=1; Second=2 * > Cookie: ClientCode=abc * > Host: example.com * * You can access the first Cookie header at headers["cookie"][0].value * and the second at headers["cookie"][1].value. * * Header values are not parsed. In the example above, * headers["cookie"][0].value is equal to "First=1; Second=2" */ let experimentUri; if (headers.cookie) { for (let i = 0; i < headers.cookie.length; i++) { if (headers.cookie[i].value.indexOf(cookieExperimentA) >= 0) { console.log('Experiment A cookie found'); experimentUri = pathExperimentA; break; } else if (headers.cookie[i].value.indexOf(cookieExperimentB) >= 0) { console.log('Experiment B cookie found'); experimentUri = pathExperimentB; break; } } } if (!experimentUri) { console.log('Experiment cookie has not been found. Throwing dice...'); if (Math.random() < 0.75) { experimentUri = pathExperimentA; } else { experimentUri = pathExperimentB; } } request.uri = experimentUri; console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python import json import random def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] if request['uri'] != '/experiment-pixel.jpg': # Not an A/B Test return request cookieExperimentA, cookieExperimentB = 'X-Experiment-Name=A', 'X-Experiment-Name=B' pathExperimentA, pathExperimentB = '/experiment-group/control-pixel.jpg', '/experiment-group/treatment-pixel.jpg' ''' Lambda at the Edge headers are array objects. Client may send multiple cookie headers. For example: > GET /viewerRes/test HTTP/1.1 > User-Agent: curl/7.18.1 (x86_64-unknown-linux-gnu) libcurl/7.18.1 OpenSSL/1.0.1u zlib/1.2.3 > Cookie: First=1; Second=2 > Cookie: ClientCode=abc > Host: example.com You can access the first Cookie header at headers["cookie"][0].value and the second at headers["cookie"][1].value. Header values are not parsed. In the example above, headers["cookie"][0].value is equal to "First=1; Second=2" ''' experimentUri = "" for cookie in headers.get('cookie', []): if cookieExperimentA in cookie['value']: print("Experiment A cookie found") experimentUri = pathExperimentA break elif cookieExperimentB in cookie['value']: print("Experiment B cookie found") experimentUri = pathExperimentB break if not experimentUri: print("Experiment cookie has not been found. Throwing dice...") if random.random() < 0.75: experimentUri = pathExperimentA else: experimentUri = pathExperimentB request['uri'] = experimentUri print(f"Request uri set to { experimentUri}") return request Exemplo: substituir um cabeçalho de resposta O exemplo abaixo mostra como alterar o valor de um cabeçalho de resposta com base no valor de outro cabeçalho. Node.js export const handler = async (event) => { const response = event.Records[0].cf.response; const headers = response.headers; const headerNameSrc = 'X-Amz-Meta-Last-Modified'; const headerNameDst = 'Last-Modified'; if (headers[headerNameSrc.toLowerCase()]) { headers[headerNameDst.toLowerCase()] = [ { key: headerNameDst, value: headers[headerNameSrc.toLowerCase()][0].value, }]; console.log(`Response header "$ { headerNameDst}" was set to ` + `"$ { headers[headerNameDst.toLowerCase()][0].value}"`); } return response; }; Python import json def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] headers = response['headers'] header_name_src = 'X-Amz-Meta-Last-Modified' header_name_dst = 'Last-Modified' if headers.get(header_name_src.lower()): headers[header_name_dst.lower()] = [ { 'key': header_name_dst, 'value': headers[header_name_src.lower()][0]['value'] }] print(f'Response header " { header_name_dst}" was set to ' f'" { headers[header_name_dst.lower()][0]["value"]}"') return response Gerar respostas: exemplos Os exemplos a seguir mostram como você pode usar o Lambda@Edge para gerar respostas. Tópicos Exemplo: fornecer conteúdo estático (resposta gerada) Exemplo: gerar um redirecionamento de HTTP (resposta gerada) Exemplo: fornecer conteúdo estático (resposta gerada) O exemplo a seguir mostra como usar uma função do Lambda para fornecer conteúdo estático de site. Isso reduz a carga no servidor de origem e a latência geral. nota Você pode gerar respostas HTTP para eventos de solicitação de visualizador e de solicitação de origem. Para obter mais informações, consulte Gerar respostas de HTTP em acionadores da solicitação . Você também pode substituir ou remover o corpo da resposta de HTTP em eventos de resposta de origem. Para obter mais informações, consulte Atualizar respostas de HTTP em acionadores de resposta da origem . Node.js 'use strict'; const content = ` <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> `; exports.handler = (event, context, callback) => { /* * Generate HTTP OK response using 200 status code with HTML body. */ const response = { status: '200', statusDescription: 'OK', headers: { 'cache-control': [ { key: 'Cache-Control', value: 'max-age=100' }], 'content-type': [ { key: 'Content-Type', value: 'text/html' }] }, body: content, }; callback(null, response); }; Python import json CONTENT = """ <\!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Simple Lambda@Edge Static Content Response</title> </head> <body> <p>Hello from Lambda@Edge!</p> </body> </html> """ def lambda_handler(event, context): # Generate HTTP OK response using 200 status code with HTML body. response = { 'status': '200', 'statusDescription': 'OK', 'headers': { 'cache-control': [ { 'key': 'Cache-Control', 'value': 'max-age=100' } ], "content-type": [ { 'key': 'Content-Type', 'value': 'text/html' } ] }, 'body': CONTENT } return response Exemplo: gerar um redirecionamento de HTTP (resposta gerada) O exemplo abaixo mostra como gerar um redirecionamento HTTP. nota Você pode gerar respostas HTTP para eventos de solicitação de visualizador e de solicitação de origem. Para obter mais informações, consulte Gerar respostas de HTTP em acionadores da solicitação . Node.js 'use strict'; exports.handler = (event, context, callback) => { /* * Generate HTTP redirect response with 302 status code and Location header. */ const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html', }], }, }; callback(null, response); }; Python def lambda_handler(event, context): # Generate HTTP redirect response with 302 status code and Location header. response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html' }] } } return response Strings de consulta: exemplos Os exemplos a seguir mostram maneiras de usar o Lambda@Edge com strings de consulta. Tópicos Exemplo: adicionar um cabeçalho com base em um parâmetro de string de consulta Exemplo: normalizar os parâmetros da string de consulta para melhorar a proporção de acertos no cache Exemplo: redirecionar usuários não autenticados para uma página de login Exemplo: adicionar um cabeçalho com base em um parâmetro de string de consulta O exemplo a seguir mostra como obter o par chave-valor de um parâmetro de string de consulta e adicionar um cabeçalho com base nesses valores. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When a request contains a query string key-value pair but the origin server * expects the value in a header, you can use this Lambda function to * convert the key-value pair to a header. Here's what the function does: * 1. Parses the query string and gets the key-value pair. * 2. Adds a header to the request using the key-value pair that the function got in step 1. */ /* Parse request querystring to get javascript object */ const params = querystring.parse(request.querystring); /* Move auth param from querystring to headers */ const headerName = 'Auth-Header'; request.headers[headerName.toLowerCase()] = [ { key: headerName, value: params.auth }]; delete params.auth; /* Update request querystring */ request.querystring = querystring.stringify(params); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When a request contains a query string key-value pair but the origin server expects the value in a header, you can use this Lambda function to convert the key-value pair to a header. Here's what the function does: 1. Parses the query string and gets the key-value pair. 2. Adds a header to the request using the key-value pair that the function got in step 1. ''' # Parse request querystring to get dictionary/json params = { k : v[0] for k, v in parse_qs(request['querystring']).items()} # Move auth param from querystring to headers headerName = 'Auth-Header' request['headers'][headerName.lower()] = [ { 'key': headerName, 'value': params['auth']}] del params['auth'] # Update request querystring request['querystring'] = urlencode(params) return request Exemplo: normalizar os parâmetros da string de consulta para melhorar a proporção de acertos no cache O exemplo a seguir mostra como melhorar o índice de ocorrência no cache fazendo as seguintes alterações nas strings de consulta antes que o CloudFront encaminhe as solicitações para a origem: Colocar os pares de chave-valor em ordem alfabética pelo nome do parâmetro. Alterar os pares de chave-valor para minúsculas. Para obter mais informações, consulte Conteúdo em cache com base em parâmetros de string de consulta . Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /* When you configure a distribution to forward query strings to the origin and * to cache based on an allowlist of query string parameters, we recommend * the following to improve the cache-hit ratio: * - Always list parameters in the same order. * - Use the same case for parameter names and values. * * This function normalizes query strings so that parameter names and values * are lowercase and parameter names are in alphabetical order. * * For more information, see: * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html */ console.log('Query String: ', request.querystring); /* Parse request query string to get javascript object */ const params = querystring.parse(request.querystring.toLowerCase()); const sortedParams = { }; /* Sort param keys */ Object.keys(params).sort().forEach(key => { sortedParams[key] = params[key]; }); /* Update request querystring with normalized */ request.querystring = querystring.stringify(sortedParams); callback(null, request); }; Python from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' When you configure a distribution to forward query strings to the origin and to cache based on an allowlist of query string parameters, we recommend the following to improve the cache-hit ratio: Always list parameters in the same order. - Use the same case for parameter names and values. This function normalizes query strings so that parameter names and values are lowercase and parameter names are in alphabetical order. For more information, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html ''' print("Query string: ", request["querystring"]) # Parse request query string to get js object params = { k : v[0] for k, v in parse_qs(request['querystring'].lower()).items()} # Sort param keys sortedParams = sorted(params.items(), key=lambda x: x[0]) # Update request querystring with normalized request['querystring'] = urlencode(sortedParams) return request Exemplo: redirecionar usuários não autenticados para uma página de login O exemplo a seguir mostra como redirecionar os usuários para uma página de login caso não tenham inserido as credenciais. Node.js 'use strict'; function parseCookies(headers) { const parsedCookie = { }; if (headers.cookie) { headers.cookie[0].value.split(';').forEach((cookie) => { if (cookie) { const parts = cookie.split('='); parsedCookie[parts[0].trim()] = parts[1].trim(); } }); } return parsedCookie; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* Check for session-id in request cookie in viewer-request event, * if session-id is absent, redirect the user to sign in page with original * request sent as redirect_url in query params. */ /* Check for session-id in cookie, if present then proceed with request */ const parsedCookies = parseCookies(headers); if (parsedCookies && parsedCookies['session-id']) { callback(null, request); return; } /* URI encode the original request to be sent as redirect_url in query params */ const encodedRedirectUrl = encodeURIComponent(`https://$ { headers.host[0].value}$ { request.uri}?$ { request.querystring}`); const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: `https://www.example.com/signin?redirect_url=$ { encodedRedirectUrl}`, }], }, }; callback(null, response); }; Python import urllib def parseCookies(headers): parsedCookie = { } if headers.get('cookie'): for cookie in headers['cookie'][0]['value'].split(';'): if cookie: parts = cookie.split('=') parsedCookie[parts[0].strip()] = parts[1].strip() return parsedCookie def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Check for session-id in request cookie in viewer-request event, if session-id is absent, redirect the user to sign in page with original request sent as redirect_url in query params. ''' # Check for session-id in cookie, if present, then proceed with request parsedCookies = parseCookies(headers) if parsedCookies and parsedCookies['session-id']: return request # URI encode the original request to be sent as redirect_url in query params redirectUrl = "https://%s%s?%s" % (headers['host'][0]['value'], request['uri'], request['querystring']) encodedRedirectUrl = urllib.parse.quote_plus(redirectUrl.encode('utf-8')) response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': 'https://www.example.com/signin?redirect_url=%s' % encodedRedirectUrl }] } } return response Personalizar o conteúdo por cabeçalhos de país ou tipo de dispositivo: exemplos Os exemplos a seguir mostram como você pode usar o Lambda@Edge para personalizar o comportamento com base no local ou no tipo de dispositivo usado pelo visualizador. Tópicos Exemplo: redirecionar as solicitações do visualizador para um URL específico do país Exemplo: fornecer diferentes versões de um objeto com base no dispositivo Exemplo: redirecionar as solicitações do visualizador para um URL específico do país O exemplo a seguir mostra como gerar uma resposta de redirecionamento HTTP com um URL específico do país e retornar a resposta para o visualizador. Isso é útil quando você deseja fornecer respostas específicas do país. Por exemplo: Se tiver subdomínios específicos do país, como us.example.com e tw.example.com, você pode gerar uma resposta de redirecionamento quando um visualizador solicitar example.com. Se estiver transmitindo um vídeo, mas não tem direitos para transmitir o conteúdo em um país específico, você pode redirecionar os usuários desse país para uma página que explica por que eles não podem visualizar o vídeo. Observe o seguinte: É necessário configurar a distribuição para armazenar em cache com base no cabeçalho CloudFront-Viewer-Country . Para obter mais informações, consulte Cache baseado em Cabeçalhos de solicitação selecionados . O CloudFront adiciona o cabeçalho CloudFront-Viewer-Country após o evento de solicitação do visualizador. Para usar este exemplo, é necessário criar um trigger para o evento de solicitação da origem. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Based on the value of the CloudFront-Viewer-Country header, generate an * HTTP status code 302 (Redirect) response, and return a country-specific * URL in the Location header. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ let url = 'https://example.com/'; if (headers['cloudfront-viewer-country']) { const countryCode = headers['cloudfront-viewer-country'][0].value; if (countryCode === 'TW') { url = 'https://tw.example.com/'; } else if (countryCode === 'US') { url = 'https://us.example.com/'; } } const response = { status: '302', statusDescription: 'Found', headers: { location: [ { key: 'Location', value: url, }], }, }; callback(null, response); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Based on the value of the CloudFront-Viewer-Country header, generate an HTTP status code 302 (Redirect) response, and return a country-specific URL in the Location header. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' url = 'https://example.com/' viewerCountry = headers.get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'TW': url = 'https://tw.example.com/' elif countryCode == 'US': url = 'https://us.example.com/' response = { 'status': '302', 'statusDescription': 'Found', 'headers': { 'location': [ { 'key': 'Location', 'value': url }] } } return response Exemplo: fornecer diferentes versões de um objeto com base no dispositivo O exemplo a seguir mostra como servir diferentes versões de um objeto com base no tipo de dispositivo usado pelo usuário, por exemplo, um dispositivo móvel ou um tablet. Observe o seguinte: É necessário configurar a distribuição para armazenar em cache com base nos cabeçalhos CloudFront-Is-*-Viewer . Para obter mais informações, consulte Cache baseado em Cabeçalhos de solicitação selecionados . O CloudFront adiciona os cabeçalhos CloudFront-Is-*-Viewer após o evento de solicitação do visualizador. Para usar este exemplo, é necessário criar um trigger para o evento de solicitação da origem. Node.js 'use strict'; /* This is an origin request function */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const headers = request.headers; /* * Serve different versions of an object based on the device type. * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Is-*-Viewer headers. For more information, see * the following documentation: * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type * 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const desktopPath = '/desktop'; const mobilePath = '/mobile'; const tabletPath = '/tablet'; const smarttvPath = '/smarttv'; if (headers['cloudfront-is-desktop-viewer'] && headers['cloudfront-is-desktop-viewer'][0].value === 'true') { request.uri = desktopPath + request.uri; } else if (headers['cloudfront-is-mobile-viewer'] && headers['cloudfront-is-mobile-viewer'][0].value === 'true') { request.uri = mobilePath + request.uri; } else if (headers['cloudfront-is-tablet-viewer'] && headers['cloudfront-is-tablet-viewer'][0].value === 'true') { request.uri = tabletPath + request.uri; } else if (headers['cloudfront-is-smarttv-viewer'] && headers['cloudfront-is-smarttv-viewer'][0].value === 'true') { request.uri = smarttvPath + request.uri; } console.log(`Request uri set to "$ { request.uri}"`); callback(null, request); }; Python # This is an origin request function def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] headers = request['headers'] ''' Serve different versions of an object based on the device type. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Is-*-Viewer headers. For more information, see the following documentation: https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers https://docs.aws.amazon.com/console/cloudfront/cache-on-device-type 2. CloudFront adds the CloudFront-Is-*-Viewer headers after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' desktopPath = '/desktop'; mobilePath = '/mobile'; tabletPath = '/tablet'; smarttvPath = '/smarttv'; if 'cloudfront-is-desktop-viewer' in headers and headers['cloudfront-is-desktop-viewer'][0]['value'] == 'true': request['uri'] = desktopPath + request['uri'] elif 'cloudfront-is-mobile-viewer' in headers and headers['cloudfront-is-mobile-viewer'][0]['value'] == 'true': request['uri'] = mobilePath + request['uri'] elif 'cloudfront-is-tablet-viewer' in headers and headers['cloudfront-is-tablet-viewer'][0]['value'] == 'true': request['uri'] = tabletPath + request['uri'] elif 'cloudfront-is-smarttv-viewer' in headers and headers['cloudfront-is-smarttv-viewer'][0]['value'] == 'true': request['uri'] = smarttvPath + request['uri'] print("Request uri set to %s" % request['uri']) return request Seleção de origem dinâmica baseada em conteúdo: exemplos Os exemplos a seguir mostram como você pode usar o Lambda@Edge para rotear para diferentes origens com base em informações na solicitação. Tópicos Exemplo: usar um acionador de solicitação de origem para alterar de uma origem personalizada para uma origem do Amazon S3 Exemplo: usar um acionador de solicitação de origem para alterar a região de origem do Amazon S3 Exemplo: usar um acionador de solicitação de origem para alterar de uma origem do Amazon S3 para uma origem personalizada Exemplo: usar um acionador de solicitação de origem para transferir gradualmente o tráfego de um bucket do Amazon S3 para outro Exemplo: usar um acionador de solicitação de origem para alterar o nome do domínio de origem com base no cabeçalho do país Exemplo: usar um acionador de solicitação de origem para alterar de uma origem personalizada para uma origem do Amazon S3 Essa função demonstra como um trigger origin-request pode ser usado para alterar de uma origem personalizada para uma origem do Amazon S3 da qual o conteúdo é obtido, com base nas propriedades da solicitação. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if S3 origin should be used, and * if true, sets S3 origin properties. */ const params = querystring.parse(request.querystring); if (params['useS3Origin']) { if (params['useS3Origin'] === 'true') { const s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com'; /* Set S3 origin fields */ request.origin = { s3: { domainName: s3DomainName, region: '', authMethod: 'origin-access-identity', path: '', customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: s3DomainName}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' Reads query string to check if S3 origin should be used, and if true, sets S3 origin properties ''' params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useS3Origin') == 'true': s3DomainName = 'amzn-s3-demo-bucket.s3.amazonaws.com' # Set S3 origin fields request['origin'] = { 's3': { 'domainName': s3DomainName, 'region': '', 'authMethod': 'origin-access-identity', 'path': '', 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': s3DomainName}] return request Exemplo: usar um acionador de solicitação de origem para alterar a região de origem do Amazon S3 Esta função demonstra como um trigger origin-request pode ser usado para alterar a origem do Amazon S3 da qual o conteúdo é obtido, com base nas propriedades da solicitação. Neste exemplo, usamos o valor do cabeçalho CloudFront-Viewer-Country para atualizar o nome do domínio de bucket do S3 para um bucket em uma região mais próxima do visualizador. Isso pode ser útil de várias maneiras: Reduz as latências quando a região especificada estiver mais próxima do país do visualizador. Fornece soberania de dados, garantindo que os dados sejam oferecidos de uma origem que esteja no mesmo país de onde veio a solicitação. Para usar esse exemplo, você precisa fazer o seguinte: Configure sua distribuição para armazenar em cache com base no cabeçalho CloudFront-Viewer-Country . Para obter mais informações, consulte Cache baseado em Cabeçalhos de solicitação selecionados . Crie um gatilho para essa função no evento de solicitação de origem. O CloudFront adiciona o cabeçalho CloudFront-Viewer-Country após o evento de solicitação do visualizador. Portanto, para usar este exemplo, você precisa garantir que a função seja executada para uma solicitação de origem. nota O código de exemplo a seguir usa a mesma identidade do acesso de origem (OAI) para todos os buckets do S3 que você está usando para sua origem. Para ter mais informações, consulte Visão geral da identidade do acesso de origem . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * This blueprint demonstrates how an origin-request trigger can be used to * change the origin from which the content is fetched, based on request properties. * In this example, we use the value of the CloudFront-Viewer-Country header * to update the S3 bucket domain name to a bucket in a Region that is closer to * the viewer. * * This can be useful in several ways: * 1) Reduces latencies when the Region specified is nearer to the viewer's * country. * 2) Provides data sovereignty by making sure that data is served from an * origin that's in the same country that the request came from. * * NOTE: 1. You must configure your distribution to cache based on the * CloudFront-Viewer-Country header. For more information, see * https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers * 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer * request event. To use this example, you must create a trigger for the * origin request event. */ const countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' }; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; const region = countryToRegion[countryCode]; /** * If the viewer's country is not in the list you specify, the request * goes to the default S3 bucket you've configured. */ if (region) { /** * If you've set up OAI, the bucket policy in the destination bucket * should allow the OAI GetObject operation, as configured by default * for an S3 origin with OAI. Another requirement with OAI is to provide * the Region so it can be used for the SIGV4 signature. Otherwise, the * Region is not required. */ request.origin.s3.region = region; const domainName = `amzn-s3-demo-bucket-in-$ { region}.s3.$ { region}.amazonaws.com`; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName }]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] ''' This blueprint demonstrates how an origin-request trigger can be used to change the origin from which the content is fetched, based on request properties. In this example, we use the value of the CloudFront-Viewer-Country header to update the S3 bucket domain name to a bucket in a Region that is closer to the viewer. This can be useful in several ways: 1) Reduces latencies when the Region specified is nearer to the viewer's country. 2) Provides data sovereignty by making sure that data is served from an origin that's in the same country that the request came from. NOTE: 1. You must configure your distribution to cache based on the CloudFront-Viewer-Country header. For more information, see https://docs.aws.amazon.com/console/cloudfront/cache-on-selected-headers 2. CloudFront adds the CloudFront-Viewer-Country header after the viewer request event. To use this example, you must create a trigger for the origin request event. ''' countryToRegion = { 'DE': 'eu-central-1', 'IE': 'eu-west-1', 'GB': 'eu-west-2', 'FR': 'eu-west-3', 'JP': 'ap-northeast-1', 'IN': 'ap-south-1' } viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] region = countryToRegion.get(countryCode) # If the viewer's country in not in the list you specify, the request # goes to the default S3 bucket you've configured if region: ''' If you've set up OAI, the bucket policy in the destination bucket should allow the OAI GetObject operation, as configured by default for an S3 origin with OAI. Another requirement with OAI is to provide the Region so it can be used for the SIGV4 signature. Otherwise, the Region is not required. ''' request['origin']['s3']['region'] = region domainName = 'amzn-s3-demo-bucket-in- { 0}.s3. { 0}.amazonaws.com'.format(region) request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Exemplo: usar um acionador de solicitação de origem para alterar de uma origem do Amazon S3 para uma origem personalizada Esta função demonstra como um trigger de origem-solicitação pode ser usado para alterar a origem personalizada de onde o conteúdo é obtido, com base nas propriedades da solicitação. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; /** * Reads query string to check if custom origin should be used, and * if true, sets custom origin properties. */ const params = querystring.parse(request.querystring); if (params['useCustomOrigin']) { if (params['useCustomOrigin'] === 'true') { /* Set custom origin fields*/ request.origin = { custom: { domainName: 'www.example.com', port: 443, protocol: 'https', path: '', sslProtocols: ['TLSv1', 'TLSv1.1'], readTimeout: 5, keepaliveTimeout: 5, customHeaders: { } } }; request.headers['host'] = [ { key: 'host', value: 'www.example.com'}]; } } callback(null, request); }; Python from urllib.parse import parse_qs def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] # Reads query string to check if custom origin should be used, and # if true, sets custom origin properties params = { k: v[0] for k, v in parse_qs(request['querystring']).items()} if params.get('useCustomOrigin') == 'true': # Set custom origin fields request['origin'] = { 'custom': { 'domainName': 'www.example.com', 'port': 443, 'protocol': 'https', 'path': '', 'sslProtocols': ['TLSv1', 'TLSv1.1'], 'readTimeout': 5, 'keepaliveTimeout': 5, 'customHeaders': { } } } request['headers']['host'] = [ { 'key': 'host', 'value': 'www.example.com'}] return request Exemplo: usar um acionador de solicitação de origem para transferir gradualmente o tráfego de um bucket do Amazon S3 para outro Essa função demonstra como transferir o tráfego de um bucket do Amazon S3 para outro de forma gradual e controlada. Node.js 'use strict'; function getRandomInt(min, max) { /* Random number is inclusive of min and max*/ return Math.floor(Math.random() * (max - min + 1)) + min; } exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; const BLUE_TRAFFIC_PERCENTAGE = 80; /** * This Lambda function demonstrates how to gradually transfer traffic from * one S3 bucket to another in a controlled way. * We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from * 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic * is re-directed to blue-bucket. If not, the default bucket that we've configured * is used. */ const randomNumber = getRandomInt(1, 100); if (randomNumber <= BLUE_TRAFFIC_PERCENTAGE) { const domainName = 'blue-bucket.s3.amazonaws.com'; request.origin.s3.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } callback(null, request); }; Python import math import random def getRandomInt(min, max): # Random number is inclusive of min and max return math.floor(random.random() * (max - min + 1)) + min def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] BLUE_TRAFFIC_PERCENTAGE = 80 ''' This Lambda function demonstrates how to gradually transfer traffic from one S3 bucket to another in a controlled way. We define a variable BLUE_TRAFFIC_PERCENTAGE which can take values from 1 to 100. If the generated randomNumber less than or equal to BLUE_TRAFFIC_PERCENTAGE, traffic is re-directed to blue-bucket. If not, the default bucket that we've configured is used. ''' randomNumber = getRandomInt(1, 100) if randomNumber <= BLUE_TRAFFIC_PERCENTAGE: domainName = 'blue-bucket.s3.amazonaws.com' request['origin']['s3']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Exemplo: usar um acionador de solicitação de origem para alterar o nome do domínio de origem com base no cabeçalho do país Esta função demonstra como você pode alterar o nome de domínio de origem com base no cabeçalho CloudFront-Viewer-Country , de forma que o conteúdo seja fornecido de origem mais próxima do país do visualizador. A implementação dessa funcionalidade para sua distribuição pode ter vantagens, como as seguintes: Redução das latências quando a região especificada estiver mais próxima do país do visualizador Fornecimento da soberania de dados garantindo que os dados sejam fornecidos de uma origem que esteja no mesmo país de onde veio a solicitação Observe que, para habilitar essa funcionalidade, você deve configurar sua distribuição para o cache com base no cabeçalho CloudFront-Viewer-Country . Para obter mais informações, consulte Cache baseado em Cabeçalhos de solicitação selecionados . Node.js 'use strict'; exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.headers['cloudfront-viewer-country']) { const countryCode = request.headers['cloudfront-viewer-country'][0].value; if (countryCode === 'GB' || countryCode === 'DE' || countryCode === 'IE' ) { const domainName = 'eu.example.com'; request.origin.custom.domainName = domainName; request.headers['host'] = [ { key: 'host', value: domainName}]; } } callback(null, request); }; Python def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] viewerCountry = request['headers'].get('cloudfront-viewer-country') if viewerCountry: countryCode = viewerCountry[0]['value'] if countryCode == 'GB' or countryCode == 'DE' or countryCode == 'IE': domainName = 'eu.example.com' request['origin']['custom']['domainName'] = domainName request['headers']['host'] = [ { 'key': 'host', 'value': domainName}] return request Atualização do status de erro: exemplos Os exemplos a seguir fornecem orientações sobre como você pode usar o Lambda@Edge para alterar o status de erro retornado para os usuários. Tópicos Exemplo: usar um acionador de resposta de origem para atualizar o código do status de erro para 200 Exemplo: usar um acionador de resposta de origem para atualizar o código do status de erro para 302 Exemplo: usar um acionador de resposta de origem para atualizar o código do status de erro para 200 Esta função demonstra como você pode atualizar o status da resposta para 200 e gerar conteúdo do corpo estático para retornar ao visualizador no cenário a seguir: A função é acionada em uma resposta da origem. O status da resposta do servidor de origem é um código de status de erro (4xx ou 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; /** * This function updates the response status to 200 and generates static * body content to return to the viewer in the following scenario: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { response.status = 200; response.statusDescription = 'OK'; response.body = 'Body generation example'; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] ''' This function updates the response status to 200 and generates static body content to return to the viewer in the following scenario: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: response['status'] = 200 response['statusDescription'] = 'OK' response['body'] = 'Body generation example' return response Exemplo: usar um acionador de resposta de origem para atualizar o código do status de erro para 302 Essa função demonstra como você pode atualizar o código de status HTTP para 302, de forma a redirecionar a outro caminho (comportamento de cache) que tem uma origem diferente configurada. Observe o seguinte: A função é acionada em uma resposta da origem. O status da resposta do servidor de origem é um código de status de erro (4xx ou 5xx). Node.js 'use strict'; exports.handler = (event, context, callback) => { const response = event.Records[0].cf.response; const request = event.Records[0].cf.request; /** * This function updates the HTTP status code in the response to 302, to redirect to another * path (cache behavior) that has a different origin configured. Note the following: * 1. The function is triggered in an origin response * 2. The response status from the origin server is an error status code (4xx or 5xx) */ if (response.status >= 400 && response.status <= 599) { const redirect_path = `/plan-b/path?$ { request.querystring}`; response.status = 302; response.statusDescription = 'Found'; /* Drop the body, as it is not required for redirects */ response.body = ''; response.headers['location'] = [ { key: 'Location', value: redirect_path }]; } callback(null, response); }; Python def lambda_handler(event, context): response = event['Records'][0]['cf']['response'] request = event['Records'][0]['cf']['request'] ''' This function updates the HTTP status code in the response to 302, to redirect to another path (cache behavior) that has a different origin configured. Note the following: 1. The function is triggered in an origin response 2. The response status from the origin server is an error status code (4xx or 5xx) ''' if int(response['status']) >= 400 and int(response['status']) <= 599: redirect_path = '/plan-b/path?%s' % request['querystring'] response['status'] = 302 response['statusDescription'] = 'Found' # Drop the body as it is not required for redirects response['body'] = '' response['headers']['location'] = [ { 'key': 'Location', 'value': redirect_path}] return response Acesso ao corpo da solicitação: exemplos Os exemplos a seguir mostram como você pode usar o Lambda@Edge para trabalhar com solicitações POST. nota Para usar esses exemplos, você deve habilitar a opção include body (incluir corpo) na associação da função do Lambda da distribuição. Ele não é habilitado por padrão. Para habilitar essa configuração no console do CloudFront, marque a caixa de seleção Include Body (Incluir corpo) na Lambda Function Association (Associação de função do Lambda) . Para habilitar essa configuração na API do CloudFront ou com o CloudFormation, defina o campo IncludeBody como true em LambdaFunctionAssociation . Tópicos Exemplo: usar um acionador de solicitação para ler um formulário HTML Exemplo: usar um acionador de solicitação para modificar um formulário HTML Exemplo: usar um acionador de solicitação para ler um formulário HTML Essa função demonstra como você pode processar o corpo de uma solicitação POST gerada por um formulário HTML (formulário da web), como um formulário "entre em contato conosco". Por exemplo, você pode ter um formulário em HTML como o seguinte: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> No exemplo a seguir, a função deve ser acionada em uma solicitação de origem ou de um visualizador do CloudFront. Node.js 'use strict'; const querystring = require('querystring'); /** * This function demonstrates how you can read the body of a POST request * generated by an HTML form (web form). The function is triggered in a * CloudFront viewer request or origin request event type. */ exports.handler = (event, context, callback) => { const request = event.Records[0].cf.request; if (request.method === 'POST') { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send the data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we only log the form fields here. * You can put your custom logic here. For example, you can store the * fields in a database, such as Amazon DynamoDB, and generate a response * right from your Lambda@Edge function. */ for (let param in params) { console.log(`For "$ { param}" user submitted "$ { params[param]}".\n`); } } return callback(null, request); }; Python import base64 from urllib.parse import parse_qs ''' Say there is a POST request body generated by an HTML such as: <html> <form action="https://example.com" method="post"> Param 1: <input type="text" name="name1"><br> Param 2: <input type="text" name="name2"><br> input type="submit" value="Submit"> </form> </html> ''' ''' This function demonstrates how you can read the body of a POST request generated by an HTML form (web form). The function is triggered in a CloudFront viewer request or origin request event type. ''' def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send the data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} ''' For demonstration purposes, we only log the form fields here. You can put your custom logic here. For example, you can store the fields in a database, such as Amazon DynamoDB, and generate a response right from your Lambda@Edge function. ''' for key, value in params.items(): print("For %s use submitted %s" % (key, value)) return request Exemplo: usar um acionador de solicitação para modificar um formulário HTML Essa função demonstra como você pode modificar o corpo de uma solicitação POST gerada por um formulário HTML (formulário da web). A função é acionada em uma solicitação de origem ou de visualizador do CloudFront. Node.js 'use strict'; const querystring = require('querystring'); exports.handler = (event, context, callback) => { var request = event.Records[0].cf.request; if (request.method === 'POST') { /* Request body is being replaced. To do this, update the following /* three fields: * 1) body.action to 'replace' * 2) body.encoding to the encoding of the new data. * * Set to one of the following values: * * text - denotes that the generated body is in text format. * Lambda@Edge will propagate this as is. * base64 - denotes that the generated body is base64 encoded. * Lambda@Edge will base64 decode the data before sending * it to the origin. * 3) body.data to the new body. */ request.body.action = 'replace'; request.body.encoding = 'text'; request.body.data = getUpdatedBody(request); } callback(null, request); }; function getUpdatedBody(request) { /* HTTP body is always passed as base64-encoded string. Decode it. */ const body = Buffer.from(request.body.data, 'base64').toString(); /* HTML forms send data in query string format. Parse it. */ const params = querystring.parse(body); /* For demonstration purposes, we're adding one more param. * * You can put your custom logic here. For example, you can truncate long * bodies from malicious requests. */ params['new-param-name'] = 'new-param-value'; return querystring.stringify(params); } Python import base64 from urllib.parse import parse_qs, urlencode def lambda_handler(event, context): request = event['Records'][0]['cf']['request'] if request['method'] == 'POST': ''' Request body is being replaced. To do this, update the following three fields: 1) body.action to 'replace' 2) body.encoding to the encoding of the new data. Set to one of the following values: text - denotes that the generated body is in text format. Lambda@Edge will propagate this as is. base64 - denotes that the generated body is base64 encoded. Lambda@Edge will base64 decode the data before sending it to the origin. 3) body.data to the new body. ''' request['body']['action'] = 'replace' request['body']['encoding'] = 'text' request['body']['data'] = getUpdatedBody(request) return request def getUpdatedBody(request): # HTTP body is always passed as base64-encoded string. Decode it body = base64.b64decode(request['body']['data']) # HTML forms send data in query string format. Parse it params = { k: v[0] for k, v in parse_qs(body).items()} # For demonstration purposes, we're adding one more param # You can put your custom logic here. For example, you can truncate long # bodies from malicious requests params['new-param-name'] = 'new-param-value' return urlencode(params) O Javascript está desativado ou n� | 2026-01-13T09:30:35 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT0s5pBVyVWXL2EikesgVw8jzpst_zncmibWjO5JxVejO7PNRH03OW8ezvCKU_yj-lTWS37G1NP1YWnO0P5mmhLs151dqnVe8bIetamdjtqr7jE3T32t00VfQkfJJ3C2c5aCzwH6DTqDvGxp | 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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:35 |
https://penneo.com/da/law/ | Advokatydelser - 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 digital underskrift og reducer de administrative byrder Penneo hjælper jurister med at reducere den manuelle administration i forbindelse med dokumentunderskrifter, så de kan bruge mere tid på det, der virkelig betyder noget – at rådgive deres klienter. UDFORSK PENNEO Hvordan spænder manuelle processer ben for advokater? Manuelle processer kan holde jurister tilbage på flere kritiske områder. Det kan være en udfordring at tiltrække og fastholde talenter, da unge professionelle forventer, at teknologien understøtter fjernarbejde og fleksibelt samarbejde. Ud over potentielle personalemæssige udfordringer skaber manuelle arbejdsgange ineffektivitet – fx når dokumenter skal printes, underskrives i hånden, scannes og sendes frem og tilbage, hvilket både forsinker sagsbehandlingen og øger risikoen for fejl. Se, hvordan Penneo kan hjælpe dig Øg effektivitet ved at integrere Penneo med andre værktøjer Ved at integrere Penneo med dine eksisterende værktøjer kan du strømline arbejdsgange og øge effektiviteten. Penneo tilbyder integrationer med juridisk software som Advisor, Unik Advosys, EG AdvoPro og Legis 365 . Derudover kan du oprette tilpassede integrationer, der er skræddersyet til dine specifikke behov, ved hjælp af Penneos åbne API. Se alle vores integrationer Automatiser underskriftsprocesser og øg sikkerheden af dine dokumenter Penneo strømliner underskriftsprocessen for jurister ved at: Muliggøre sikre elektroniske signaturer med MitID, MitID Erhverv, pas eller andre eID’er Automatisere arbejdsgange – fremskynde underskrivelsen af aftalebreve, købsaftaler, fortrolighedsaftaler, databehandlingsaftaler og andre juridiske dokumenter Sikre sikkerhed og compliance – opbevar underskrevne dokumenter sikkert og beskyt dem mod uautoriseret adgang Se alle funktioner Optimér processer med Penneo Reducer manuel dataindtastning, forbedr nøjagtigheden, og spar tid med integrationer og automatiserede underskriftsflows. Penneo er GDPR-kompatibel, ISO 27001- og 27701-certificeret og bruger kryptering til at beskytte data og dokumenter. 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 fejl og øg effektiviteten med standardiserede processer for dokumentunderskrift – understøttet af detaljerede aktivitetslogfiler, der sikrer fuld sporbarhed. Giv dine kunder mulighed for at underskrive dokumenter digitalt – nemt, bekvemt og når det passer dem. 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 3000 virksomheder, herunder førende advokatfirmaer Opdag, hvordan Penneo kan hjælpe dig BOOK ET UFORPLIGTENDE 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:35 |
https://aws.amazon.com/vi/waf/ | Tường lửa ứng dụng web – Bảo vệ API web – AWS WAF – AWS Chuyển đến nội dung chính Filter: Tất cả English Liên hệ với chúng tôi AWS Marketplace Hỗ trợ Tài khoản của tôi Tìm kiếm Filter: Tất cả Đăng nhập vào bảng điều khiển Tạo tài khoản AWS Web Application Firewall Tổng quan Tính năng Giá cả Bắt đầu Tài nguyên Nhiều hơn nữa Sản phẩm › Bảo mật, danh tính và tuân thủ › AWS WAF Nhận 10 triệu yêu cầu kiểm soát bot phổ biến mỗi tháng với AWS Free Tier → AWS WAF Bảo vệ ứng dụng web khỏi các tình huống khai thác phổ biến Bắt đầu sử dụng AWS WAF Lợi ích của AWS WAF Tiết kiệm thời gian với quy tắc được quản lý Tiết kiệm thời gian với các quy tắc được quản lý để bạn có thể dành thêm thời gian xây dựng ứng dụng. Giám sát, chặn hoặc giới hạn tỷ lệ bot Dễ dàng theo dõi, chặn hoặc giới hạn tốc độ các bot thông thường và xâm lấn. Giảm các bước cấu hình bảo mật Tăng tốc cấu hình bảo mật phức tạp với giao diện hợp nhất giúp giảm độ phức tạp và các bước cấu hình triển khai bảo mật lên đến 80%. Khả năng hiển thị tập trung và có thể thực hiện Một giao diện toàn diện, duy nhất kết hợp các chức năng bảo mật cốt lõi với các biện pháp bảo vệ đối tác chuyên biệt để tăng cường khả năng hiển thị và kiểm soát bảo mật. Cách tiếp cận thống nhất này chuyển đổi dữ liệu bảo mật thành thông tin chi tiết có thể thực hiện được, loại bỏ ma sát hoạt động và đẩy nhanh phản ứng rủi ro. Tăng cường khả năng bảo mật Các gói bảo vệ được cấu hình sẵn tận dụng chuyên môn bảo mật của AWS để cung cấp các mẫu bảo vệ tức thì cho các ngành và loại khối lượng công việc cụ thể như API, ứng dụng PHP và dịch vụ web. Các mẫu này liên tục được tối ưu hóa để đảm bảo bảo mật cập nhật mà không yêu cầu chuyên môn triển khai sâu sắc. Nhận các khuyến nghị bảo mật liên tục để tăng cường tư thế bảo mật tổng thể. Tại sao nên chọn AWS WAF? Với AWS WAF, bạn có thể tạo quy tắc bảo mật giúp kiểm soát lưu lượng bot và chặn các mẫu tấn công thường gặp, chẳng hạn như hoạt động đưa SQL vào hoặc chèn tập lệnh liên trang web (XSS). Phát Trường hợp sử dụng Lọc lưu lượng truy cập web Tạo quy tắc để lọc yêu cầu web dựa trên các điều kiện như địa chỉ IP, phần tiêu đề và nội dung HTTP hoặc URI tùy chỉnh. Tìm hiểu thêm về quá trình tạo quy tắc Ngăn chặn hoạt động gian lận chiếm đoạt tài khoản Giám sát trang đăng nhập trên ứng dụng của bạn để tìm kiếm truy cập trái phép vào tài khoản người dùng bằng thông tin chứng thực bị xâm phạm. Tìm hiểu thêm về quá trình ngăn chặn gian lận Bảo vệ DDoS lớp 7 tự động Được thiết kế để liên tục theo dõi và tự động giảm thiểu các sự kiện từ chối dịch vụ phân tán (DDoS) lớp ứng dụng (lớp 7) trong vòng vài giây. Thực hiện bảo mật nhanh chóng Tự tin khởi chạy các ứng dụng mới bằng cách sử dụng thiết lập giới thiệu có hướng dẫn hợp lý với giao diện một trang để kích hoạt các mặc định bảo mật được cấu hình sẵn phù hợp với nhu cầu của bạn. Tăng cường khả năng bảo mật Thông qua các gói quy tắc do chuyên gia quản lý, khả năng hiển thị hợp nhất và các đề xuất liên tục, bạn có được sự bảo vệ ngay lập tức để tối ưu hóa tư thế bảo mật của mình. Bắt đầu sử dụng AWS WAF Bắt đầu sử dụng AWS WAF Khám phá AWS WAF Liên hệ với chuyên gia Liên hệ với chúng tôi Tạo tài khoản AWS Tìm hiểu AWS là gì? Điện toán đám mây là gì? AI trợ lý ảo là gì? Trung tâm khái niệm về điện toán đám mây Khả năng bảo mật của Đám mây AWS Thông tin mới Blog Thông cáo báo chí Tài nguyên Bắt đầu Đào tạo Trung tâm tin cậy AWS Thư viện giải pháp AWS Trung tâm kiến trúc Câu hỏi thường gặp về sản phẩm và kỹ thuật Báo cáo của chuyên gia phân tích Đối tác AWS Nhà phát triển Trung tâm dành cho nhà kiến tạo SDK và Công cụ .NET trên AWS Python trên AWS Java trên AWS PHP trên AWS JavaScript trên AWS Trợ giúp Liên hệ với chúng tôi Gửi phiếu yêu cầu hỗ trợ AWS re:Post Trung tâm kiến thức Tổng quan về Hỗ trợ AWS Nhận trợ giúp từ chuyên gia Khả năng truy cập AWS Pháp lý English Trở lại đầu trang Amazon là nhà tuyển dung mang lại cơ hội làm việc bình đẳng: Dân tộc thiểu số/Nữ giới/Người khuyết tật/Cựu chiến binh/Bản dạng giới/Xuhướng tình dục/Tuổi tác. x facebook linkedin instagram twitch youtube podcasts email Quyền riêng tư Điều khoản áp dụng cho trang web Tùy chọn cookie © 2026, Amazon Web Services, Inc. hoặc các chi nhánh của Amazon. Bảo lưu mọi quyền. | 2026-01-13T09:30:35 |
https://penneo.com/da/use-cases/eidas-compliance/ | Skab tillid med e-underskrifter i overensstemmelse med eIDAS 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Å Skab tillid med e-signatur der overholder eIDAS Få sikkerhed for, at dine e-signaturer er juridisk bindende og gyldige i hele EU. Med Penneo kan du nemt underskrive med en avanceret elektronisk underskrift (AdES) ved brug af MitID – eller med en kvalificeret elektronisk underskrift (QES) via itsme® eller pas. BOOK ET MØDE Hvorfor vælge Penneo? Underskriv dokumenter online sikkert og effektivt Dokumenter, du kan stole på – også efter underskrift Avancerede og kvalificerede elektroniske underskrifter bygger på PKI-teknologi, som beskytter dokumentets integritet og forhindrer ændringer efter underskrivning. Underskriften havner hos den rette person Underskrifterne er personligt knyttet til underskriveren . Du kan identificere, hvem der har skrevet under – så du undgår tvivl om, hvem der har godkendt hvad. Stærk dokumentation, hvis underskriften bliver betvivlet Avancerede og kvalificerede elektroniske underskrifter gør det nærmest umuligt for nogen at benægte, at de har underskrevet . Det giver dig solid juridisk sikkerhed, hvis der opstår uenighed. 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. Hvilke typer elektroniske underskrifter findes der ifølge eIDAS? eIDAS-forordningen opererer med tre typer elektroniske underskrifter – hver med forskellig grad af juridisk gyldighed og sikkerhed: Simpel elektronisk signatur (SES): En simpel elektronisk signatur er juridisk gyldig, men giver kun et lavt niveau af sikkerhed i forhold til, hvem der har underskrevet, og om dokumentet er blevet ændret efterfølgende. Avanceret elektronisk signatur (AdES): En avanceret elektronisk signatur giver en højere grad af sikkerhed og juridisk værdi end en simpel underskrift. Den er typisk knyttet til et digitalt certifikat og gør det muligt at identificere underskriveren og sikre, at dokumentet ikke er blevet ændret efter underskrivning. Kvalificeret elektronisk signatur (QES): En kvalificeret elektronisk signatur har samme retsvirkning som en håndskrevet underskrift i hele EU. Den tilbyder det højeste niveau af juridisk sikkerhed og kræver, at underskriveren anvender en kvalificeret signeringsløsning udstedt af en godkendt udbyder (QTSP). 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. X/Twitter 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 Tryghed med en kvalificeret tillidstjenesteudbyder Penneo er godkendt som kvalificeret tillidstjenesteudbyder (QTSP) og er officielt opført på EU’s liste over godkendte udbydere. Denne status bekræfter, at Penneo lever op til eIDAS-forordningens strenge krav og har tilladelse til at levere kvalificerede tillidstjenester – hvilket sikrer den højeste grad af sikkerhed og juridisk gyldighed ved digitale transaktioner i hele EU. Penneo giver dig mulighed for at oprette kvalificerede elektroniske underskrifter (QES) via itsme®, norsk BankID, .beID eller dit pas, samt avancerede elektroniske underskrifter med MitID, MitID Erhverv eller svensk BankID. Lær mer DEAS sparer 385 timer om måneden med Penneo Vi har over 3.000 kontrakter, der kræver underskrifter hver måned. Med Penneos digitale signaturløsning har vi sparet 385 arbejdstimer om måneden. Som resultat kan vores medarbejdere nu fokusere på at servicere vores kunder og lejere bedre – i stedet for at bruge tid på manuelle, administrative opgaver. — Thomas B. Skræddergaard, IT-chef hos DEAS Læs mere om samarbejdet 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 Ofte stillede spørgsmål Er e-signaturer oprettet via Penneo juridisk bindende? Ja, e-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). 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 e-signatur er gyldig? Du kan verificere en elektronisk 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 Hvad er forskellen på en simpel e-signatur og en digital signatur? En simpel e-signatur (SES) kan være så enkel som at indtaste et navn eller klikke på en knap. Det er nemt, men giver kun begrænset sikkerhed og retsgyldighed. En digital signatur – enten avanceret eller kvalificeret – giver langt højere sikkerhed og juridisk vægt i henhold til eIDAS-forordningen. Læs mere om forskellen på digitale og elektroniske signaturer 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 . Bliv klogere på elektroniske underskrifter Ny til digitale underskrifter? Overvej disse 9 punkter først Læs mere Hvad betyder eIDAS 2.0 for digitale transaktioner? Læs mere eIDAS-forordningen: Elektronisk identifikation og tillidstjenester i EU 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:35 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-event-structure.html#lambda-event-structure-response | Struktur acara Lambda @Edge - Amazon CloudFront Struktur acara Lambda @Edge - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Pemilihan asal dinamis Permintaan acara Peristiwa respon Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Struktur acara Lambda @Edge Topik berikut menjelaskan objek peristiwa permintaan dan respons yang CloudFront diteruskan ke fungsi Lambda @Edge saat dipicu. Topik Pemilihan asal dinamis Permintaan acara Peristiwa respon Pemilihan asal dinamis Anda dapat menggunakan pola jalur dalam perilaku cache untuk merutekan permintaan ke asal berdasarkan jalur dan nama objek yang diminta, seperti images/*.jpg . Menggunakan Lambda@Edge, Anda juga dapat merutekan permintaan ke asal berdasarkan karakteristik lain, seperti nilai-nilai dalam header permintaan. Ada sejumlah cara agar pemilihan asal dinamis ini dapat berguna. Misalnya, Anda dapat mendistribusikan permintaan lintas asal-usul di area geografis yang berbeda untuk membantu menyeimbangkan beban global. Atau Anda dapat secara selektif merutekan permintaan ke asal-usul berbeda yang masing-masing melayani fungsi tertentu: penanganan bot, optimalisasi SEO, autentikasi, dan sebagainya. Untuk contoh kode yang mendemonstrasikan cara menggunakan fitur ini, lihat Pemilihan asal dinamis berbasis konten - contoh . Dalam peristiwa permintaan CloudFront asal, origin objek dalam struktur peristiwa berisi informasi tentang asal yang akan diarahkan ke permintaan, berdasarkan pola jalur. Anda dapat memperbarui nilai di origin mengajukan keberatan untuk mengirimkan permintaan ke negara asal yang berbeda. Saat Anda memperbarui origin objek, Anda tidak perlu menentukan asal dalam distribusi. Anda juga dapat mengganti objek asal Amazon S3 dengan objek asal kustom, dan sebaliknya. Namun, Anda hanya dapat menentukan asal tunggal per permintaan; asal kustom atau asal Amazon S3, tetapi tidak keduanya. Permintaan acara Topik berikut menunjukkan struktur objek yang CloudFront diteruskan ke fungsi Lambda untuk acara permintaan penampil dan asal . Contoh-contoh ini menunjukkan GET tanpa isi. Berikut ini contoh adalah daftar semua bidang yang mungkin muncul dalam peristiwa permintaan penampil dan asal. Topik Contoh permintaan penampil Contoh permintaan asal Permintaan bidang acara Contoh permintaan penampil Contoh berikut menunjukkan objek acara permintaan penampil. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "viewer-request", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "host": [ { "key": "Host", "value": "d111111abcdef8.cloudfront.net" } ], "user-agent": [ { "key": "User-Agent", "value": "curl/7.66.0" } ], "accept": [ { "key": "accept", "value": "*/*" } ] }, "method": "GET", "querystring": "", "uri": "/" } } } ] } Contoh permintaan asal Contoh berikut menunjukkan objek peristiwa permintaan asal usul. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "origin-request", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "x-forwarded-for": [ { "key": "X-Forwarded-For", "value": "203.0.113.178" } ], "user-agent": [ { "key": "User-Agent", "value": "Amazon CloudFront" } ], "via": [ { "key": "Via", "value": "2.0 2afae0d44e2540f472c0635ab62c232b.cloudfront.net (CloudFront)" } ], "host": [ { "key": "Host", "value": "example.org" } ], "cache-control": [ { "key": "Cache-Control", "value": "no-cache" } ] }, "method": "GET", "origin": { "custom": { "customHeaders": { }, "domainName": "example.org", "keepaliveTimeout": 5, "path": "", "port": 443, "protocol": "https", "readTimeout": 30, "responseCompletionTimeout": 30, "sslProtocols": [ "TLSv1", "TLSv1.1", "TLSv1.2" ] } }, "querystring": "", "uri": "/" } } } ] } Permintaan bidang acara Meminta data objek peristiwa dimuat dalam dua subobjek: config ( Records.cf.config ) and request ( Records.cf.request ). Daftar berikut menjelaskan setiap bidang subobject. Bidang di objek konfigurasi Daftar berikut menjelaskan bidang dalam config objek ( Records.cf.config ). distributionDomainName (hanya baca) Nama domain distribusi yang terkait dengan permintaan. distributionID (hanya baca) ID distribusi yang terkait dengan permintaan. eventType (hanya baca) Jenis pemicu yang terkait dengan permintaan: viewer-request atau origin-request . requestId (hanya baca) String terenkripsi yang secara unik mengidentifikasi permintaan. viewer-to-CloudFront requestId Nilai juga muncul di log CloudFront akses sebagai x-edge-request-id . Untuk informasi selengkapnya, lihat Akses log (log standar) dan Bidang file log . Bidang di objek permintaan Daftar berikut menjelaskan bidang dalam request objek ( Records.cf.request ). clientIp (hanya baca) Alamat IP penampil yang membuat permintaan. Jika penampil menggunakan proksi HTTP atau penyeimbang beban untuk mengirim permintaan, nilainya adalah alamat IP proksi atau pengimbang beban. header (baca/tulis) Header pada permintaan. Perhatikan hal-hal berikut: Kunci dalam headers objek adalah versi huruf kecil nama header HTTP standar. Menggunakan tombol huruf kecil memberi Anda akses huruf kecil ke nilai header. Setiap objek header (misalnya, headers["accept"] atau headers["host"] ) adalah serangkaian pasangan utama-nilai. Untuk header tertentu, larik berisi satu pasangan nilai kunci untuk setiap nilai dalam permintaan. key berisi nama case-sensitive dari header seperti yang muncul dalam permintaan HTTP; misalnya,,, Host User-Agent , X-Forwarded-For Cookie , dan sebagainya. value berisi nilai header sebagaimana muncul dalam permintaan HTTP. Ketika fungsi Lambda Anda menambahkan atau memodifikasi header permintaan dan Anda tidak menyertakan bidang header key , Lambda @Edge secara otomatis menyisipkan header key menggunakan nama header yang Anda berikan. Terlepas dari bagaimana Anda memformat nama header, kunci header yang disisipkan secara otomatis diformat dengan kapitalisasi awal untuk setiap bagian, dipisahkan oleh tanda hubung (-). Misalnya, Anda dapat menambahkan header seperti berikut, tanpa header key : "user-agent": [ { "value": "ExampleCustomUserAgent/1.X.0" } ] Dalam contoh ini, Lambda@Edge secara otomatis memasukkan "key": "User-Agent" . Untuk informasi tentang pembatasan penggunaan header, lihat Pembatasan pada fungsi edge . method (hanya baca) Metode HTTP permintaan. querystring (baca/tulis) String kueri, jika ada, dalam permintaan. Jika permintaan tidak menyertakan string kueri, objek acara masih menyertakan querystring dengan nilai kosong. Untuk informasi selengkapnya tentang string kueri, lihat Konten cache berdasarkan parameter string kueri . uri (baca/tulis) Jalur relatif objek yang diminta. Jika fungsi Lambda Anda memodifikasi uri perhatikan hal-hal berikut: uri nilai harus dimulai dengan garis miring ke depan (/). Saat fungsi mengubah uri yang mengubah objek yang diminta oleh penampil. Ketika fungsi mengubah uri nilai, itu tidak mengubah perilaku cache untuk permintaan atau asal permintaan yang dikirim. body (baca/tulis) Isi permintaan HTTP. body struktur dapat memuat kolom berikut: inputTruncated (hanya baca) Bendera Boolean yang menunjukkan apakah tubuh dijejali Lambda@Edge. Untuk informasi selengkapnya, lihat Pembatasan pada isi permintaan dengan opsi sertakan isi . action (baca/tulis) Tindakan yang ingin Anda lakukan dengan tubuh. Opsi untuk action adalah sebagai berikut: read-only: Ini adalah pengaturan default. Saat mengembalikan respons dari fungsi Lambda, jika action adalah hanya baca, Lambda@Edge mengabaikan setiap perubahan pada encoding atau data . replace: Tentukan ini saat Anda ingin mengganti tubuh yang dikirim ke asal. encoding (baca/tulis) Pengodean untuk tubuh. Saat Lambda@Edge mengekspos tubuh ke fungsi Lambda, pertama-tama tubuh berubah menjadi base64-encoding. Jika Anda memilih replace untuk action untuk mengganti tubuh, Anda dapat memilih untuk menggunakan pengodean base64 (default) atau text . Jika Anda menentukan encoding sebagai base64 tetapi tubuh tidak validbase64, CloudFront mengembalikan kesalahan. data (baca/tulis) Isi konten permintaan. origin (baca/tulis) (hanya peristiwa awal) Asal pengiriman permintaan ke. origin Struktur harus berisi tepat satu asal , yang dapat berupa asal khusus atau asal Amazon S3. Bergantung pada jenis asal yang Anda tentukan (asal kustom atau Amazon S3), Anda harus menentukan bidang berikut dalam permintaan Anda: customHeaders (baca/tulis) (kustom dan berasal dari Amazon S3) (Opsional) Anda dapat menyertakan header khusus dengan permintaan dengan menentukan nama header dan pasangan nilai untuk setiap header kustom. Anda tidak dapat menambahkan header yang tidak diizinkan, dan header dengan nama yang sama tidak dapat hadir. Records.cf.request.headers Catatan tentang header permintaan juga berlaku untuk header kustom. Untuk informasi lebih lanjut, lihat Header khusus yang tidak CloudFront dapat ditambahkan ke permintaan asal dan Pembatasan pada fungsi edge . domainName (baca/tulis) (kustom dan berasal dari Amazon S3) Nama domain asal. Nama domain tidak bisa kosong. Untuk asal kustom – Tentukan nama domain DNS, seperti www.example.com . Nama domain tidak dapat menyertakan titik dua (:), dan tidak bisa menjadi alamat IP. Nama domain dapat terdiri dari hingga 253 karakter. Untuk asal Amazon S3 – Tentukan nama domain DNS bucket Amazon S3, seperti amzn-s3-demo-bucket.s3.eu-west-1.amazonaws.com . Nama bisa sampai 128 karakter dan harus berupa huruf kecil. path (baca/tulis) (kustom dan berasal dari Amazon S3) Jalur direktori di tempat asal permintaan harus menemukan konten. Jalur harus dimulai dengan garis miring (/) tetapi tidak boleh diakhiri dengan satu (misalnya, seharusnya tidak diakhiri dengan example-path/ ). Hanya untuk asal kustom, alur harus dienkode URL dan memiliki panjang maksimum 255 karakter. keepaliveTimeout (baca/tulis) (hanya asal sesuai undang-undang) Berapa lama, dalam hitungan detik, yang CloudFront harus mencoba mempertahankan koneksi ke asal setelah menerima paket terakhir dari respons. Nilainya harus berupa angka dari 1-120, inklusif. port (baca/tulis) (hanya asal sesuai undang-undang) Port yang CloudFront harus terhubung ke asal kustom Anda. Port harus 80, 443, atau nomor dalam kisaran 1024–65535, termasuk. protocol (baca/tulis) (hanya asal sesuai undang-undang) Protokol koneksi yang CloudFront harus digunakan saat menghubungkan ke asal Anda. Nilai dapat berupa http atau https . readTimeout (baca/tulis) (kustom dan berasal dari Amazon S3) Berapa lama, dalam hitungan detik, CloudFront harus menunggu tanggapan setelah mengirim permintaan ke asal Anda. Ini juga menentukan berapa lama CloudFront harus menunggu setelah menerima paket tanggapan sebelum menerima paket berikutnya. Nilainya harus berupa angka dari 1-120, inklusif. Jika Anda membutuhkan kuota yang lebih tinggi, lihat Batas waktu respons per asal . responseCompletionTimeout (baca/tulis) (kustom dan berasal dari Amazon S3) Waktu (dalam detik) permintaan dari CloudFront ke asal dapat tetap terbuka dan menunggu tanggapan. Jika respons lengkap tidak diterima dari asal saat ini, CloudFront akhiri koneksi. Nilai untuk responseCompletionTimeout harus sama dengan atau lebih besar dari nilai untuk readTimeout . Jika Anda menetapkan nilai ini ke 0, itu akan menghapus nilai sebelumnya yang Anda tetapkan dan kembali ke default. Anda juga dapat melakukannya dengan menghapus responseCompletionTimeout bidang dari permintaan acara. sslProtocols (baca/tulis) (hanya asal sesuai undang-undang) SSL/TLS Protokol minimum yang CloudFront dapat digunakan saat membuat koneksi HTTPS dengan asal Anda. Nilai dapat berupa: TLSv1.2 , TLSv1.1 , TLSv1 , atau SSLv3 . authMethod (baca/tulis) (hanya asal-usul Amazon S3) Jika Anda menggunakan identitas akses asal (OAI) , setel bidang ini ke origin-access-identity . Jika Anda tidak menggunakan OAI, atur ke none . Jika Anda mengatur authMethod untuk origin-access-identity , ada beberapa persyaratan: Anda harus menentukan region (lihat bidang berikut). Anda harus menggunakan OAI yang sama ketika Anda mengubah permintaan dari satu asal Amazon S3 ke yang lain. Anda tidak dapat menggunakan OAI saat mengubah permintaan dari asal kustom ke asal Amazon S3. catatan Bidang ini tidak mendukung kontrol akses asal (OAC) . region (baca/tulis) (hanya asal-usul Amazon S3) AWS Wilayah ember Amazon S3 Anda. Ini hanya diperlukan ketika Anda mengatur authMethod untuk origin-access-identity . Peristiwa respon Topik berikut menunjukkan struktur objek yang CloudFront diteruskan ke fungsi Lambda untuk penampil dan peristiwa respons asal . Berikut ini contoh adalah daftar semua bidang yang mungkin muncul di penampil dan kejadian respons asal. Topik Contoh respon asal Contoh respons penampil Bidang acara respons Contoh respon asal Contoh berikut menunjukkan objek peristiwa respons asal usul. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "origin-response", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "x-forwarded-for": [ { "key": "X-Forwarded-For", "value": "203.0.113.178" } ], "user-agent": [ { "key": "User-Agent", "value": "Amazon CloudFront" } ], "via": [ { "key": "Via", "value": "2.0 8f22423015641505b8c857a37450d6c0.cloudfront.net (CloudFront)" } ], "host": [ { "key": "Host", "value": "example.org" } ], "cache-control": [ { "key": "Cache-Control", "value": "no-cache" } ] }, "method": "GET", "origin": { "custom": { "customHeaders": { }, "domainName": "example.org", "keepaliveTimeout": 5, "path": "", "port": 443, "protocol": "https", "readTimeout": 30, "responseCompletionTimeout": 30, "sslProtocols": [ "TLSv1", "TLSv1.1", "TLSv1.2" ] } }, "querystring": "", "uri": "/" }, "response": { "headers": { "access-control-allow-credentials": [ { "key": "Access-Control-Allow-Credentials", "value": "true" } ], "access-control-allow-origin": [ { "key": "Access-Control-Allow-Origin", "value": "*" } ], "date": [ { "key": "Date", "value": "Mon, 13 Jan 2020 20:12:38 GMT" } ], "referrer-policy": [ { "key": "Referrer-Policy", "value": "no-referrer-when-downgrade" } ], "server": [ { "key": "Server", "value": "ExampleCustomOriginServer" } ], "x-content-type-options": [ { "key": "X-Content-Type-Options", "value": "nosniff" } ], "x-frame-options": [ { "key": "X-Frame-Options", "value": "DENY" } ], "x-xss-protection": [ { "key": "X-XSS-Protection", "value": "1; mode=block" } ], "content-type": [ { "key": "Content-Type", "value": "text/html; charset=utf-8" } ], "content-length": [ { "key": "Content-Length", "value": "9593" } ] }, "status": "200", "statusDescription": "OK" } } } ] } Contoh respons penampil Contoh berikut menunjukkan objek acara respons penampil. { "Records": [ { "cf": { "config": { "distributionDomainName": "d111111abcdef8.cloudfront.net", "distributionId": "EDFDVBD6EXAMPLE", "eventType": "viewer-response", "requestId": "4TyzHTaYWb1GX1qTfsHhEqV6HUDd_BzoBZnwfnvQc_1oF26ClkoUSEQ==" }, "request": { "clientIp": "203.0.113.178", "headers": { "host": [ { "key": "Host", "value": "d111111abcdef8.cloudfront.net" } ], "user-agent": [ { "key": "User-Agent", "value": "curl/7.66.0" } ], "accept": [ { "key": "accept", "value": "*/*" } ] }, "method": "GET", "querystring": "", "uri": "/" }, "response": { "headers": { "access-control-allow-credentials": [ { "key": "Access-Control-Allow-Credentials", "value": "true" } ], "access-control-allow-origin": [ { "key": "Access-Control-Allow-Origin", "value": "*" } ], "date": [ { "key": "Date", "value": "Mon, 13 Jan 2020 20:14:56 GMT" } ], "referrer-policy": [ { "key": "Referrer-Policy", "value": "no-referrer-when-downgrade" } ], "server": [ { "key": "Server", "value": "ExampleCustomOriginServer" } ], "x-content-type-options": [ { "key": "X-Content-Type-Options", "value": "nosniff" } ], "x-frame-options": [ { "key": "X-Frame-Options", "value": "DENY" } ], "x-xss-protection": [ { "key": "X-XSS-Protection", "value": "1; mode=block" } ], "age": [ { "key": "Age", "value": "2402" } ], "content-type": [ { "key": "Content-Type", "value": "text/html; charset=utf-8" } ], "content-length": [ { "key": "Content-Length", "value": "9593" } ] }, "status": "200", "statusDescription": "OK" } } } ] } Bidang acara respons Data objek peristiwa respons dimuat dalam tiga subobjek: config ( Records.cf.config ), request ( Records.cf.request ), dan response ( Records.cf.response ). Untuk informasi lebih lanjut tentang bidang di objek permintaan, lihat Bidang di objek permintaan . Daftar berikut menjelaskan bidang dalam config dan response subobjects. Bidang di objek konfigurasi Daftar berikut menjelaskan bidang dalam config objek ( Records.cf.config ). distributionDomainName (hanya baca) Nama domain distribusi yang terkait dengan respons. distributionID (hanya baca) ID distribusi yang terkait dengan respons. eventType (hanya baca) Jenis pemicu yang terkait dengan respons: origin-response atau viewer-response . requestId (hanya baca) String terenkripsi yang secara unik mengidentifikasi viewer-to-CloudFront permintaan yang terkait dengan respons ini. requestId Nilai juga muncul di log CloudFront akses sebagai x-edge-request-id . Untuk informasi selengkapnya, lihat Akses log (log standar) dan Bidang file log . Bidang di objek respons Daftar berikut menjelaskan bidang dalam response objek ( Records.cf.response ). Untuk informasi tentang penggunaan fungsi Lambda@Edge untuk membuat respons HTTP, lihat Hasilkan respons HTTP dalam pemicu permintaan . headers (baca/tulis) Header dalam respons. Perhatikan hal-hal berikut: Kunci dalam headers objek adalah versi huruf kecil nama header HTTP standar. Menggunakan tombol huruf kecil memberi Anda akses huruf kecil ke nilai header. Setiap objek header (misalnya, headers["content-type"] atau headers["content-length"] ) adalah serangkaian pasangan utama-nilai. Untuk header tertentu, larik berisi satu pasangan nilai kunci untuk setiap nilai dalam respons. key berisi nama case-sensitive header seperti yang muncul dalam respons HTTP; misalnya,,, Content-Type Content-Length Cookie , dan sebagainya. value berisi nilai header sebagaimana muncul dalam respons HTTP. Ketika fungsi Lambda Anda menambahkan atau memodifikasi header respons dan Anda tidak menyertakan bidang header key , Lambda @Edge secara otomatis menyisipkan header key menggunakan nama header yang Anda berikan. Terlepas dari bagaimana Anda memformat nama header, kunci header yang disisipkan secara otomatis diformat dengan kapitalisasi awal untuk setiap bagian, dipisahkan oleh tanda hubung (-). Misalnya, Anda dapat menambahkan header seperti berikut, tanpa header key : "content-type": [ { "value": "text/html;charset=UTF-8" } ] Dalam contoh ini, Lambda@Edge secara otomatis memasukkan "key": "Content-Type" . Untuk informasi tentang pembatasan penggunaan header, lihat Pembatasan pada fungsi edge . status Kode status HTTP dari respons. statusDescription Deskripsi status HTTP untuk respons. Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Hapus fungsi dan replika Bekerja dengan permintaan dan tanggapan 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:35 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT3KcD82fNRVc24dI_tN63VhZx_Niwcx96TOUk_vcxy1GcV_LRCK_e5etAJFd9uGv8uzSrvYfmPuQjrocMmLgfEzysiY2GU53kMcvtttEm6vLrLaz8xcuZFcbpbKC7govFPS-hjYFS9m1FQM | 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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:35 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT2IvyiGiIX-j-C9prkovyldF2UyBFMEpgdptlGwyv-t5CU-YAHMU8jIZVKwb62ZB2kBFTpfSPe8wVm1j8nV44fltWAV1bFCrvY-9shbdebnCxPcZJHnTFsMElC2GfWgbYrjRDcEBBvCN_Aw | 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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:35 |
https://www.visma.com/voiceofvisma/ep-13-building-partnerships-beyond-software-with-daniel-ognoy-kaspersen | Ep 13: Building partnerships beyond software with Daniel Ognøy Kaspersen Who we are About us Connected by software – driven by people Become a Visma company Join our family of thriving SaaS companies Technology and AI at Visma Innovation with customer value at its heart Our sponsorship Team Visma | Lease a Bike Sustainability A better impact through software Contact us Find the right contact information What we offer Cloud software We create brilliant ways to work For medium businesses Lead your business with clarity For small businesses Start, run and grow with ease For public sector Empower efficient societies For accounting offices Build your dream accounting office For partners Help us keep customers ahead For investors For investors Latest results, news and strategy Financials Key figures, quarterly and annual results Events Financial calendar Governance Policies, management, board and owners Careers Careers at Visma Join the business software revolution Locations Find your nearest office Open positions Turn your passion into a career Resources News For small businesses Cloud accounting software built for small businesses Who we are About us Technology and AI at Visma Sustainability Become a Visma company Our sponsorship What we offer Cloud software For small businesses For accounting offices For enterprises Public sector For partners For investors Overview Financials Governance News and press Events Careers Careers at Visma Open positions Hubs Resources Blog Visma Developer Trust Centre News Press releases Team Visma | Lease a Bike Podcast Ep 13: Building partnerships beyond software with Daniel Ognøy Kaspersen Voice of Visma February 19, 2025 Spotify Created with Sketch. YouTube Apple Podcasts Amazon Music <iframe style="border-radius:12px" src="https://www.youtube.com/embed/TK9GKZAz6T8?si=BsBKzRvWI1PunGNZ" width="100%" height="500" frameBorder="0" allowfullscreen="" allow="autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture" loading="lazy"></iframe> About the episode What does it look like when an accounting software company delivers more than just great software? Today, Daniel joins host Petteri Rantamäki to explore the Tripletex partner programme – where accounting offices and software work together to create a system in which everyone benefits. From hands-on support to events and roadshows, they unpack the relationship between service and software, and why true partnership matters. Share More from Voice of Visma We're sitting down with leaders and colleagues from around Visma to share their stories, industry knowledge, and valuable career lessons. With the Voice of Visma podcast, we’re bringing our people and culture closer to you. Get to know the podcast Ep 22: Building, learning, and accelerating growth in the SaaS world with Maxin Schneider Entrepreneurial leadership often grows through experience, and Maxin Schneider has seen that up close. Read more Ep 21: How DEI fuels business success with Iveta Bukane Why DEI isn't just a moral imperative—it’s a business necessity. Read more Ep 20: Driving tangible sustainability outcomes with Freja Landewall Discover how ESG goes far beyond the environment, encompassing people, governance, and the long-term resilience of business. Read more Ep 19: Future-proofing public services in Sweden with Marie Ceder Between demographic changes, the rise in AI, and digitalisation, the public sector is at a pivotal moment. Read more Ep 18: Making inclusion part of our everyday work with Ida Algotsson What does inclusion truly mean at Visma – not just as values, but as everyday actions? Read more Ep 17: Sustainability at the heart of business with Robin Åkerberg Honouring our responsibility goes well beyond the numbers – it starts with a shared purpose and values. Read more Ep 16: Innovation for the public good with Kasper Lyhr Serving the public sector goes way beyond software – it’s about shaping the future of society as a whole. Read more Ep 15: Leading with transparency and vulnerability with Ellen Sano What does it mean to be a “firestarter” in business? Read more Ep 14: Women, innovation, and the future of Visma with Merete Hverven Our CEO, Merete, knows that great leadership takes more than just hard work – it takes vision. Read more Ep 13: Building partnerships beyond software with Daniel Ognøy Kaspersen What does it look like when an accounting software company delivers more than just great software? Read more Ep 12: AI in the accounting sphere with Joris Joppe Artificial intelligence is changing industries across the board, and accounting is no exception. But in such a highly specialised field, what does change actually look like? Read more Ep 11: From Founder to Segment Director with Ari-Pekka Salovaara Ari-Pekka is a serial entrepreneur who joined Visma when his company was acquired in 2010. He now leads the small business segment. Read more Ep 10: When brave choices can save a company with Charlotte von Sydow What’s it like stepping in as the Managing Director for a company in decline? Read more Ep 09: Revolutionising tax tech in Italy with Enrico Mattiazzi and Vito Lomele Take one look at their product, their customer reviews, or their workplace awards, and it’s clear why Fiscozen leads Italy’s tax tech scene. Read more Ep 08: Navigating the waters of entrepreneurship with Steffen Torp When it comes to being an entrepreneur, the journey is as personal as it is unpredictable. Read more Ep 07: The untold stories of Visma with Øystein Moan What did Visma look like in its early days? Are there any decisions our former CEO would have made differently? Read more Ep 06: Measure what matters: Employee engagement with Vibeke Müller Research shows that having engaged, happy employees is so important for building a great company culture and performing better financially. Read more Ep 05: Our Team Visma | Lease a Bike sponsorship with Anne-Grethe Thomle Karlsen It’s one thing to sponsor the world’s best cycling team; it’s a whole other thing to provide software and expertise that helps them do what they do best. Read more Ep 04: “How do you make people care about security?” with Joakim Tauren With over 700 applications across the Visma Group (and counting!), cybersecurity is make-or-break for us. Read more Ep 03: The human side of enterprise with Yvette Hoogewerf As a software company, our products are central to our business… but that’s only one part of the equation. Read more Ep 02: From Management Trainee to CFO with Stian Grindheim How does someone work their way up from Management Trainee to CFO by the age of 30? And balance fatherhood alongside it all? Read more Ep 01: An optimistic look at the future of AI with Jacob Nyman We’re all-too familiar with the fears surrounding artificial intelligence. So today, Jacob and Johan are flipping the script. Read more (Trailer) Introducing: Voice of Visma These are the stories that shape us... and the reason Visma is unlike anywhere else. Read more Visma Software International AS Organisation number: 980858073 MVA (Foretaksregisteret/The Register of Business Enterprises) Main office Karenslyst allé 56 0277 Oslo Norway Postal address PO box 733, Skøyen 0214 Oslo Norway visma@visma.com Visma on LinkedIn Who we are About us Technology at Visma Sustainability Become a Visma company Our sponsorship Contact us What we offer For small businesses For accounting offices For medium businesses For public sector For partners e-invoicing Digital signature For investors Overview Financials Governance Events Careers Careers at Visma Open positions Hubs Resources Blog Trust Centre Community News Press ©️ 2026 Visma Privacy policy Cookie policy Whistleblowing Cookies settings Transparency Act Change country | 2026-01-13T09:30:35 |
https://penneo.com/da/blog/ | Vidensunivers - 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Å VIDENSUNIVERS Alt, hvad du har brug for at vide om digital tillid Her får du guides, knivskarp juridisk viden og perspektiver fra vores eksperter. Du kan også se hvordan andre virksomheder bruger Penneo Sign til at gøre hverdagen lettere mens juraen overholdes. Nyt fra Penneo Hemmeligheden bag en stærk revision: Skab værdi, undgå manuelt besvær Læs mere Produktopdateringer fra Q4 2025: Hurtigere afsendelse, global QES & API-opdateringer Læs mere Penneo QES: Højeste juridiske gyldighed og dokumenteret sikkerhed Læs mere Filtrér efter indholdstype ↓ Blogindlæg Guides og e-bøger Referencer Produktopdateringer Alle Digital transformation Digitale tillidstjenester Signaturer og juridisk gyldighed Sikkerhed og overholdelse Vækst og forretning Send dokumenter til underskrift på få sekunder med Penneo Sign Læs mere Penneo i opråb – Med svindleres brug af AI har vi akut brug for bedre beskyttelse Læs mere Hvad er nyt i Penneo Sign? Produktopdateringer fra Q2 2025 Læs mere Vi introducerer Penneos nye analysepanel: Forbrugsoversigt Læs mere Hvad hvis din kunde siger ‘Det er ikke min underskrift’? Læs mere Sådan gør du din revisionsproces fuldt integreret med Penneo og Caseware Læs mere Q1 2025 Penneo Sign Opdateringer Læs mere Har du brug for at indsamle underskrifter fra internationale interessenter? Penneo Sign gør det nu nemmere Læs mere Hvad er nyt i Penneo Sign? Produktopdateringer fra H2 2024 Læs mere SE FLERE ARTIKLER 4.700 i erhvervslivet læser allerede vores nyhedsbrev - hvad med dig? Når du tilmelder dig vores e-mail nyhedsbrev holder vi dig opdateret på alt det nyeste inden for digitale underskrifter. Du får også et klart overblik over, hvad nye regler betyder i praksis for dig og din virksomhed. Vi sender dig nøje udvalgt indhold, så du nemt kan holde dig et skridt foran. Email Dette felt er til validering og bør ikke ændres. E-mail * * Jeg giver samtykke til at modtage nyheder og opdateringer fra Penneo via e-mail. Indsigter fra vores eksperter Fredrik Lernevall Information Security Manager hos Penneo Læs mere Ksenia Bezukladnikova Product Manager hos Penneo Læs mere Kasper Behrens Strategisk forretningsudvikler Læs mere Nina Vesalainen Seniorjurist hos Penneo Læs mere Tag en snak med os Vil du se, hvordan Penneo Sign fungerer i praksis? Book en kort demo, og så viser vi dig platformen trin for trin, og besvarer dine spørgsmål. Helt uden pres. BOOK ET MØDE Start din gratis prøveperiode i dag Underskriv dine første dokumenter med Penneo Sign på få minutter, og se, hvor nemt det er at komme i gang med digital signering. Vi beder ikke om dine kortoplysninger. GRATIS PRØVEPERIODE 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:35 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT32dSAIFyj6v8l4Hn2MhVxBzcA7uvvRSf0mPBb-hDG4drHHy6wMm3TktTLLHZjD2VN87n2M7qhHryxKnJbcEluS4PN2F-8tFcu3U1NmjG6WkK42UecmiyfVwJ3z97i-Qy8XACr_mO-RIpjb | 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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:35 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.