cloudflare / .github Goto Github PK

PR proposal: Provide direct link to docs and httpHostHeader example

Changes: diff in my repository

Filing this as a result of my experience, and opening this issue first per the contributing guidelines.

Rationale

The httpHostHeader key defaults to "" per the documentation, which overrides what the browser sends and requires this key to be set for most k8s ingress controllers configured on a per host basis. Most k8s implementations will have cloudflared call a common ingress controller which, if looking for a specific host, as is usually the case, and the request comes in without it, will 404. Therefore, I recommend including the example.

(Even better, in the future, would love to see an option to preserve this header in named tunnels).

In addition, based on the difficulty navigating documentation to find these parameters and, in particular, their defaults, I recommend including the direct link to those docs similar to the ingress doc link further down in the config.yaml example.

Your code references Request[...] which causes IIS to read the entire request object, including the post content.

Once that is done any Classic ASP code which needs to reference Request.form fails. (https://stackoverflow.com/questions/17903722/classic-asp-request-form-not-working-when-using-integrated-pipeline)

I changed all occurrences of Request[...] to Request.ServerVariables[...] to fix the issue.

P.S. Yes I know that this module is officially deprecated and you refer users to other options (https://developers.cloudflare.com/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/). The options you recommend only help for capturing the client ip in the log files, it does not help for exposing the correct ip within the application, so I still need to use this module.

WICG/turtledove#725

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY]
Build fingerprint: HONOR/VNE-LX3/HNVNE-M:12/HONORVNE-L43CM/6.1.0.268C605E2R2P1:user/release-keys
Brand: HONOR
Device: HNVNE-M
Model: VNE-LX3
TestId: dGVzdGluZy0xYTE3ODdiMi01NWViLTQ5YzYtYjEyZi0zZTk5NzEzN2ZmMWU=

I need to use cfssl to generate certs with subject names that are general OIDs.

My proposal is to extend Name field to include an OID component which would be a map from strings (OID dot notation) to string values.

See accompanying PR.

The [email protected] email address listed in the Cloudflare contributing guidelines and code of conduct does not work, I received the below bounce message from Google in response to a mail asking the group to look at an issue I filed.

Hello,

We're writing to let you know that the group you tried to contact (opensource) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post:

 * You might have spelled or formatted the group name incorrectly.
 * The owner of the group may have removed this group.
 * You may need to join the group before receiving permission to post.
 * This group may not be open to posting.

If you have questions related to this or any other Google Group, visit the Help Center at https://support.google.com/a/cloudflare.com/bin/topic.py?topic=25838.

Thanks,

cloudflare.com admins

zlib, for example, has no issues page, so one can't file an issue to discuss planned work.

firasdib/Regex101#2094

TAWAN boonsingh development international Business and [email protected]

[email protected]

_Originally posted by @aody9992o in https://github.com/0000854453/finance-portfolio-e49421e3-f92d-43cc-b074-cbe76526fd59/issues/3

I'm trying to narrow down why text messages aren't coming to my device. My carrier, who is assurance wireless confirmed my connection is great. I don't use cloudflare whatsoever, and actually would like this platform to be detached from my network and IP address. I think it's conflicting with Google DNS. Please assist me because I haven't received any text messages to my device all day. This is unacceptable. What are my options? I don't not need or have any interest in firewalls etc. I want my text messages and ability to interact on my device as usual. Please assist me.

https://pipelinesghubeus2.actions.githubusercontent.com/DhNHyOUSVaJqQNlidg3CSYOoA9ohSYeigIa0MLmne5rpEYmyXy/_apis/pipelines/1/runs/80095/signedlogcontent/2?urlExpires=2023-11-30T07%3A22%3A11.9583242Z&urlSigningMethod=HMACV1&urlSignature=9auIV1zHPxUWfOLidVwO6QrEU6f5I9huByEhVodZTUQ%3D

title: About community profiles for public repositories
intro: Repository maintainers can review their public repository's community profile to learn how they can help grow their community and support contributors. Contributors can view a public repository's community profile to see if they want to contribute to the project.
redirect_from:

• /articles/viewing-your-community-profile
• /articles/about-community-profiles-for-public-repositories
• /github/building-a-strong-community/about-community-profiles-for-public-repositories
  versions:
  fpt: ''
  ghec: ''
  topics:
• Community
  shortTitle: Community profiles

The community profile checklist checks to see if a project includes recommended community health files, such as README, CODE_OF_CONDUCT, LICENSE, or CONTRIBUTING, in a supported location. For more information, see "AUTOTITLE."

Using the community profile checklist as a repository maintainer

As a repository maintainer, you can use the community standards checklist to see if your project meets the recommended community standards to help people use and contribute to your project. For more information, see "Building community" in the Open Source Guides.

If a project doesn't have one of the recommended files, you can click the associated Add button to draft and submit a file.

{% data reusables.repositories.security-guidelines %}

{% data reusables.repositories.valid-community-issues %} For more information, see "AUTOTITLE."

Using the community profile checklist as a community member or collaborator

As a potential contributor, use the community profile checklist to see if a project meets the recommended community standards and decide if you'd like to contribute. For more information, see "How to contribute" in the Open Source Guides.

If a project doesn't have a recommended file, you can click Propose to draft and submit a file to the repository maintainer for approval.

Further reading

• "AUTOTITLE"
• "AUTOTITLE"
• "AUTOTITLE"
• "AUTOTITLE"
• "Open Source Guides"
• [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})

We use custom hostnames quite extensively. In our multi-tenant architecture, we exclusively use custom_origin_server.

We need to extend the CustomHostname struct to include the custom_origin_server property, when used.

I installed cert-manager and origin-ca-issuer with helm and then created a secret, an originissuer, and a certificate.
my originissuer is verified & ready:

[
  {
    "lastTransitionTime": "2021-03-04T07:57:32Z",
    "message": "OriginIssuer verified and ready to sign certificates",
    "reason": "Verified",
    "status": "True",
    "type": "Ready"
  }
]

but in the certificaterequest i see the message:

Message:               Failed to sign certificate request: unable to sign request: Post "https://api.cloudflare.com/client/v4/certificates": net/http: invalid header field value "v1.0-FFFFF-FFFFFF\n" for key X-Auth-User-Service-Key

I re-deployed everything to make sure I did not forget anything but it is always the same issue.
my resources are:

apiVersion: v1
kind: Secret
metadata:
  name: cloudflare-origin-ca-key
  namespace: istio-gateway
data:
  key: KEY
---
apiVersion: cert-manager.k8s.cloudflare.com/v1
kind: OriginIssuer
metadata:
  name: cloudflare-origin-ca-issuer
  namespace: istio-gateway
spec:
  requestType: OriginECC
  auth:
    serviceKeyRef:
      name: cloudflare-origin-ca-key
      key: key
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: wildcard.examle.com
  namespace: istio-gateway
spec:
  secretName: wildcard.example.com-tls
  issuerRef:
    group: cert-manager.k8s.cloudflare.com
    kind: OriginIssuer
    name: cloudflare-origin-ca-issuer
  dnsNames:
  - '*.example.com'

any ideas what my issue is?

title: Contributing to GitHub Docs documentation
shortTitle: Contribute to GitHub Docs
intro: 'Learn about how the {% data variables.product.prodname_docs %} team creates documentation and how you can contribute.'
layout: product-landing
versions:
feature: 'contributing'
featuredLinks:
startHere:
- /contributing/writing-for-github-docs/about-githubs-documentation-philosophy
- /contributing/style-guide-and-content-model/style-guide
- /contributing/style-guide-and-content-model/about-the-content-model
- /contributing/collaborating-on-github-docs/about-contributing-to-github-docs
changelog:
label: docs
children:

• /writing-for-github-docs
• /style-guide-and-content-model
• /collaborating-on-github-docs
• /setting-up-your-environment-to-work-on-github-docs

Please make the following changes to the language selector for the 1.1.1.1 site:

• Change "Indonesia" to "Bahasa Indonesia". The original name was correct, but this is to avoid confusion between the name of the language and the name of the country.
• Now that all locales have been added, the locale list needs to be sorted. Please sort it as follows:

English
Bahasa Indonesia
Deutsch
Español
Français
Italiano
Nederlands
Polski
Português
Türkçe
العربية
فارسی
日本語
한국어
Русский
简体中文
繁體中文