GitLab

Enhance WafLogController proxy handling by setting request URL scheme and preserving query parameters, improving request integrity for WAF log processing.

Refactor WafLogController to implement a new ReverseProxy structure, enhancing URL path rewriting and host assignment for improved proxy request handling.

Refactor WafLogController to utilize the new proxy request rewriting method, improving URL handling and ensuring correct host assignment for WAF log requests.

Update WafLogController to set request URL scheme in proxy handling, ensuring correct protocol usage for WAF log requests.

Refactor import statements in cmd.go and app.go for improved organization; add logging in WafLogController for better traceability of proxy requests.

Update WafLogController to use 'region_code' query parameter instead of 'region' for improved clarity in WAF log proxy handling.

Refactor API router and WAF handling to support additional parameters and improve configuration management

This update modifies the SetRouters and SetWafRouter functions to accept new parameters, including a debug flag and a region URL map, enhancing the flexibility of the API routing. Additionally, a new SetApiRouters function is introduced for better organization of API routes. The configuration management has been streamlined by moving configuration imports to the internal package, ensuring a more consistent structure across the application.

This update introduces the ability to set the RDB password via an environment variable in the LoadConfig function, enhancing database security. Additionally, the IP info controller file has been removed as it was no longer needed, streamlining the codebase.

Enhance WafService and ListWafsV2 response by adding ID field to improve data representation and clarity in WAF listings.

- Introduce ListWafsV2 method in WafController to enhance the WAF listing functionality with a new response structure.
- Update the API route for listing WAFs to point to the new ListWafsV2 method, improving clarity and consistency in the API design.

- Update GetAttackLogDetails and GetAttackLogRsp methods in the WafController and wafService to accept UUID as a string parameter instead of a uint32 ID.
- Modify corresponding service interface to reflect the change in parameter type for improved clarity and consistency in handling attack logs.

- Introduce new API routes for fetching attack log details and response packages.
- Implement corresponding methods in the WafController and wafService to handle the new functionality.
- Update service interface and types to support the new data structures for attack logs and responses.

- Set the default limit for listener history queries to 1,000,000 in the ListListenerHistory method.
- Change the operation constant for creation from "新建" to "创建" for improved clarity in the WAF model.

- Introduce a new GET endpoint for listing attack classes in the WAF router.
- Implement AttackClassesList method in WafController to handle requests and return attack class data based on the specified language.
- Enhance the WAF service with ListAttackClasses method to retrieve attack classes and support localization for descriptions.
- Define AttackClasses struct to standardize the response format for attack class data.

- Introduce a new GET endpoint for listing listener history in the WAF router.
- Implement ListListenerHistory method in the WafController to handle requests and return paginated results based on query parameters.
- Enhance the WAF service to log listener creation and deletion events, capturing relevant details for auditing purposes.
- Update the WafListenerHistory model and service methods to support querying and storing listener history data effectively.

- Update the response format in the GetBlackWhiteLists method to utilize a new ListRespData structure, enhancing clarity and consistency in the returned data.
- Maintain existing functionality while improving the organization of response data, including items and total count.

- Update the GetBlackWhiteLists method in both the service and controller layers to return the total number of items alongside the list of MatcherExpr.
- Modify response structure in the controller to include total items for improved client-side handling.
- Ensure proper error handling and maintain existing functionality while enhancing data retrieval capabilities.

- Add UpdateBlackWhiteList method in WafController to handle updates to black/white list entries
- Introduce EnableBlackWhiteList method in WafController for enabling/disabling black/white lists
- Enhance WafService with logic to update and manage configuration maps for black/white lists
- Ensure proper error handling and response assembly for both methods

- Introduce ListWafs method in WafController to retrieve a list of WAF services
- Update WAF router to include new GET routes for listing WAFs
- Implement ListWafs method in the service layer to fetch WAF data from the database
- Enhance the MatcherExpr and WafService structures to support new functionality

- Implement Create, Update, Enable, Delete, and Get methods for managing Black/White Lists
- Introduce new routes in the WAF router for handling Black/White List operations
- Update service and model layers to support new functionality
- Refactor cluster client management to accommodate new Kubernetes client structure

- Introduce a new response structure to encapsulate rule group items
- Map existing rules to the new response format, including category details
- Ensure consistent response format for improved API usability

- Add log statements to track Elasticsearch query hits and source data
- Improve visibility into WAF attack log retrieval process
- Log raw Elasticsearch response and individual hit sources for debugging

- Integrate Elasticsearch client for querying WAF attack logs
- Add new API endpoints for listing attack logs and WAF rules
- Implement pagination and filtering for attack log retrieval
- Support language-based rule category display
- Update service and controller layers to support new functionality

- Update `Waf` method in WafController to retrieve gateway details using query parameters
- Modify parameter extraction from `ctx.Param()` to `ctx.Query()`
- Maintain consistent method signature and service call logic

- Introduced new API endpoint and service method to enable/disable WAF for multiple listeners
- Updated router, controller, and service to support bulk listener WAF operations
- Added new request type `EnableListenerWafsReq` to handle multiple listener configurations
- Implemented logic to add or remove WAF configurations for specific listeners based on input

- Modified SQL migration to add 'hosts' column to gateway_listeners table
- Updated model, service, and controller to support hosts in gateway listener operations
- Added new GetWafGatewayInfo method to retrieve WAF gateway information
- Refactored WAF service methods to handle hosts and improve flexibility