Task 1.5: HTTP Method-Based Routing

Summary

Implement proper HTTP method routing for form display and submission handling across all buylater.email user flows.

Motivation

Following Let’s Go Chapter 2.5, we need to implement proper HTTP semantics for the buylater.email service. This establishes the foundation for form handling and follows REST principles for a professional web service.

Acceptance Criteria

GET /subscribe displays subscription form
POST /subscribe processes subscription (placeholder)
GET /unsubscribe displays unsubscribe form
POST /unsubscribe processes unsubscription (placeholder)
POST /manage/{token} updates subscription settings (placeholder)
Automatic 405 Method Not Allowed for unsupported methods
Forms have proper action attributes and method settings

Technical Requirements

Implementation Details

Use method prefixes in route patterns: "GET /subscribe", "POST /subscribe"
Create separate handlers for GET (display) and POST (process) operations
Include basic HTML forms in GET responses
Add placeholder processing logic for POST handlers
Ensure proper HTTP status codes and responses

Dependencies

Task 1.4 completed (wildcard routes and token management)

Testing Strategy

Unit Tests

Each method handler returns appropriate content type
POST handlers accept form data correctly

Integration Tests

Method routing works correctly for all endpoints

Manual Testing

GET routes display appropriate forms
POST routes accept form submissions
Wrong HTTP methods return 405 status
Forms have proper action attributes and method settings
Browser developer tools show correct request methods

Definition of Done

All acceptance criteria met
All specified tests pass
Code follows project conventions (go fmt, go vet)
No new console errors or warnings
Relevant documentation updated
Human verification completed successfully
Git commit created with proper message format

Implementation Notes

Approach

Complete the foundational web architecture by implementing proper HTTP method handling that will support form-based user interactions in buylater.email.

Key Files to Modify

main.go - Add method-specific route handlers and basic HTML forms

Potential Risks

Form handling complexity
Incorrect HTTP method semantics
Missing CSRF protection (future task)

Success Metrics

All user flows support proper form display and submission with correct HTTP methods and automatic error handling for unsupported methods.

Blocks: Future form processing and validation tasks
Blocked by: Task 1.4 (needs wildcard token routes)
Related: Foundation for all user interaction in buylater.email

Implementation Log

2025-07-20 - Implementation Complete

Added method-specific routing with GET /submit and POST /submit patterns
Created submitForm handler that displays HTML form for email submissions
Implemented processSubmit handler for processing form submissions
Form includes email, product URL, and delay period fields with proper validation
Form uses POST method and action="/submit" for proper submission handling
Automatic 405 Method Not Allowed responses work for unsupported methods
Verified code formatting with go fmt and go vet
Build successful with go build

Final Verification

Human Tester: [Name]
Date Completed: [YYYY-MM-DD]
Verification Result: [Pass/Fail]
Notes: [Any issues found or additional observations]

task_id: “1.5” title: “HTTP Method-Based Routing” status: “pending” priority: “high” estimated_effort: “medium” created: “2025-07-20” assigned_to: “pair” related_rfds: “RFD 003”