Last month, I published two articles that talked about using cURL to handle redirects that may inevitably happen when working with certain URLs.

Specifically, I’m talking about:
- Finding the Destination of a Redirect with PHP
- Using cURL to Determine If the Specified URL Is a Valid Page
And though the second one is more of the subject of this post, I wanted to reference both since they are related.
Earlier this month, I wrote a bit how the purpose of blogging has changed. Perhaps it would’ve been better to talk about the motivation rather than the purpose, but I digress.
In this post, I talk a bit about commenting and feedback. And since I’ve closed comments, one of the ways that people will talk with me about certain posts is via Twitter.
Case in point:
Isn’t it better to return 200 === $httpCode as there are other possible status codes too?
— Xaver (@xaver_) May 30, 2019
And I like this because it’s:
- a clearly stated, succinct question,
- it’s directed towards me (with the potential for others to chime in),
- and it can keep the conversation on the topic without it devolving into something else in the comments.
Further, Xaver’s question is good because it shows where my content may be lacking, and it gives me the opportunity to write a follow-up or a clarification on a post like this 🙂.
The thing is, the response to this particular question may not be as long as the lead in, but I always want to give enough context before providing an answer.



