<div dir="ltr">>><span style="font-size:12.8px">if you don't own the domain then you won't ever receive the request and you can't do nothing about it</span><br><span style="font-size:12.8px">We don't own <a href="http://ad.domain.com">ad.domain.com</a> but that domain sends http/https request to our domain '<a href="http://ourdomain.com">ourdomain.com</a>' .We just need to find out the $scheme they use to send requests such as :</span><br><br><span style="font-size:12.8px">Is request coming from <a href="http://ad.domain.com">http://ad.domain.com</a> or is it coming from <a href="https://ad.domain.com">https://ad.domain.com</a> ?</span><div class="" style="font-size:12.8px"><div class="adm"><div id="q_150f64be9386d084_1" class="h4"></div></div></div><input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false},"attachments":{}}"></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 11, 2015 at 4:02 PM, Avraham Serour <span dir="ltr"><<a href="mailto:tovmeod@gmail.com" target="_blank">tovmeod@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">if you don't own the domain then you won't ever receive the request and you can't do nothing about it</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 11, 2015 at 1:01 PM, shahzaib shahzaib <span dir="ltr"><<a href="mailto:shahzaib.cb@gmail.com" target="_blank">shahzaib.cb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">One point is worth mentioning, we don't own <a href="http://ad.domain.com" target="_blank">ad.domain.com</a> its a 3rd party website. All we can control is <a href="http://ourdomain.com" target="_blank">ourdomain.com</a>.<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false},"attachments":{}}"></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 11, 2015 at 3:25 PM, shahzaib shahzaib <span dir="ltr"><<a href="mailto:shahzaib.cb@gmail.com" target="_blank">shahzaib.cb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span>>><span style="font-size:12.8px">you can create separate server blocks for each domain</span><input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false},"attachments":{}}"></span><div><span style="font-size:12.8px">I think issue will still persist. Say <a href="https://ad.domain.com" target="_blank">https://ad.domain.com</a> makes static call to <a href="http://ourdomain.com" target="_blank">http://ourdomain.com</a> , it'll end up with conflicted scheme i.e https -> http. We can't force http to https as well because it'll break static calls from http -> http.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Actually we've video sharing website from where people embed http/https links to there websites. Now the problem is, some of the HTTPS websites have embedded HTTP URL links from our website instead of HTTPS due to which the code is unable to execute on their HTTPS website because it is making call from https -> http which is wrong. The number of these malformed links are huge and there's no way that those users can manually correct the embedded links by editing http to https and vice versa). </span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">So we're thinking to have some condition in place that if the request for HTTP embedded link comes from any HTTPS domain , nginx will detect that source $scheme and redirect that request to HTTPS.</span></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 11, 2015 at 3:10 PM, Avraham Serour <span dir="ltr"><<a href="mailto:tovmeod@gmail.com" target="_blank">tovmeod@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">you can create separate server blocks for each domain</div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Wed, Nov 11, 2015 at 11:36 AM, shahzaib shahzaib <span dir="ltr"><<a href="mailto:shahzaib.cb@gmail.com" target="_blank">shahzaib.cb@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi,<div><br></div><div> Is there a way we can serve $scheme (HTTP/HTTPS) based on source request ? Such as :<br><br>if <a href="https://ad.domain.com" target="_blank">https://ad.domain.com</a> --> sends request to <a href="http://ourdomain.com" target="_blank">http://ourdomain.com</a> (as it'll fail due to cross $scheme conflict)</div><div><br></div><div>So <a href="http://ourdomain.com" target="_blank">http://ourdomain.com</a> will check that the request invoked using https $scheme and it'll redirect <a href="http://ourdomain.com" target="_blank">http://ourdomain.com</a> to <a href="https://ourdomain.com" target="_blank">https://ourdomain.com</a> for that particular <a href="http://ad.domain.com" target="_blank">ad.domain.com</a>.</div><div><br></div><div>---------------------------------------------------------</div><div><br></div><div>Is that possible guys ?<br><br>Thanks in Advance !<br><br>Regards.</div><div>Shahzaib<br><br>
<br>
<div lang="klingon" style="color:rgb(146,146,146)!important;display:block">
Need to send me private email? I use <a lang="klingon" style="color:#929292!important" href="https://www.virtru.com/how-it-works/?utm_medium=Email&utm_source=Plugin%20Users&utm_campaign=Footer" target="_blank">Virtru</a>.
<div></div>
</div><input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false},"attachments":{}}"></div></div>
<br></div></div>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br></blockquote></div><br></div>