Programmed Canon Canola calculators in 1977. Assorted platforms and languages ever since. Assisting with HOPL.info.
I am NOT looking for work -- I've got more than enough to do.
Location
Perth, WA Australia
Education
A few diplomas.
Work
Software Engineer at [Daisy Digital](https://daisydigital.com.au/)
This is, by the way, me trying to find an IIS-based approach. We got a contractor to figure out how to do it in nginx but he only got as far as the server-to-third-party part and couldn't tell us how to do the browser-to-server part. This serverfault posting is me trying to find out what to do next. I got given a pointer but it assumed more knowledge than I actually have.
Programmed Canon Canola calculators in 1977. Assorted platforms and languages ever since. Assisting with HOPL.info.
I am NOT looking for work -- I've got more than enough to do.
Location
Perth, WA Australia
Education
A few diplomas.
Work
Software Engineer at [Daisy Digital](https://daisydigital.com.au/)
I have tried a number of things like that, but without good results. I'm having a I-just-don't-get-it moment which I'm hoping will pass soon. I finally understood outbound rules this morning. I'm hoping for that understanding of inbound rules will follow soon.
I don't want it to resolve to a physical path. I want it to resolve to a third party site. And what's with all the third repeats? The original request was http://our.server:80/third/au/mx which I want to resolve to http://thirdparty.com/au/mx
And then there's all the links to the thirdparty that will need to get rewritten as links to our.server ... but that's another story.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Have you tried a url rewrite wildcard with source specified like domain.com/{R:0} and ensure TLS 1.3 is fully supported.
I think it's bizarre that there'll be so much issues with it although I don't know the whole issues.
This is, by the way, me trying to find an IIS-based approach. We got a contractor to figure out how to do it in
nginxbut he only got as far as the server-to-third-party part and couldn't tell us how to do the browser-to-server part. This serverfault posting is me trying to find out what to do next. I got given a pointer but it assumed more knowledge than I actually have.I have tried a number of things like that, but without good results. I'm having a I-just-don't-get-it moment which I'm hoping will pass soon. I finally understood outbound rules this morning. I'm hoping for that understanding of inbound rules will follow soon.
For example a (redacted) error
I don't want it to resolve to a physical path. I want it to resolve to a third party site. And what's with all the
thirdrepeats? The original request washttp://our.server:80/third/au/mxwhich I want to resolve tohttp://thirdparty.com/au/mxAnd then there's all the links to the thirdparty that will need to get rewritten as links to our.server ... but that's another story.