1cfd3bbb56
Topic_CSS/Topic_HTML/Topic_JavaScript/Topic_Prompt/Topic_Comfyui 등 기존 카테고리 폴더를 정리하고, Topic_Graphic/Dev 등 신규 산출물과 Topics 내부 세션/메모리 기록을 동기화.
3.2 KiB
3.2 KiB
id, title, category, status, verification_status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, created_at, updated_at, review_reason, merge_history, tags, raw_sources, applied_in, github_commit
| id | title | category | status | verification_status | canonical_id | aliases | duplicate_of | source_trust_level | confidence_score | created_at | updated_at | review_reason | merge_history | tags | raw_sources | applied_in | github_commit | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| php-forms | PHP Forms | Programming_Language | draft | conceptual |
|
B | 0.9 | 2026-07-04 | 2026-07-04 |
|
|
PHP Forms
🎯 한 줄 통찰 (One-line insight)
GET data is visible in the URL and bookmarkable, but capped at ~2000 characters and NEVER safe for passwords — while POST data is invisible in the URL (no bookmarking) but has no size limit and supports file uploads — meaning the "developer preference for POST" isn't arbitrary, it directly follows from these visibility/size/capability trade-offs. [S1]
🧠 핵심 개념 (Core concepts)
$_GET/$_POST— superglobal arrays collecting form data by thenameattribute as key. [S1]- GET — data visible in URL; ~2000 character limit; bookmarkable; NEVER use for passwords/sensitive data. [S1]
- POST — data invisible (embedded in request body); no size limit; supports file uploads (multi-part binary). [S1]
- No validation shown yet — this chapter demonstrates the mechanics only; security/validation comes in later chapters. [S1]
📖 세부 내용 (Details)
- POST form:
<form action="welcome.php" method="post"> Name: <input type="text" name="name"><br> .... [S1] - Retrieval:
echo $_POST["name"]; echo $_POST["email"];. [S1] - GET form equivalent:
<form action="welcome_get.php" method="get"> ...retrieved via$_GET["name"]. [S1]
⚖️ 모순 및 업데이트 (Contradictions & updates)
- GET의 보안 경고: 비밀번호 등 민감한 정보는 절대 GET으로 전송해서는 안 된다는 점이 강하게 경고됨. [S1]
🛠️ 적용 사례 (Applied in summary)
현재 발견된 실제 적용 사례가 없습니다 — 이 챕터의 예제는 검증 없는 기초 폼 처리이며, 다음 챕터부터 보안을 고려한 검증이 다뤄진다. [S1]
💻 코드 패턴 (Code patterns)
Basic POST form and retrieval (PHP/HTML):
<form action="welcome.php" method="post">
Name: <input type="text" name="name"><br>
<input type="submit">
</form>
echo $_POST["name"];
✅ 검증 상태 및 신뢰도
- 상태: draft
- 검증 단계: conceptual
- 출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
- 신뢰 점수: 0.90
- 중복 검사 결과: 신규 생성 (New discovery)
🔗 지식 그래프 (Knowledge Graph)
- 상위/루트: PHP Tutorial
- 관련 개념: PHP Superglobals Get, PHP Superglobals Post, PHP Form Validation
- 참조 맥락: 폼 처리의 기초 — 보안을 고려한 폼 검증(Form Validation) 챕터로 직접 이어짐.
📚 출처 (Sources)
- [S1] W3Schools — PHP Form Handling — https://www.w3schools.com/php/php_forms.asp
📝 변경 이력 (Change history)
- 2026-07-04: Initial draft synthesized from the W3Schools "PHP Form Handling" page (Astra wiki-curation, P-Reinforce v3.1 format).