• Log in or sign up for an account here: https://www.sythe.org/login

Why is everything inside the user CP PHP but threads and profiles are .html?

Status
Not open for further replies.

Anet390

Grand Master
Joined
Jun 3, 2010
Sythe Gold
291
Messages
2,223
Why is everything inside the user CP PHP but threads and profiles are .html?
I was going to post this into programming, but I figured it's Sythe.org related and the description of this forum is spot on "Assistance for anything Sythe.org related".

So why is the User CP programmed in .php but profile links like http://www.sythe.org/members/254183-anet390.html and thread links like the url you are on now are HTML.

I know why threads are in HTML because its mostly text and so I assume since User CP is mostly an interface and has more user stored data? I really know nothing about PHP but I've heard something about it relating to security and a lot of user based files and stuff (I think?). I'm not really sure about profile links though because I assume it has user data but I guess since it's displayed in text mostly? But so is User CP so I'm not sure lol.


Thanks,
Anet390
 
Why is everything inside the user CP PHP but threads and profiles are .html?
bump.
 
Why is everything inside the user CP PHP but threads and profiles are .html?
Better off PMing one of the tech admins as I doubt anyone outside of them would likely know the answer.
 
Why is everything inside the user CP PHP but threads and profiles are .html?
bump.
 
Why is everything inside the user CP PHP but threads and profiles are .html?
You'll need to ask someone involves with that kind of thing Govind/Matthew/Sythe.
 
Why is everything inside the user CP PHP but threads and profiles are .html?
To answer your question: All user facing pages are written in PHP. Some URLs are "rewritten" (re-mapped) from what you would otherwise expect for SEO reasons.

The description of content delivered by the HTTP protocol is not dependent or even remotely related to the URL at which the content is found. The Content-Type HTTP header specifies this information. For example requesting the following URL "http://example.com/virus.exe" could return a content type of "application/octet-stream" (which is a binary file which might indeed be executable) or it could return a content type of "text/plain" in which case it is / will be displayed as a text file.

Long story short: our servers see your requested URL and can do whatever they please with it. They are not bound by your assumptions about how they would or should handle it. A URL can be in any format or structure that is allowed by a HTTP request.

More information here:
https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Response_message
 
Status
Not open for further replies.
Runescape Gamblingrunescape gambling
Back
Top