Origin header patch & header question
Saint-Genest Gwenael <[email protected]> Fri, 25 Mar 2016 10:13:52 +0100
| Newsgroups | gmane.comp.gcc.cgicc.general |
|---|---|
| Message-ID | <[email protected]> |
--=_61d5519be918bdd3bd0f7767cb6a9e23 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8; format=flowed Hi, For my target application, i must implement CORS. To respond the right Access-*-Origin it is necessary to get the Origin from the request header. The small attached patch add an accessor to CgiEnvironment Actually, each known and supported header have a dedicated member into Environment. Today, there is a lot of application specific header that can be used, so, i think a more generic way to read headers could be better. Opinions ? Comments ? Regards, G. Saint-Genest --=_61d5519be918bdd3bd0f7767cb6a9e23 Content-Transfer-Encoding: base64 Content-Type: text/x-diff; name=env-origin.patch Content-Disposition: attachment; filename=env-origin.patch; size=1244 ZGlmZiAtdXJOIGNnaWNjLXJlZi9jZ2ljYy9DZ2lFbnZpcm9ubWVudC5jcHAgY2dpY2MtZGV2L2Nn aWNjL0NnaUVudmlyb25tZW50LmNwcAotLS0gY2dpY2MtcmVmL2NnaWNjL0NnaUVudmlyb25tZW50 LmNwcAkyMDE0LTEyLTA3IDE1OjI4OjMwLjAwMDAwMDAwMCArMDEwMAorKysgY2dpY2MtZGV2L2Nn aWNjL0NnaUVudmlyb25tZW50LmNwcAkyMDE2LTAzLTIzIDAxOjA1OjU5LjkyNDkxNTI4NSArMDEw MApAQCAtMjYwLDYgKzI2MCw4IEBACiAgIGZSZWZlcnJlciAJCT0gaW5wdXQtPmdldGVudigiSFRU UF9SRUZFUkVSIik7CiAgIGZDb29raWUgCQk9IGlucHV0LT5nZXRlbnYoIkhUVFBfQ09PS0lFIik7 CiAgIGZBY2NlcHRMYW5ndWFnZVN0cmluZyA9IGlucHV0LT5nZXRlbnYoIkhUVFBfQUNDRVBUX0xB TkdVQUdFIik7IAorICAKKyAgZk9yaWdpbiAgICAgICAgICAgICAgID0gaW5wdXQtPmdldGVudigi SFRUUF9PUklHSU4iKTsKIAogICAvLyBXaW4zMiBidWcgZml4IGJ5IFBldGVyIEdvZWR0a2luZHQg CiAgIHN0ZDo6c3RyaW5nIGh0dHBzIAk9IGlucHV0LT5nZXRlbnYoIkhUVFBTIik7CmRpZmYgLXVy TiBjZ2ljYy1yZWYvY2dpY2MvQ2dpRW52aXJvbm1lbnQuaCBjZ2ljYy1kZXYvY2dpY2MvQ2dpRW52 aXJvbm1lbnQuaAotLS0gY2dpY2MtcmVmL2NnaWNjL0NnaUVudmlyb25tZW50LmgJMjAxNC0wNC0y MyAyMjo1NTowMy4wMDAwMDAwMDAgKzAyMDAKKysrIGNnaWNjLWRldi9jZ2ljYy9DZ2lFbnZpcm9u bWVudC5oCTIwMTYtMDMtMjMgMDE6MDc6MjQuNTM2OTE3MDg5ICswMTAwCkBAIC01MDAsNiArNTAw LDEwIEBACiAgICAgeyByZXR1cm4gZlJlZGlyZWN0U3RhdHVzOyB9CiAgICAgLy9AfQogICAgIAor ICAgIGlubGluZSBzdGQ6OnN0cmluZworICAgIGdldE9yaWdpbigpCQkJCQljb25zdAorICAgIHsg cmV0dXJuIGZPcmlnaW47IH0KKyAgICAKICAgcHJvdGVjdGVkOgogICAgIAogICAgIC8vID09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpA QCAtNTczLDYgKzU3Nyw3IEBACiAgICAgc3RkOjpzdHJpbmcgCQlmQ29va2llOwogICAgIHN0ZDo6 dmVjdG9yPEhUVFBDb29raWU+IAlmQ29va2llczsKICAgICBzdGQ6OnN0cmluZyAgICAgICAgICAg ICAgICAgZkFjY2VwdExhbmd1YWdlU3RyaW5nOyAKKyAgICBzdGQ6OnN0cmluZyAgICAgICAgICAg ICAgICAgZk9yaWdpbjsKICAgfTsKICAgCiB9IC8vIG5hbWVzcGFjZSBjZ2ljYwo= --=_61d5519be918bdd3bd0f7767cb6a9e23 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ help-cgicc mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-cgicc --=_61d5519be918bdd3bd0f7767cb6a9e23--